From: Dhruba Bandopadhyay <dhruba@codewordt.co.uk>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] [WIP] gcc 3.3
Date: 16 May 2003 13:00:53 +0100 [thread overview]
Message-ID: <1053086453.22966.10.camel@wolf.codewordt.co.uk> (raw)
In-Reply-To: <20030516022031.57157e45.spider@gentoo.org>
On Fri, 2003-05-16 at 01:20, Spider wrote:
> hi folks,
> here is an initial ebuild of gcc 3.3, it doesn't contain propolice
> patch, and I haven't checked it with "build" or other flags except the
> default. (its slow to build on this machine)
There is an ebuild for it on bugzilla and one here and some on forums
too. Have you used any of these as a definitive base or is this a new
creation?
Also, is there any sign of this being entered into hardmasked or testig
state on portage?
I'd be quite keen on testing it out since I have had my fair share of
pentium4 problems and am desperately hoping an upgrade of gcc will sort
them out.
Pardon my ignorance but have all these patches been commented out to
prevent resultant problems or because they are no longer necessary?
Also, as a short note to those devs making a cflags guide to say that
the optimisation options have changed somewhat for gcc 3.3; an example
being -fomit-frame-pointer is now enabled by -O3 (taken from online
manual).
With regards
Dhruba Bandopadhyay
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-05-16 12:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-16 0:20 [gentoo-dev] [WIP] gcc 3.3 Spider
2003-05-16 0:24 ` Spider
2003-05-16 0:32 ` Spider
2003-05-16 12:00 ` Dhruba Bandopadhyay [this message]
2003-05-16 14:20 ` Spider
2003-05-16 15:38 ` David Nielsen
2003-05-16 15:38 ` David Nielsen
2003-05-16 19:58 ` Martin Schlemmer
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=1053086453.22966.10.camel@wolf.codewordt.co.uk \
--to=dhruba@codewordt.co.uk \
--cc=gentoo-dev@gentoo.org \
--cc=gentoo-user@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