public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ryan Hill <dirtyepic@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: GCC 4.6 unmasking
Date: Sun, 25 Sep 2011 20:18:59 -0600	[thread overview]
Message-ID: <20110925201859.59ba52f8@gentoo.org> (raw)
In-Reply-To: 1316956213.4375.47.camel@raven.home.flameeyes.eu

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

On Sun, 25 Sep 2011 15:10:13 +0200
Diego Elio Pettenò <flameeyes@gentoo.org> wrote:

> 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.

Hmm, I don't see any bugs open that cover that.  The support is upstream
already? 

I think we should also consider bumping the minimum glibc version to 2.12
now that it's stable. I know it's a pain in the ass but anything older than
that just plain doesn't work anymore.

-- 
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 --]

  reply	other threads:[~2011-09-26  2: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 ` [gentoo-dev] " Diego Elio Pettenò
2011-09-26  2:18   ` Ryan Hill [this message]
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=20110925201859.59ba52f8@gentoo.org \
    --to=dirtyepic@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