public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "andi-gcc at firstfloor dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/50568] [4.7 Regression] Massive LTO failures
Date: Thu, 29 Sep 2011 20:47:00 -0000	[thread overview]
Message-ID: <bug-50568-4-lLEipXKcde@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-50568-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50568

--- Comment #18 from Andi Kleen <andi-gcc at firstfloor dot org> 2011-09-29 20:36:50 UTC ---
Created attachment 25384
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=25384
fix + splay tree

I have some unrelated trouble with a 32bit bootstrap currently.

This patch should fix all the problems with the splay tree, by allocating
the key separately.

Can you give it a test please? Thanks


  parent reply	other threads:[~2011-09-29 20:37 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-29 15:50 [Bug lto/50568] New: " hjl.tools at gmail dot com
2011-09-29 15:55 ` [Bug lto/50568] " hjl.tools at gmail dot com
2011-09-29 16:02 ` andi-gcc at firstfloor dot org
2011-09-29 16:04 ` hjl.tools at gmail dot com
2011-09-29 16:18 ` hjl.tools at gmail dot com
2011-09-29 18:12 ` hjl.tools at gmail dot com
2011-09-29 18:16 ` andi-gcc at firstfloor dot org
2011-09-29 18:18 ` hjl.tools at gmail dot com
2011-09-29 18:19 ` hjl.tools at gmail dot com
2011-09-29 18:20 ` andi-gcc at firstfloor dot org
2011-09-29 18:21 ` andi-gcc at firstfloor dot org
2011-09-29 18:26 ` hjl.tools at gmail dot com
2011-09-29 18:28 ` hjl.tools at gmail dot com
2011-09-29 18:29 ` hjl.tools at gmail dot com
2011-09-29 18:29 ` andi-gcc at firstfloor dot org
2011-09-29 18:35 ` andi-gcc at firstfloor dot org
2011-09-29 18:45 ` hjl.tools at gmail dot com
2011-09-29 18:45 ` hjl.tools at gmail dot com
2011-09-29 20:47 ` andi-gcc at firstfloor dot org [this message]
2011-09-29 20:55 ` hjl.tools at gmail dot com
2011-09-29 22:23 ` hjl.tools at gmail dot com
2011-09-29 22:23 ` hjl.tools at gmail dot com
2011-09-29 22:28 ` hjl.tools at gmail dot com
2011-09-29 22:53 ` hjl.tools at gmail dot com
2011-09-29 23:17 ` andi-gcc at firstfloor dot org
2011-09-29 23:21 ` hjl.tools at gmail dot com
2011-09-29 23:22 ` hjl.tools at gmail dot com
2011-09-29 23:32 ` andi-gcc at firstfloor dot org
2011-09-29 23:34 ` andi-gcc at firstfloor dot org
2011-09-30  0:33 ` hjl.tools at gmail dot com
2011-09-30  0:45 ` andi-gcc at firstfloor dot org
2011-09-30  6:00 ` hjl.tools at gmail dot com
2011-09-30 15:57 ` hjl at gcc dot gnu.org
2011-10-10 15:14 ` rguenth at gcc dot gnu.org
2021-08-24 13:10 ` hjl.tools at gmail dot com

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=bug-50568-4-lLEipXKcde@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).