On Fri, Feb 13, 2015 at 8:47 AM, Joseph Myers wrote:
> On Fri, 13 Feb 2015, H.J. Lu wrote:
>
>> the end. This patch adds gcc_default_target_compile, which is
>> almost identical to default_target_compile in dejagnu, except that
>> it has
>
> Duplicating large piles of code from DejaGnu seems a ba
On Fri, 13 Feb 2015, H.J. Lu wrote:
> the end. This patch adds gcc_default_target_compile, which is
> almost identical to default_target_compile in dejagnu, except that
> it has
Duplicating large piles of code from DejaGnu seems a bad idea - it's bound
to cause problems when DejaGnu makes its o
PING
-- Forwarded message --
From: H.J. Lu
Date: Wed, Jan 29, 2014 at 8:18 AM
Subject: PR testsuite/59971: multilib_flags is placed with the wrong order
To: gcc-patches@gcc.gnu.org
Cc: r...@cebitec.uni-bielefeld.de, mikest...@comcast.net
Hi,
Some testcases need explicit GCC
Hi,
Some testcases need explicit GCC options to properly run, like
gcc.target/i386/sse2-init-v2di-2.c has
/* { dg-options "-O2 -msse4 -march=core2 -dp" } */
-march=core2 is specified explicitly. But with multlib, like
make check-gcc RUNTESTFLAGS="--target_board='unix{-march=k8}'
-march=k8 is
