public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/51860] [4.7 regression] s390 esa mode bootstrap comparison failure since transactional memory branch merge
Date: Mon, 16 Jan 2012 01:40:00 -0000	[thread overview]
Message-ID: <bug-51860-4-7TjYWrqGHF@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51860-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> 2012-01-16 00:06:26 UTC ---
Created attachment 26335
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=26335
pr51860.ii

Partly reduced testcase.
g++ -O2 -mesa -fcompare-debug pr51860.ii
Unfortunately, delta is quite slow to reduce it even further than this (most
probably because it depends on the inter insn distances to hit the literal pool
insertion at the exact spot).


  parent reply	other threads:[~2012-01-16  0:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-14 13:28 [Bug bootstrap/51860] New: [4.7 regression] s390 esa mode bootstrap comparison failure since transactional memory branch krebbel at gcc dot gnu.org
2012-01-14 13:30 ` [Bug bootstrap/51860] [4.7 regression] s390 esa mode bootstrap comparison failure since transactional memory branch merge krebbel at gcc dot gnu.org
2012-01-15 19:06 ` jakub at gcc dot gnu.org
2012-01-15 20:37 ` jakub at gcc dot gnu.org
2012-01-15 20:44 ` krebbel at gcc dot gnu.org
2012-01-15 21:23 ` jakub at gcc dot gnu.org
2012-01-16  1:40 ` jakub at gcc dot gnu.org [this message]
2012-01-16  9:01 ` jakub at gcc dot gnu.org
2012-01-16  9:27 ` krebbel at gcc dot gnu.org
2012-01-16 11:13 ` jakub at gcc dot gnu.org
2012-01-16 13:29 ` jakub at gcc dot gnu.org
2012-01-16 14:16 ` jakub at gcc dot gnu.org
2012-01-16 14:21 ` jakub at gcc dot gnu.org

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-51860-4-7TjYWrqGHF@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).