dg-skip-if on powerpc when multiple cpu cflags specified

[Joel Sherrill]

Janis Johnson wrote:
> On Thu, 2008-04-24 at 17:54 -0500, Joel Sherrill wrote:
>
>   
>> Not knowing the internal details of the test harness, I
>> would make an ignorant guess that the command line
>> should be checked before it is executed.  If it has multiple
>> -mcpu/-march options and they were not all the same, the
>> test should be skipped.
>>
>> Is that kind of the logic we need even if the implementation
>> is way off?
>>     
>
> When you put it that way it sounds very simple!  
It is easy to say. :-D
> Something like
>
> /* { dg-options "-mcpu=xxx" } */
> /* { dg-skip-if-incompatible-options } */
>
> where dg-skip-if-incompatible-options starts out by looking for
> multiple instances of non-identical -mcpu= or -march= and then
> gets refined over time.  There's already code in check_flags in
> target-supports-dg.exp to gather together all the various flags
> that will be used for a test.
>
>   
This will involve editing every test that using dg-options
to add a -mcpu/-march flag.  Would it make sense to let
dg-options check for the conflict as it adds an option?

In my case, the options are added in the board file
this way:

set_board_info cflags  "-B${RTEMS_MAKEFILE_PATH}/lib/ -specs bsp_specs 
-qrtems -mcpu=603e"

> I'll investigate.
>
>   
Thanks. This is really a precision fix. :-D
> Janis
>
>   


-- 
Joel Sherrill, Ph.D.             Director of Research & Development
joel.sherrill@OARcorp.com        On-Line Applications Research
Ask me about RTEMS: a free RTOS  Huntsville AL 35805
   Support Available             (256) 722-9985