[llvm-bugs] [Bug 27464] New: clang doesn't unescape \(\) in response correctly

via llvm-bugs llvm-bugs at lists.llvm.org
Thu Apr 21 18:16:13 PDT 2016


            Bug ID: 27464
           Summary: clang doesn't unescape \(\) in response correctly
           Product: clang
           Version: trunk
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P
         Component: Driver
          Assignee: unassignedclangbugs at nondot.org
          Reporter: nicolasweber at gmx.de
                CC: llvm-bugs at lists.llvm.org
    Classification: Unclassified

$ cat test.c
void bar() {}
void f() { FOO; }
$ cat foo.rsp
$ gcc -c test.c @foo.rsp  # works
@ clang -c test.c @foo.rsp
test.c:3:3: error: expected ';' after expression
<command line>:1:16: note: expanded from here
#define FOO bar\(\)

rsp files (on posix) should be unescaped like shell, and `echo bar\(\)` prints
"bar()" as well.

You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20160422/0299acef/attachment.html>

More information about the llvm-bugs mailing list