public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ned Ludd <solar@gentoo.org>
To: Daniel Goller <morfic@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] GCC 3.4 and ~x86
Date: Sat, 11 Sep 2004 15:50:29 -0400	[thread overview]
Message-ID: <1094932229.2092.43.camel@simple> (raw)
In-Reply-To: <4143476D.5070207@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1074 bytes --]

On Sat, 2004-09-11 at 14:43, Daniel Goller wrote:
> GCC 3.4 should be ready to go ~x86 w/o being profile masked in x86 
> profiles anymore.
> There are no critical packages that dont compile with it.
> If anyone sees a reason to not unmask it, let me know, otherwise we 
> would like to unamsk it soon.

Ideally I'd like to see us get all arches that can use gcc-3.4 on it and
in stable for the next release cycle. So this ~x86 unmask in profiles 
has my blessing. Works best when used in tandem with >=binutils-2.15
(feature wise)

Users that experience failures of gcc/binutils/libc compiling itself
should send any bugs toolchain@g.o
Usually this is only limited the users with buggy athlon{,-xp} hardware
that ever seem to have problems.

Programs that fail to compile with 3.4.x that previously compiled with
3.3.4 should be routed to gcc-porting@g.o and package maintainers
respectively.

> 
> 
> --
> gentoo-dev@gentoo.org mailing list
-- 
Ned Ludd <solar@gentoo.org>
Gentoo (hardened,security,infrastructure,embedded,toolchain) Developer

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2004-09-11 19:50 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-11 18:43 [gentoo-dev] GCC 3.4 and ~x86 Daniel Goller
2004-09-11 19:31 ` Ioannis Aslanidis
2004-09-11 20:30   ` Daniel Goller
2004-09-11 19:50 ` Ned Ludd [this message]
2004-09-11 23:09   ` Daniel Goller
2004-09-12  0:08 ` Alberto Garcia Hierro
2004-09-12  0:24   ` Robert Moss
2004-09-13 19:12     ` Paul de Vrieze
2004-09-12 15:25   ` Norberto Bensa
2004-09-13 23:58     ` Stefan Jones
2004-09-14  5:54       ` Norberto Bensa
  -- strict thread matches above, loose matches on Subject: below --
2004-09-12 23:49 Patrick Dawson
2004-09-13  0:24 ` Mike Frysinger
2004-09-13  0:33   ` Daniel Goller
2004-09-13  3:51     ` Luke-Jr
2004-09-13  4:30       ` Daniel Goller
2004-09-13  5:51         ` Seemant Kulleen
2004-09-13 19:20       ` Paul de Vrieze
2004-09-13 22:00         ` Mike Frysinger
2004-09-14  8:54           ` Paul de Vrieze
2004-09-15  8:21           ` Paul de Vrieze
2004-09-15 14:54             ` Mike Frysinger
2004-09-18  7:44             ` Ned Ludd
2004-09-18  9:09               ` Robert Moss
2004-09-18 15:02                 ` Daniel Goller
2004-09-18 15:21                   ` Robert Moss
2004-09-19  3:20                   ` Donnie Berkholz
2004-09-19  3:27                     ` Ned Ludd
2004-09-19  8:01                       ` Stuart Herbert
2004-09-19 15:22                     ` Paul de Vrieze
2004-09-18 18:40                 ` Travis Tilley
2004-09-13 19:54 ` Joshua J. Berry
2004-09-13 22:02   ` Mike Frysinger
2004-09-14 13:57     ` Mike Frysinger

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=1094932229.2092.43.camel@simple \
    --to=solar@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=morfic@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