[cfe-dev] 2009-10-20-GlobalDebug.c failing on Windows

[John Thompson]

Hmmm, I tried passing -Xclang "-triple=i686-pc-linux-gnu" to clang.exe, but
apparently it conflicts with a -target directive the driver puts in.  But
I'm not sure this is the proper format.  The driver didn't like just
"-target=i686-pc-linux-gnu" either.

Is this a bug in the driver, not checking for options being overidden?
What does the -dA option do?  I don't see it in "clang -help".

Which triple should it be using?

Here's the command output, with the triple option and a -v also:

FAIL: Clang::CodeGen/2009-10-20-GlobalDebug.c (1 of 1)
******************** TEST 'Clang::CodeGen/2009-10-20-GlobalDebug.c' FAILED
********************
Script:
--
C:/Tools/llvm/bin/Debug\clang.EXE -S -g -dA -Xclang
"-triple=i686-pc-linux-gnu" -v
C:\Tools\llvm\tools\clang\test\CodeGen\2009-10-20-GlobalDebug.c -o - |
FileCheck C:\Tools\llvm\tools\clang\test\CodeGen\2009-10-20-GlobalDebug.c
--
Exit Code: 1
Command Output (stdout):
--
Command 0: "C:/Tools/llvm/bin/Debug\clang.EXE" "-S" "-g" "-dA" "-Xclang"
"-triple=i686-pc-linux-gnu" "-v"
"C:\Tools\llvm\tools\clang\test\CodeGen\2009-10-20-GlobalDebug.c" "-o" "-"
Command 0 Result: 1
Command 0 Output:

Command 0 Stderr:
clang version 1.1 (trunk 84674)
Target: i686-pc-win32
Thread model: posix
 "C:/Tools/llvm/bin/Debug/clang-cc.exe" -triple i686-pc-win32 -S
-disable-free -main-file-name 2009-10-20-GlobalDebug.c --relocation-model
static --disable-fp-elim --asm-verbose --unwind-tables=0 --fmath-errno=1 -v
-g -fexceptions=0 -fdiagnostics-show-option -triple=i686-pc-linux-gnu -o -
-x c C:\Tools\llvm\tools\clang\test\CodeGen\2009-10-20-GlobalDebug.c
clang-cc.exe: for the -triple option: may only occur zero or one times!

Command 1: "FileCheck"
"C:\Tools\llvm\tools\clang\test\CodeGen\2009-10-20-GlobalDebug.c"
Command 1 Result: 1
Command 1 Output:

Command 1 Stderr:
C:\Tools\llvm\tools\clang\test\CodeGen\2009-10-20-GlobalDebug.c:3:52: error:
expected string not found in input
// CHECK: asciz "global" ## DW_AT_MIPS_linkage_name
                                                   ^
<stdin>:1:1: note: scanning from here
^

--
Command Output (stderr):
--
--

On Wed, Oct 21, 2009 at 10:54 AM, Douglas Gregor <dgregor at apple.com> wrote:

>
> On Oct 21, 2009, at 9:31 AM, Devang Patel wrote:
>
>
>> On Oct 21, 2009, at 5:38 AM, John Thompson wrote:
>>
>> Devang,
>>>
>>> On Windows, the 2009-10-20-GlobalDebug.c test fails.  Is it because debug
>>> info is not yet supported on Windows?
>>>
>>
>> Is that the real reason ? I do not know.
>>
>> If so, how could this test be set up to not fail?
>>>
>>
>> Is it possible to xfail or xtarget this test ?
>>
>
> You could just force the triple...
>
>        - Doug
>



-- 
John Thompson
John.Thompson.JTSoftware at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20091021/450c66e6/attachment.html>