failures in gcc tests when multiple cpu cflags specified

Hi,

Janis wanted a recap on this list.  The thread
starts here:

http://gcc.gnu.org/ml/gcc/2008-04/msg00587.html

And this is the last message in the thread which
sums up the expert views:

http://gcc.gnu.org/ml/gcc/2008-04/msg00708.html

The latest powerpc-rtems4.10 GCC test results
are here:

http://gcc.gnu.org/ml/gcc-testresults/2008-12/msg01477.html

The tests in question are "scan-assembler" and
other tests which specify a particular -mcpu option
which conflicts with those used by the particular
target hardware we are running on.

So for example, a test may try to verify that
gcc generates a particular instruction on a
ppc405.  But the specific board cflags
are explicitly selecting another -mcpu so the
code can actually work on the target board.

--
Joel Sherrill, Ph.D.             Director of Research & Development
joel.sherrill@...        On-Line Applications Research
Ask me about RTEMS: a free RTOS  Huntsville AL 35805
   Support Available             [phone]




_______________________________________________
DejaGnu mailing list
DejaGnu@...
http://lists.gnu.org/mailman/listinfo/dejagnu

[Janis Johnson]

On Wed, 2008-12-17 at 16:05 -0600, Joel Sherrill wrote:

> Hi,
>
> Janis wanted a recap on this list.  The thread
> starts here:
>
> http://gcc.gnu.org/ml/gcc/2008-04/msg00587.html
>
> And this is the last message in the thread which
> sums up the expert views:
>
> http://gcc.gnu.org/ml/gcc/2008-04/msg00708.html
>
> The latest powerpc-rtems4.10 GCC test results
> are here:
>
> http://gcc.gnu.org/ml/gcc-testresults/2008-12/msg01477.html
>
> The tests in question are "scan-assembler" and
> other tests which specify a particular -mcpu option
> which conflicts with those used by the particular
> target hardware we are running on.
>
> So for example, a test may try to verify that
> gcc generates a particular instruction on a
> ppc405.  But the specific board cflags
> are explicitly selecting another -mcpu so the
> code can actually work on the target board.

I'll take another look at this.  It probably needs to be solved
within the GCC testsuite support rather than in DejaGnu.

Janis



_______________________________________________
DejaGnu mailing list
DejaGnu@...
http://lists.gnu.org/mailman/listinfo/dejagnu

Janis Johnson wrote:

> On Wed, 2008-12-17 at 16:05 -0600, Joel Sherrill wrote:
>  
>> Hi,
>>
>> Janis wanted a recap on this list.  The thread
>> starts here:
>>
>> http://gcc.gnu.org/ml/gcc/2008-04/msg00587.html
>>
>> And this is the last message in the thread which
>> sums up the expert views:
>>
>> http://gcc.gnu.org/ml/gcc/2008-04/msg00708.html
>>
>> The latest powerpc-rtems4.10 GCC test results
>> are here:
>>
>> http://gcc.gnu.org/ml/gcc-testresults/2008-12/msg01477.html
>>
>> The tests in question are "scan-assembler" and
>> other tests which specify a particular -mcpu option
>> which conflicts with those used by the particular
>> target hardware we are running on.
>>
>> So for example, a test may try to verify that
>> gcc generates a particular instruction on a
>> ppc405.  But the specific board cflags
>> are explicitly selecting another -mcpu so the
>> code can actually work on the target board.
>>    
>
> I'll take another look at this.  It probably needs to be solved
> within the GCC testsuite support rather than in DejaGnu.
>  

OK.  Thank you.  Maybe you will have some insight
that no one came to earlier this year.

--joel


_______________________________________________
DejaGnu mailing list
DejaGnu@...
http://lists.gnu.org/mailman/listinfo/dejagnu