public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael Mol <mikemol@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] ~gcc-4.7.0
Date: Mon, 28 May 2012 22:26:43 -0400	[thread overview]
Message-ID: <CA+czFiCEnaYdOXgQs1c4FM6OZK6c7LONEVOpLbjusHfKm401Qg@mail.gmail.com> (raw)
In-Reply-To: <CAA2qdGUWE=zd9MopqDPV93+rN6CHwk+WcM0GBh5u9_=pshH7UA@mail.gmail.com>

On Mon, May 28, 2012 at 10:19 PM, Pandu Poluan <pandu@poluan.info> wrote:
>
> On May 29, 2012 4:15 AM, "Stefan G. Weichinger" <lists@xunil.at> wrote:
>>
>> Am 2012-05-28 22:54, schrieb Sascha Cunz:
>> > On Monday, 28. May 2012 22:04:30 Stefan G. Weichinger wrote:
>> >> As GCC-4.7.0 appeared for ~amd64 now ...
>> >>
>> >> anyone recompiled system or world with it already?
>> >>
>> >> More advantages or disadvantages?
>> >
>> > I tried an emerge -ev world yesterday (on a box with a total about 1100
>> > emergeed packages), so far only had compiling trouble with
>> > gst-pluings-ffmpeg
>> > (gcc4.7.0 bug including patch is on b.g.o[1], so was easy to solve) and
>> > firefox 12.
>> >
>> > All of KDE 4.8.3 and libreoffice did emerge nicely. Though i did not
>> > test the
>> > results yet.
>> >
>> > SaCu
>> >
>> > [1] https://bugs.gentoo.org/show_bug.cgi?id=407741
>> >
>>
>>
>> Thanks alot, Sascha, for that helpful feedback!
>>
>> I will give it a try on one of my machines tonight.
>>
>> In gentoo-ricer-terms: did you notice any improvements?
>>
>> ;-)
>>
>
> LOL
>
> Yeah, I am also wondering how much improvement graphite sees with 4.7.0
>
> *shuffles over to gcc changelog

I'm mostly looking forward to Bulldozer support and RDRAND.

-- 
:wq



  reply	other threads:[~2012-05-29  2:28 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-28 20:04 [gentoo-user] ~gcc-4.7.0 Stefan G. Weichinger
2012-05-28 20:54 ` Sascha Cunz
2012-05-28 21:11   ` Stefan G. Weichinger
2012-05-29  2:19     ` Pandu Poluan
2012-05-29  2:26       ` Michael Mol [this message]
2012-05-29  8:30         ` microcai
2012-05-29 12:58           ` Michael Mol
2012-05-29 16:18             ` Volker Armin Hemmann
2012-05-29  9:42 ` [gentoo-user] ~gcc-4.7.0 Nikos Chantziaras
2012-05-29 11:35   ` Ezequiel Garcia
2012-05-29 11:58     ` Stefan G. Weichinger
2012-05-29 11:51   ` Stefan G. Weichinger
2012-05-29 10:13 ` [gentoo-user] ~gcc-4.7.0 Andrey Moshbear
2012-05-29 10:26 ` Hinnerk van Bruinehsen
2012-05-29 13:01   ` Adam Carter
2012-05-29 14:11   ` Michael Orlitzky
2012-05-29 11:54 ` [gentoo-user] ~gcc-4.7.0 walt
2012-06-02  0:36   ` walt
2012-06-02  2:37     ` Nilesh Govindrajan
2012-06-02  6:52       ` Hinnerk van Bruinehsen

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=CA+czFiCEnaYdOXgQs1c4FM6OZK6c7LONEVOpLbjusHfKm401Qg@mail.gmail.com \
    --to=mikemol@gmail.com \
    --cc=gentoo-user@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