[LLVMbugs] [Bug 20597] New: clang-cl: '@' args after /link should not be expanded to response files

[bugzilla-daemon at llvm.org]

http://llvm.org/bugs/show_bug.cgi?id=20597

            Bug ID: 20597
           Summary: clang-cl: '@' args after /link should not be expanded
                    to response files
           Product: clang
           Version: trunk
          Hardware: All
                OS: All
            Status: NEW
          Severity: normal
          Priority: P
         Component: Driver
          Assignee: unassignedclangbugs at nondot.org
          Reporter: rafaelauler at gmail.com
                CC: llvmbugs at cs.uiuc.edu
    Classification: Unclassified

The "/base" flag of MSVC's linker.exe (see
http://msdn.microsoft.com/en-us/library/f7f5138s.aspx) accepts two forms:

/base:{address[,size]}

or

/base:@filename,key

The latter construction is problematic for clang because of the '@' character.
In this case, '@' is not a response file, but a list of key-value pairs that
link.exe can read to establish the base address. However, if a user tries to
pass this argument to the linker via clang-cl, she would be forced to use:

clang-cl /link /base:@filename,key

In this case, clang commandline utilities will wrongly expand the '@' args to a
response file before the clang arg parser kicks in.

This bug could occur in theory, but I am not sure if it occurs in practice. I
am filing it here to keep track of it.

-- 
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/20140808/b9d1a913/attachment.html>