From: Ryan Hill <dirtyepic@gentoo.org>
To: gentoo-dev@gentoo.org, gentoo-dev-announce@gentoo.org
Subject: [gentoo-dev] GCC 4.6.0
Date: Sat, 2 Apr 2011 22:11:12 -0600 [thread overview]
Message-ID: <20110402221112.2101b4c1@gentoo.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1287 bytes --]
I just added 4.6.0 to the tree. We probably won't be unmasking it any time
soon (after 4.6.1 for sure), but please start testing your packages now so we
can get things rolling.
http://gcc.gnu.org/gcc-4.6/changes.html
For general testing you may want to add the gcc-porting overlay to avoid
known failures that haven't been fixed in the tree yet.
Outstanding issues I know about:
- hardened is broken (stage comparison mismatch)
- sys-boot/grub-0.97 is miscompiled (bug #360513)
https://overlays.gentoo.org/proj/gcc-porting/browser/README-4.6
Common errors:
https://overlays.gentoo.org/proj/gcc-porting/browser/ERRORS-4.6
http://lists.fedoraproject.org/pipermail/devel/2011-February/148523.html
You may also want to test your packages with the new -Ofast option to be
sure it doesn't have any hardcoded assumptions about -O flags.
Please assign any bugs you find in GCC itself to toolchain, and any bugs in
packages to their respective maintainers with a block on "gcc-4.6" (ie. bug
#346809).
--
fonts, gcc-porting, it makes no sense how it makes no sense
toolchain, wxwidgets but i'll take it free anytime
@ gentoo.org EFFD 380E 047A 4B51 D2BD C64F 8AA8 8346 F9A4 0662
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next reply other threads:[~2011-04-03 4:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-03 4:11 Ryan Hill [this message]
2011-04-03 5:50 ` [gentoo-dev] Re: GCC 4.6.0 Duncan
2011-04-03 10:19 ` Ryan Hill
2011-04-03 14:04 ` Mike Frysinger
2011-04-03 16:31 ` Branko Badrljica
2011-04-03 17:29 ` Chí-Thanh Christopher Nguyễn
2011-04-03 14:56 ` [gentoo-dev] " Andreas K. Huettel
2011-04-03 17:31 ` Mike Frysinger
2011-04-06 1:37 ` [gentoo-dev] " Diego Elio Pettenò
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=20110402221112.2101b4c1@gentoo.org \
--to=dirtyepic@gentoo.org \
--cc=gentoo-dev-announce@gentoo.org \
--cc=gentoo-dev@gentoo.org \
--cc=gentoo-dev@lists.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