[Bug driver/35532] Native GCC no longer searches $prefix/lib for startfiles when run from $objdir

2008-03-15 Thread gschafer at zip dot com dot au
--- Comment #7 from gschafer at zip dot com dot au 2008-03-16 06:41 --- (In reply to comment #6) > As a workaround can you try using all of the sysroot framework? Thanks for looking at this Carlos. But the sysroot stuff is not really suited to a non /usr layout. For example, with

[Bug driver/35532] Native GCC no longer searches $prefix/lib for startfiles when run from $objdir

2008-03-12 Thread gschafer at zip dot com dot au
--- Comment #5 from gschafer at zip dot com dot au 2008-03-12 11:26 --- (In reply to comment #4) > > The example you describe looks an awful lot like a cross-compile. No, it's definitely native. See below. > Is there > anything preventing you from configuring wi

[Bug driver/35532] Native GCC no longer searches $prefix/lib for startfiles when run from $objdir

2008-03-10 Thread gschafer at zip dot com dot au
--- Comment #3 from gschafer at zip dot com dot au 2008-03-10 22:52 --- (In reply to comment #2) > It is better to use -B $prefix/lib while building. -B doesn't work on multilib ie: -B $prefix/lib doesn't find $prefix/lib/../lib64 Not only that, I'm talking about GC

[Bug driver/35532] Native GCC no longer searches $prefix/lib for startfiles when run from $objdir

2008-03-10 Thread gschafer at zip dot com dot au
--- Comment #1 from gschafer at zip dot com dot au 2008-03-10 22:37 --- Created an attachment (id=15292) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=15292&action=view) Patch that restores old behaviour (for demonstration only) -- http://gcc.gnu.org/bugzilla/show_bug

[Bug driver/35532] New: Native GCC no longer searches $prefix/lib for startfiles when run from $objdir

2008-03-10 Thread gschafer at zip dot com dot au
on: 4.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: driver AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: gschafer at zip dot com dot au http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35532

[Bug target/35239] New: Build failure when host cc is GCC-2.95,3 or earlier

2008-02-17 Thread gschafer at zip dot com dot au
Version: 4.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: gschafer at zip dot com dot au GCC build triplet: i686-pc-linux-gnu GCC host triplet: i686-pc-linux-gnu GCC target triplet: i686-pc-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35239

[Bug driver/19353] Faulty handling of (some) user specified specs

2006-10-10 Thread gschafer at zip dot com dot au
--- Comment #7 from gschafer at zip dot com dot au 2006-10-11 06:18 --- The root cause of this bug is obvious after studying gcc.c. Essentially, the user specified specs are read _way_ too late in the process. The sequence is roughly this: 1 - search for default specs file, if found

[Bug libmudflap/23069] New: libmudflap.cth timeouts too short

2005-07-25 Thread gschafer at zip dot com dot au
tatus: UNCONFIRMED Severity: normal Priority: P2 Component: libmudflap AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: gschafer at zip dot com dot au CC: gcc-bugs at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.c

[Bug libmudflap/20003] libmudflap.cth

2005-07-25 Thread gschafer at zip dot com dot au
--- Additional Comments From gschafer at zip dot com dot au 2005-07-26 06:07 --- (In reply to comment #1) > Fixed at least in 4.0.1. No it's not. Please see these results for example (all from different folks): http://gcc.gnu.org/ml/gcc-testresults/2005-07/msg01370.h

[Bug target/14206] Mention that exec-shield-randomize (linux) conflicts with PCH

2005-07-19 Thread gschafer at zip dot com dot au
--- Additional Comments From gschafer at zip dot com dot au 2005-07-20 02:31 --- Stock Linux kernel 2.6.12 introduced "address space randimization" which appears to be essentially the same thing as RH's exec-shield-randomize. More info about this issue here: http://gcc

[Bug testsuite/21577] New: libstdc++ testsuite broken

2005-05-14 Thread gschafer at zip dot com dot au
Summary: libstdc++ testsuite broken Product: gcc Version: 3.4.4 Status: UNCONFIRMED Severity: normal Priority: P2 Component: testsuite AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: gschafer at zip dot com dot

[Bug middle-end/20635] [4.0 Regression] ICE in cgraph_mark_reachable_node

2005-03-29 Thread gschafer at zip dot com dot au
--- Additional Comments From gschafer at zip dot com dot au 2005-03-29 23:41 --- (In reply to comment #6) > I'll apply the patch and report back later if it fixes the problem. Would be > nice to get this applied on the 4.0 branch. Thanks. It did indeed fix the prob

[Bug middle-end/20635] [4.0/4.1 Regression] ICE in cgraph_mark_reachable_node

2005-03-28 Thread gschafer at zip dot com dot au
--- Additional Comments From gschafer at zip dot com dot au 2005-03-29 04:53 --- I just hit this trying to compile psmisc-21.6 with snapshot gcc-4.0-20050326: pstree.c: In function 'dump_tree': pstree.c:539: internal compiler error: in cgraph_mark_reachable_node, at cgraph.c

[Bug target/20166] Bootstrap failure due to lack of fixinclude of pthread problem

2005-02-23 Thread gschafer at zip dot com dot au
--- Additional Comments From gschafer at zip dot com dot au 2005-02-24 06:43 --- Here's the fix to pthread.h from Glibc cvs. I suppose the fixinclude "fix" would need to replicate this: http://sources.redhat.com/ml/glibc-cvs/2005-q1/msg00303.html -- http://gcc.g

[Bug target/20166] Bootstrap failure due to lack of fixinclude of pthread problem

2005-02-23 Thread gschafer at zip dot com dot au
--- Additional Comments From gschafer at zip dot com dot au 2005-02-24 04:39 --- This also happens for me on i686-pc-linux-gnu. It's a bog-standard unpatched NPTL-enabled glibc-2.3.4 system. I don't think it classifies as a "bad glibc". I concur that some fixi

[Bug driver/19353] Faulty handling of startfile_prefix_spec

2005-01-27 Thread gschafer at zip dot com dot au
--- Additional Comments From gschafer at zip dot com dot au 2005-01-27 21:39 --- The patch was approved by the RM here: http://gcc.gnu.org/ml/gcc-patches/2005-01/msg00850.html but it is still not applied. It would be great if you could pls commit this patch then close the BZ. Many

[Bug driver/19353] Faulty handling of startfile_prefix_spec

2005-01-11 Thread gschafer at zip dot com dot au
--- Additional Comments From gschafer at zip dot com dot au 2005-01-12 05:46 --- (In reply to comment #1) > Hmm, this SPEC should be removed from the mainline, it is unused in GCC at > all. Ok, good. I suppose removing faulty code is better then leaving it there for folks to (

[Bug driver/19353] New: Faulty handling of startfile_prefix_spec

2005-01-09 Thread gschafer at zip dot com dot au
bove technique and it works fine. I tried 3.4.3 and 4.0 and this bug is present in both. Thankyou -- Summary: Faulty handling of startfile_prefix_spec Product: gcc Version: 4.0.0 Status: UNCONFIRMED Severity: normal Priority: P2

[Bug bootstrap/19223] --disable-checking doesn't fully disable checking

2005-01-04 Thread gschafer at zip dot com dot au
--- Additional Comments From gschafer at zip dot com dot au 2005-01-05 00:19 --- Here are some timimgs from my test runs. This is all done with: --enable-languages=c --disable-checking make bootstrap gcc-4.014:50 gcc-4.012.25-> with STAGE1_CHECKING manually remo

[Bug bootstrap/19223] --disable-checking doesn't fully disable checking

2005-01-02 Thread gschafer at zip dot com dot au
--- Additional Comments From gschafer at zip dot com dot au 2005-01-02 22:27 --- > This is an urban legend. I agree with the above comment, but you've completely missed my point. With gcc-3.4.3, I can `make bootstrap' with --enable-languages=c and it takes 7:25. With gcc-

[Bug bootstrap/19223] --disable-checking doesn't fully disable checking

2005-01-01 Thread gschafer at zip dot com dot au
--- Additional Comments From gschafer at zip dot com dot au 2005-01-02 02:41 --- Like I said, fairynuff. But users will definitely notice slower bootstraps, thus further contributing to the perceived feeling that GCC is forever getting slower. It will be a shame IMHO. If the extra

[Bug bootstrap/19223] --disable-checking doesn't fully disable checking

2005-01-01 Thread gschafer at zip dot com dot au
--- Additional Comments From gschafer at zip dot com dot au 2005-01-02 02:30 --- Because it currently makes my bootstraps slow as molasses. Yes, stage 2 and 3 are fine. But I thought released compilers were meant to have checking switched off completely. If you release the compiler like

[Bug bootstrap/19223] --disable-checking doesn't fully disable checking

2005-01-01 Thread gschafer at zip dot com dot au
--- Additional Comments From gschafer at zip dot com dot au 2005-01-02 02:21 --- Fairynuff. As long as someone remembers to switch it off before release, because if not, it will then clearly be a bug. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19223

[Bug bootstrap/19223] New: --disable-checking doesn't fully disable checking

2005-01-01 Thread gschafer at zip dot com dot au
Product: gcc Version: 4.0.0 Status: UNCONFIRMED Severity: minor Priority: P2 Component: bootstrap AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: gschafer at zip dot com dot au CC: gcc-bugs at gcc dot gn

[Bug target/18910] [4.0 Regression] unrecognisable insn in regclass on x86/amd64

2004-12-31 Thread gschafer at zip dot com dot au
--- Additional Comments From gschafer at zip dot com dot au 2005-01-01 01:18 --- I've just hit this while trying to build Glibc with current GCC trunk. It's a showstopper. -- What|Removed