[llvm-commits] [llvm-gcc-4.2] r48905 - /llvm-gcc-4.2/trunk/gcc/testsuite/g++.dg/debug/debug.exp

Dale Johannesen dalej at apple.com
Fri Mar 28 10:01:35 PDT 2008


On Mar 28, 2008, at 9:54 AM, Dale Johannesen wrote:

>
> On Mar 28, 2008, at 9:43 AM, Devang Patel wrote:
>
>>
>> On Mar 27, 2008, at 10:27 PM, Chris Lattner wrote:
>>
>>> On Mar 27, 2008, at 5:31 PM, Devang Patel wrote:
>>>> Author: dpatel
>>>> Date: Thu Mar 27 19:31:45 2008
>>>> New Revision: 48905
>>>>
>>>> URL: http://llvm.org/viewvc/llvm-project?rev=48905&view=rev
>>>> Log:
>>>> Disable optimized code debug info tests for now.
>>>
>>> My understanding is that this will disable the test even if -- 
>>> enable-
>>> llvm is not passed when configuring llvm-gcc.
>>
>> Yes, I did not think about it.
>>
>>> Is there any way to
>>> disable the tests just for llvm-gcc but not normal gcc?
>>
>> I don't know.
>
> What I've been doing so far is make test disabling dependent on  
> is_llvm,
> see e.g. gcc.dg/vect/vect.exp.  Right now is_llvm is always true  
> (defined in
> lib/target-supports.exp).  I figure if somebody cares they will add  
> something
> that allows them to turn it off, but I don't know how to do that.

I've also been adding predicates for classes of tests that llvm  
doesn't support
in target-supports-dg.exp, e.g. dg-require-fdump, so that if we decide  
to implement
these features, it will be clean to reenable the tests.  I'd suggest  
something
like dg-require-optimized-debug for this.  (dg-require-stabs would be  
another
good one.)

>> Is there anyone out there with enough dejagnu/tcl/gcc build script
>> knowledge knowledge to produce a  patch that disable these tests only
>> when llvm-gcc is configured using --enable-llvm=<blah> ?
>>
>> -
>> Devang
>>
>>
>>
>> _______________________________________________
>> llvm-commits mailing list
>> llvm-commits at cs.uiuc.edu
>> http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits
>




More information about the llvm-commits mailing list