From: "Diego Elio Pettenò" <flameeyes@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: GCC 4.6 unmasking
Date: Sun, 25 Sep 2011 15:10:13 +0200 [thread overview]
Message-ID: <1316956213.4375.47.camel@raven.home.flameeyes.eu> (raw)
In-Reply-To: <20110923203832.5c922e8e@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 541 bytes --]
Il giorno ven, 23/09/2011 alle 20.38 -0600, Ryan Hill ha scritto:
> If you have any issues with 4.6 itself or patches you need applied,
> now is
> the time to speak up.
There should be already a bug open about valgrind: even when _not_ using
DWARF-4 (which breaks binutils, btw) the new gcc uses new DWARF
instructions that are not supported even by the ~arch version. We need
either to get upstream to release a new version or we should patch
it/snapshot it.
--
Diego Elio Pettenò — Flameeyes
http://blog.flameeyes.eu/
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2011-09-25 13:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-24 2:38 [gentoo-dev] GCC 4.6 unmasking Ryan Hill
2011-09-25 13:10 ` Diego Elio Pettenò [this message]
2011-09-26 2:18 ` [gentoo-dev] " Ryan Hill
2011-10-30 21:22 ` Ryan Hill
2011-11-12 2:50 ` Ryan Hill
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=1316956213.4375.47.camel@raven.home.flameeyes.eu \
--to=flameeyes@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