On 03/11/14 18:36, Mike Stump wrote:
On Oct 30, 2014, at 10:25 AM, Andrew Stubbs wrote:
Many of the tests in gcc.target/powerpc specify an explicit -mcpu option with
dg-options. This is a problem for multilib configurations that use -mcpu in
their definition
OK to commit?
Given the discu
On Oct 30, 2014, at 10:25 AM, Andrew Stubbs wrote:
> Many of the tests in gcc.target/powerpc specify an explicit -mcpu option with
> dg-options. This is a problem for multilib configurations that use -mcpu in
> their definition
> OK to commit?
Given the discussion, I think the patch as is is f
On 30/10/14 18:37, Mike Stump wrote:
On Oct 30, 2014, at 10:25 AM, Andrew Stubbs
wrote:
Many of the tests in gcc.target/powerpc specify an explicit -mcpu
option with dg-options.
So, I think this isn’t the strategy people like for this sort of
thing. The problem is default flags. You can hav
On Oct 30, 2014, at 10:25 AM, Andrew Stubbs wrote:
> Many of the tests in gcc.target/powerpc specify an explicit -mcpu option with
> dg-options.
So, I think this isn’t the strategy people like for this sort of thing. The
problem is default flags. You can have a certain cpu as a target but no
Many of the tests in gcc.target/powerpc specify an explicit -mcpu option
with dg-options. This is a problem for multilib configurations that use
-mcpu in their definition; the test commands will list both -mcpu
options, with the multilib option overriding the test option. This
causes many bogus
