--- Comment #53 from janis at gcc dot gnu dot org 2009-02-09 17:22 ---
Rob, you don't seem to understand that setting GCC_EXEC_PREFIX does NOT cause
the tests to use GCC files from the install tree. The test framework
explicitly uses -B options to override GCC_EXEC_PREFIX, so the only e
--- Comment #52 from rob1weld at aol dot com 2009-02-07 06:00 ---
(In reply to comment #48)
> Subject: Re: [4.3/4.4 Regression]: HOSTCC doesn't work
> with installed gcc
>
> rob1weld at aol dot com wrote:
> > One example is inherently derived from where we see it being set (wrongly),
--- Comment #51 from janis at gcc dot gnu dot org 2009-02-06 19:30 ---
Mark pointed out way back in comment #9 that GCC used to effectively do the
same thing by searching the install directory even without GCC_EXEC_PREFIX. I
understand that setting it makes people nervous, but I haven't
--- Comment #50 from mark at codesourcery dot com 2009-02-06 19:22 ---
Subject: Re: [4.3/4.4 Regression]: HOSTCC doesn't work
with installed gcc
hjl dot tools at gmail dot com wrote:
> For most people, GCC_EXEC_PREFIX points to either a directory which
> doesn't exist or a different
--- Comment #49 from hjl dot tools at gmail dot com 2009-02-06 19:15
---
For most people, GCC_EXEC_PREFIX points to either a directory which
doesn't exist or a different version of gcc. Since GCC_EXEC_PREFIX
may point a directory which doesn't exist, it isn't really needed
by "make chec
--- Comment #48 from mark at codesourcery dot com 2009-02-06 18:35 ---
Subject: Re: [4.3/4.4 Regression]: HOSTCC doesn't work
with installed gcc
rob1weld at aol dot com wrote:
> One example is inherently derived from where we see it being set (wrongly),
> during "make -i check" _PRIO
--- Comment #47 from rob1weld at aol dot com 2009-02-05 04:06 ---
(In reply to comment #46)
> As I understand it, the complaint here is that GCC_EXEC_PREFIX being set
> affects HOSTCC, when HOSTCC is itself some other GCC. ...
It is true (for most of us in this thread) that "GCC_EXEC_PR
--- Comment #46 from mmitchel at gcc dot gnu dot org 2009-02-02 22:00
---
As I understand it, the complaint here is that GCC_EXEC_PREFIX being set
affects HOSTCC, when HOSTCC is itself some other GCC.
But, we have to make sure that the newly built compiler searches the right
directory.
--- Comment #45 from rob1weld at aol dot com 2009-01-31 22:13 ---
Here is another attempt using "gcc version 4.4.0 20090128 (experimental) [trunk
revision 143729]" to compile "gcc version 4.4.0 20090131 (experimental) [trunk
revision 143817]".
I have an Athlon X2 running OpenSolaris in
--- Comment #44 from rob1weld at aol dot com 2009-01-29 23:12 ---
(In reply to comment #43)
> Rob, your various assertions do not show that there is a bug here. ...
...
> I built GCC from 20090106, broke a couple of thing affecting cc1, float.h, and
> libgcc.a, and installed it. Then I
--- Comment #43 from janis at gcc dot gnu dot org 2009-01-29 22:36 ---
Rob, your various assertions do not show that there is a bug here. The failure
of gcc.target/i386/funcspec-3.c described in comment #41 does not prove that
the compiler under test is using GCC files from the install
--- Comment #42 from janis at gcc dot gnu dot org 2009-01-29 18:32 ---
I'm looking into this. It's all very messy and confusing, so I'm trying to
step back and understand the big picture.
Is there a reason that GCC_EXEC_PREFIX is set to $(libdir)/gcc/ for the
compiler tests but not for
--- Comment #41 from rob1weld at aol dot com 2009-01-29 15:01 ---
(In reply to comment #35)
> In response to comment #34, the -B option overrides GCC_EXEC_PREFIX and the
> compiler being tested in the build directory is invoked with -B.
> GCC_EXEC_PREFIX will only be used to find files
--- Comment #40 from rob1weld at aol dot com 2009-01-28 13:52 ---
Notes from 38820: I had "Known to fail" set to 4.4.0 4.3.2
Another 'proof' this is a Bug.
You are allowed to build GCC after you set (reasonable) Environment
variables. Examples are:
export set CC="gcc -v"
export set CC=
--- Comment #39 from rob1weld at aol dot com 2009-01-28 03:08 ---
H.J. Lu,
This comment ( http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14435#c25 ) requests
that Bug Report be modified "restore to P3 if it affects non-Ada testsuites
or any case where the compiler exports GCC_EXEC_PREFIX i
--- Comment #38 from rob1weld at aol dot com 2009-01-27 21:32 ---
Clearly, it is wrong:
# locate crtprec80.o
/mnt/drive2/gcc_build/gcc/crtprec80.o
/mnt/drive2/gcc_build/i386-redhat-linux/libgcc/crtprec80.o
/mnt/drive2/gcc_build/prev-gcc/crtprec80.o
/mnt/drive2/gcc_build/prev-i386-redhat
--- Comment #37 from rob1weld at aol dot com 2009-01-27 21:26 ---
(In reply to comment #20)
> (In reply to comment #19)
> > Subject: Re: [4.3/4.4 Regression]: HOSTCC doesn't work
> > with installed gcc
> > hjl dot tools at gmail dot com wrote:
> > > They sound to me the ideal usage for
--- Comment #36 from rob1weld at aol dot com 2009-01-27 21:12 ---
(In reply to comment #33)
*** Bug 38820 has been marked as a duplicate of this bug. ***
(In reply to comment #34)
> If I have an old gcc 4.4 installed on my machine, will setting
> GCC_EXEC_PREFIX use the old installed gcc
--- Comment #35 from janis at gcc dot gnu dot org 2009-01-27 18:45 ---
In response to comment #34, the -B option overrides GCC_EXEC_PREFIX and the
compiler being tested in the build directory is invoked with -B.
GCC_EXEC_PREFIX will only be used to find files that are not in the build
d
--- Comment #34 from hjl dot tools at gmail dot com 2009-01-27 16:06
---
If I have an old gcc 4.4 installed on my machine, will setting
GCC_EXEC_PREFIX use the old installed gcc 4.4 for "make check"?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36443
--- Comment #33 from hjl dot tools at gmail dot com 2009-01-27 15:54
---
I think it is a very bad idea to set GCC_EXEC_PREFIX for "make check".
If some people want binary tools, which aren't the part of installed gcc,
in the GCC_EXEC_PREFIX directory when running "make check", they
shou
--- Comment #32 from hjl dot tools at gmail dot com 2009-01-27 15:48
---
*** Bug 38820 has been marked as a duplicate of this bug. ***
--
hjl dot tools at gmail dot com changed:
What|Removed |Added
-
--- Comment #31 from hjl at gcc dot gnu dot org 2009-01-26 18:14 ---
Subject: Bug 36443
Author: hjl
Date: Mon Jan 26 18:13:58 2009
New Revision: 143681
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=143681
Log:
2009-01-26 H.J. Lu
Backport from mainline:
2008-
--- Comment #30 from rguenth at gcc dot gnu dot org 2009-01-24 10:20
---
GCC 4.3.3 is being released, adjusting target milestone.
--
rguenth at gcc dot gnu dot org changed:
What|Removed |Added
--
--- Comment #29 from jsm28 at gcc dot gnu dot org 2008-08-27 22:04 ---
4.3.2 is released, changing milestones to 4.3.3.
--
jsm28 at gcc dot gnu dot org changed:
What|Removed |Added
---
--- Comment #28 from hjl at gcc dot gnu dot org 2008-07-17 05:14 ---
Subject: Bug 36443
Author: hjl
Date: Thu Jul 17 05:13:27 2008
New Revision: 137909
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=137909
Log:
2008-07-17 H.J. Lu <[EMAIL PROTECTED]>
PR testsuite/36443
--- Comment #27 from pinskia at gcc dot gnu dot org 2008-07-15 14:41
---
(In reply to comment #26)
> Don't we need the same workaround in
Yes.
I can confirm this with 4.3.0.
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
-
--- Comment #26 from hjl dot tools at gmail dot com 2008-06-12 12:33
---
Don't we need the same workaround in
./objc.dg/gnu-encoding/gnu-encoding.exp:set status [remote_exec host "$HOSTCC
$HOSTCFLAGS $generator_cmd"]
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36443
--- Comment #25 from jakub at gcc dot gnu dot org 2008-06-12 11:41 ---
Committed patch Janis approved as temporary solution.
--
jakub at gcc dot gnu dot org changed:
What|Removed |Added
--
--- Comment #24 from jakub at gcc dot gnu dot org 2008-06-12 11:39 ---
Subject: Bug 36443
Author: jakub
Date: Thu Jun 12 11:38:55 2008
New Revision: 136700
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=136700
Log:
PR testsuite/36443
* gcc.dg/compat/struct-layout
--- Comment #23 from jakub at gcc dot gnu dot org 2008-06-12 11:17 ---
Subject: Bug 36443
Author: jakub
Date: Thu Jun 12 11:17:05 2008
New Revision: 136698
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=136698
Log:
PR testsuite/36443
* gcc.dg/compat/struct-layout
--
jsm28 at gcc dot gnu dot org changed:
What|Removed |Added
Target Milestone|--- |4.3.2
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36443
--- Comment #22 from hjl dot tools at gmail dot com 2008-06-10 05:49
---
(In reply to comment #21)
> Subject: Re: [4.3/4.4 Regression]: HOSTCC doesn't work
> with installed gcc
>
> hjl dot tools at gmail dot com wrote:
>
> >>> --syroot supports libraries and headers. Does it suppor
--- Comment #21 from mark at codesourcery dot com 2008-06-10 05:02 ---
Subject: Re: [4.3/4.4 Regression]: HOSTCC doesn't work
with installed gcc
hjl dot tools at gmail dot com wrote:
>>> --syroot supports libraries and headers. Does it support
>>> assembler and linker?
>> Not as far
--- Comment #20 from hjl dot tools at gmail dot com 2008-06-10 01:45
---
(In reply to comment #19)
> Subject: Re: [4.3/4.4 Regression]: HOSTCC doesn't work
> with installed gcc
>
> hjl dot tools at gmail dot com wrote:
>
> > They sound to me the ideal usage for --sysroot. They aren'
--- Comment #19 from mark at codesourcery dot com 2008-06-10 00:38 ---
Subject: Re: [4.3/4.4 Regression]: HOSTCC doesn't work
with installed gcc
hjl dot tools at gmail dot com wrote:
> They sound to me the ideal usage for --sysroot. They aren't from
> gcc and they don't change from o
--- Comment #18 from hjl dot tools at gmail dot com 2008-06-09 23:58
---
(In reply to comment #17)
> Subject: Re: [4.3/4.4 Regression]: HOSTCC doesn't work
> with unstalled gcc
>
> hjl dot tools at gmail dot com wrote:
> > --- Comment #16 from hjl dot tools at gmail dot com 2008
--- Comment #17 from mark at codesourcery dot com 2008-06-09 21:16 ---
Subject: Re: [4.3/4.4 Regression]: HOSTCC doesn't work
with unstalled gcc
hjl dot tools at gmail dot com wrote:
> --- Comment #16 from hjl dot tools at gmail dot com 2008-06-09 14:16
> ---
> (In reply to
38 matches
Mail list logo
