All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] gcc 4.3.3 anyone?
Date: Thu, 05 Feb 2009 12:06:53 +0100	[thread overview]
Message-ID: <871vudcfci.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <1233827954.6323.3.camel@sven> (Sven Neumann's message of "Thu\, 05 Feb 2009 10\:59\:14 +0100")

>>>>> "Sven" == Sven Neumann <s.neumann@phase-zero.de> writes:

 Sven> Hi,
 Sven> On Mon, 2009-02-02 at 21:06 +0100, Peter Korsgaard wrote:

 Sven> I've ran into what appears to be a bug in gcc 4.3.2 and reported it
 Sven> here: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39076

 Sven> The gcc people have fixed this problem in the gcc-4.3 branch. I verified
 Sven> that the patch fixes the compiler segfault when compiling flac. Attached
 Sven> is a patch for buildroot that incorporates this fix for gcc 4.3.2.

Thanks, will apply.

 Sven> I also noticed that two of the patches in toolchain/gcc/4.3.2 don't end
 Sven> in .patch and thus are not applied. Is this intentional?

No, not afaik. The 995-short-enums.diff comes from Bernhard and is a
fix for PR34205 which got tagged WONTFIX upstream
(http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34205), and afaik
shouldn't be needed now we don't use abi=iwmmxt anymore - Bernhard,
correct me if I'm wrong - Otherwise I'll remove it.

The 306-arm-funroll-loops.patch.arm is from Ulf (r24993), and not just
the name is wrong, it doesn't apply (wrong patch level). I've fixed
that up and am now doing a test build to check if it fixes the mplayer
ICE. If so, then I'll commit, otherwise I'll remove it.

Thanks for noticing!

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2009-02-05 11:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-02 17:02 [Buildroot] gcc 4.3.3 anyone? Sven Neumann
2009-02-02 20:06 ` Peter Korsgaard
2009-02-05  9:59   ` Sven Neumann
2009-02-05 11:06     ` Peter Korsgaard [this message]
2009-02-05 13:29     ` Peter Korsgaard

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=871vudcfci.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.