Searched refs:sequences (Results 1 – 25 of 332) sorted by relevance
12345678910>>...14
27 ; Other sequences besides this one would be OK.62 ; Other sequences besides this one would be OK.109 ; Other sequences besides this one would be OK.144 ; Other sequences besides this one would be OK.204 ; Other sequences besides this one would be OK.242 ; Other sequences besides this one would be OK.
25 ; Other sequences besides this one would be OK.57 ; Other sequences besides this one would be OK.
29 ; Other sequences besides this one would be OK.64 ; Other sequences besides this one would be OK.
45 ; Other sequences besides this one would be OK.77 ; Other sequences besides this one would be OK.
31 ; Other sequences besides this one would be OK.69 ; Other sequences besides this one would be OK.
46 ; Other sequences besides this one would be OK.81 ; Other sequences besides this one would be OK.
2 // One can't pass UTF-8 sequences via multiple escaped chars - in narrow
4 ; thread local variables. These TLS access code sequences are generated8 ; TLS access code sequences are cleaned up.
24 ; test. Obviously, other sequences are valid.63 ; test. Obviously, other sequences are valid.
1 ## Show that llvm-objdump handles invalid byte sequences, and continues.
2 ## Test code sequences of synthesized _restgpr1_{14..31}
2 ## Test code sequences of synthesized _savegpr1_{14..31}
2 ## Test code sequences of synthesized _savegpr0_{14..31}
2 ## Test code sequences of synthesized _restgpr0_{14..31}
19 …y vary from 1 to 13 dwords, but assembler currently supports a limited range of register sequences.
4 - sequences: `int x; this is absolute garbage; x++;`8 brackets ("lazy parsing") and vague ones about sequences.34 Can we apply the same technique to sequences?