public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Bart Verwilst <verwilst@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Re: GCC3.1 bootstrap fails
Date: Sun, 2 Jun 2002 23:32:09 +0200	[thread overview]
Message-ID: <200206022332.09275.verwilst@gentoo.org> (raw)
In-Reply-To: <Pine.HPX.4.10.10206022302370.11141-100000@bhaskar.cc.iitk.ac.in>

Would be cool if you could try and bootstrap again with -fomit-frame-pointer, 
and now use the 1.3-gcc3.1 tarball from ibiblio 
(http://www.ibiblio.org/gentoo/releases/build/) i just made. If it fails, i 
guess we should filter out most of the optimisations... I think the new 
gcc3.1-compiled tarball will make all the gcc3.1-users much happier :o)
I also updated the packages file from the gcc 3.1 profile, and the 
make.defaults. Please keep us posted on any progress!

Thanks!


On Sunday 02 June 2002 19:42, Prashanth Aditya Susarla wrote:
|| >do -not- use  -fomit-frame-pointer during bootstrap! (can anyone who
|| >actually got this to -work- using omit-frame-pointer speak up??)
|| >
|| >This causes breakage in glibc.
||
|| That's interesting. When I used default-1.0, I used all the flags which
|| one particular FAQ on gentoo.org mentioned (-fforce-addr
|| -fomit-frame-pointer -funroll-loops blah blah blah along with -march=i686
|| -O3 of course) and everything worked fine (atleast compiled fine though I
|| was not truly happy with the performance (lots of memory leaks and
|| subsequent crashes of kswapd primarily). So maybe this is an issue only
|| with gcc-3.x and/or binutils-2.12.x. But I toned down the optimizations
|| and the bootstrap worked fine.
||
|| >this is due to a broken glibc (omit frame pointer and -O3. I think glibc
|| >strips out -O3 but  not the -f flags. )
||
|| gcc does this. glibc retains whatever you specify. Anyway, that's beside
|| the point - only for the sake of information ;-).
||
|| >> problem is that most binaries segfault soon after glibc is built.
|| >
|| >Try again with -O2 -pipe  and you will get a working system :)
||
|| Infact, I finally used the default options for Athlon systems (-march=i686
|| -pipe -O3.... not -O2 but -O3) and glibc didn't break. As I said earlier,
|| this is strange because all those crazy optimizations worked in the case
|| of the default-1.0 profile.
||
|| >emerge system
|| >/(watch it break down and cry in xfree because you overoptimized)
||
|| So you're saying that if I use -march=athlon-tbird -fomit-frame-pointer
|| -O3 [-pipe] -mmmx -m3dnow (the latter only for the sake of multimedia apps
|| like xmms, mplayer etc.) the xfree ebuild b0rks out? That's too bad,
|| really. And the thing with xfree is that experimenting stops being an
|| option if the very first emerge itself doesn't work :-(. Not all of us
|| have all the time in the world...
||
|| Regards,
|| Prashanth Aditya Susarla

-- 
Bart Verwilst
Gentoo Linux Developer, Desktop Team
Gent, Belgium


  reply	other threads:[~2002-06-02 21:38 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20020602170104.750B0AC465@chiba.3jane.net>
2002-06-02 17:42 ` [gentoo-dev] Re: GCC3.1 bootstrap fails Prashanth Aditya Susarla
2002-06-02 21:32   ` Bart Verwilst [this message]
2002-06-03  0:53     ` Prashanth Aditya Susarla
2002-06-03  1:18     ` Prashanth Aditya Susarla
2002-06-03  2:07       ` Prashanth Aditya Susarla
2002-06-03  3:52     ` Brian Webb
2002-06-03  6:04       ` Brian Webb
2002-06-03  5:59         ` Prashanth Aditya Susarla
2002-06-03  6:08           ` [gentoo-dev] Re: Correction - " Prashanth Aditya Susarla
2002-06-04 17:12           ` [gentoo-dev] " Matthew Kennedy
2002-06-03 16:49             ` Prashanth Aditya Susarla
2002-06-05  5:51               ` Christian Hergl
2002-06-04  6:05                 ` Prashanth Aditya Susarla
2002-06-04 17:13 Zaborowski, Ed, Ctr, AFPCA/OAC
2002-06-03 16:57 ` Prashanth Aditya Susarla
  -- strict thread matches above, loose matches on Subject: below --
2002-06-04 19:07 Zaborowski, Ed, Ctr, AFPCA/OAC
2002-06-03 18:42 ` Prashanth Aditya Susarla

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200206022332.09275.verwilst@gentoo.org \
    --to=verwilst@gentoo.org \
    --cc=gentoo-dev@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox