This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
2013/4/29 Jakub Jelinek <jakub@redhat.com>: > Also, why are you handling just %{ and %}, and > not also %| ? I mean, if you want to print say {|} into assembly for both > dialects, don't you need: > asm ("{dialect1%{%|%}|%{%|%}dialect2}"); > or similar? If you use just | instead of %|, it would be handled as > separator of the dialects. Sure. %| was removed due to concerns over some target architectures already use it, but now %| is under ASSEMBLER_DIALECT and doesn't seem to affect them. ChangeLog: 2013-04-29 Maxim Kuznetsov <maks.kuznetsov@gmail.com> * final.c (do_assembler_dialects): Don't handle curly braces and vertical bar escaped by % as dialect delimiters. (output_asm_insn): Print curly braces and vertical bar if escaped by % and ASSEMBLER_DIALECT defined. * doc/tm.texi (ASSEMBLER_DIALECT): Document new standard escapes. testsuite/ChangeLog: 2013-04-29 Maxim Kuznetsov <maks.kuznetsov@gmail.com> * gcc.target/i386/asm-dialect-2.c: New testcase. -- Maxim Kuznetsov
Attachment:
curly_braces_20130429-2.patch
Description: Binary data
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |