public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Prashanth Aditya Susarla <aditya@iitk.ac.in>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Re: GCC3.1 bootstrap fails
Date: Mon, 3 Jun 2002 11:29:40 +0530 (IST)	[thread overview]
Message-ID: <Pine.LNX.4.44.0206031123220.2390-100000@thunderbird.junta.iitk.ac.in> (raw)
In-Reply-To: <36846.192.168.0.6.1023084252.squirrel@web.local>

I've managed to get a working system up and running on gcc-3.1. I used the 
1.3-gcc3.1 stage1 tarball with the following optimizations:-
-march=athlon-tbird -mmmx -m3dnow -O3 -pipe (no -fomit-frame-pointer). The 
mmx and 3dnow flags are obviously only cosmetic at this stage but there 
was no problem with -O3.
There was that problem with xfree, which I could solve by using 
-march=i686 -O3 -pipe (again no -fomit-frame-pointer and -O3 caused no 
problems).
Since -fomit-frame-pointer used to work everywhere with gcc-2..95.x, I 
find it somewhat strange that it should b0rk out with gcc-3.1. It's maybe 
because of changes in the compiler itself, or maybe because of the 
software itself - which the earlier compiler let through without any fuss.
The second looks more likely because my regular optimization flags (for 
the system builds as well as world builds) are -march=-athlon-tbird -mmmx 
-m3dnow -O3 -pipe -fomit-frame-pointer and there's absolutely no problem.
I have yet to compile  qt and kde and going by what I've seen about these 
builds vis-a-vis gcc 3.1 I just might have to go easy again on the 
optimization flags a bit (like I did for xfree).

Regards,
Prashanth Aditya Susarl

On Sun, 2 Jun 2002, Brian Webb wrote:

> I think I may have found at least part of the problem.  I noticed that on
> my other gcc-3.0 profile machines, texinfo couldn't be emerged.  It turns
> out that texinfo is masked.  Texinfo is a required system package in the
> gcc-3.0 profile and it's masked the package.mask, which obviously is not a
> good thing.  If I unmask texinfo my existing systems are happy, but I
> haven't tested it on a bootstrap yet.
> 
> Brian
> 
> 
> P.S. Sorry about the run-on emails.  I really have to figure out why
> Squirrelmail is running all my paragraphs together!!!!



  reply	other threads:[~2002-06-04  6:54 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
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 [this message]
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=Pine.LNX.4.44.0206031123220.2390-100000@thunderbird.junta.iitk.ac.in \
    --to=aditya@iitk.ac.in \
    --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