public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/53249] [4.8 Regression] Bootstrap failure
Date: Sat, 05 May 2012 23:27:00 -0000	[thread overview]
Message-ID: <bug-53249-4-qoNBPdeNwa@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53249-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #1 from H.J. Lu <hjl.tools at gmail dot com> 2012-05-05 22:22:27 UTC ---
Created attachment 27322
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=27322
A testcase

On Linux/x86-64:

[hjl@gnu-35 gcc]$ ./xgcc -B./ -O2 -mx32 -fPIC -S -ftls-model=initial-exec
/tmp/barrier.i -o /tmp/x.s
../../../../src-trunk/libgomp/barrier.c: In function \u2018GOMP_barrier\u2019:
../../../../src-trunk/libgomp/barrier.c:34:21: internal compiler error: in
plus_constant, at explow.c:88
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
[hjl@gnu-35 gcc]$


  reply	other threads:[~2012-05-05 22:22 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-05 22:22 [Bug bootstrap/53249] New: " hjl.tools at gmail dot com
2012-05-05 23:27 ` hjl.tools at gmail dot com [this message]
2012-05-06 10:59 ` [Bug bootstrap/53249] " rsandifo at gcc dot gnu.org
2012-05-06 14:16 ` hjl.tools at gmail dot com
2012-05-06 14:35 ` hjl.tools at gmail dot com
2012-05-06 14:54 ` hjl.tools at gmail dot com
2012-05-06 15:07 ` hjl.tools at gmail dot com
2012-05-06 15:09 ` rsandifo at gcc dot gnu.org
2012-05-06 15:56 ` hjl.tools at gmail dot com
2012-05-06 16:01 ` rdsandiford at googlemail dot com
2012-05-06 17:04 ` hjl.tools at gmail dot com
2012-05-09  9:24 ` rsandifo at gcc dot gnu.org
2012-05-09  9:40 ` rsandifo at gcc dot gnu.org
2012-05-09 13:34 ` hjl 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-53249-4-qoNBPdeNwa@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).