Searched refs:POT (Results 1 – 16 of 16) sorted by relevance
10 "POT-Creation-Date: 2011-06-06 00:34-0400\n"
11 "POT-Creation-Date: 2026-01-28 19:53-0500\n"
10 "POT-Creation-Date: 2022-04-26 17:09-0400\n"
10 "POT-Creation-Date: 2015-05-06 14:59-0400\n"
10 "POT-Creation-Date: 2015-07-01 16:15-0400\n"
36 "POT-Creation-Date: 2015-07-01 16:15-0400\n"
9 "POT-Creation-Date: 2015-07-01 16:15-0400\n"
205 SmallVector<MDNode *, 16> POT; // Post-order traversal. member752 D.ID = G.POT.size(); in createPOT()753 G.POT.push_back(WE.N); in createPOT()785 for (MDNode *N : POT) { in propagateChanges()804 for (auto *N : G.POT) { in mapNodesInPOT()871 for (const MDNode *N : G.POT) in mapTopLevelUniquedNode()
960 std::vector<MachineBasicBlock*> POT; in rewrite() local963 POT.push_back(B); in rewrite()965 for (MachineBasicBlock *B : POT) { in rewrite()
3806 POT-Creation-Date is set to match the timestamp in 5.7.2beta which8547 actually would change more than the POT-Creation-Date line.8553 POT-Creation-Date line. This had pros and cons: It made it clear8557 ignored with something like "diff -I'^"POT-Creation-Date: '" but8566 changes that would affect only the POT-Creation-Date line.8568 Note that po4a always uses msgmerge with --update, so POT-Creation-Date8573 Distribution tarballs will still have non-reproducible POT-Creation-Date
9016 A046;YI SYLLABLE POT;Lo;0;L;;;;;N;;;;;
9465 A046;YI SYLLABLE POT;Lo;0;L;;;;;N;;;;;
12566 D405;D405;1111 1169 11C0;D405;1111 1169 11C0; # (퐅; 퐅; 퐅; 퐅; 퐅; ) HANGUL SYLLABLE POT