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 middle-end/55597] New: [4.8 Regression] internal compiler error: in plus_constant, at explow.c:88
Date: Tue, 04 Dec 2012 21:01:00 -0000	[thread overview]
Message-ID: <bug-55597-4@http.gcc.gnu.org/bugzilla/> (raw)


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

             Bug #: 55597
           Summary: [4.8 Regression] internal compiler error: in
                    plus_constant, at explow.c:88
    Classification: Unclassified
           Product: gcc
           Version: 4.8.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: middle-end
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: hjl.tools@gmail.com


On Linux/x86-64, revision 194159 gave:

[hjl@gnu-ivb-1 gcc]$ cat /tmp/testcase.c 
struct initial_sp {
  void *sp;
  int mask;
};
void foo (int *);
__thread struct initial_sp __morestack_initial_sp;
void __morestack_release_segments (void) {
  foo (&__morestack_initial_sp.mask);
}
[hjl@gnu-ivb-1 gcc]$ ./xgcc -B./ -fPIC -O2 -mx32 -S -maddress-mode=long
/tmp/testcase.c 
/tmp/testcase.c: In function ‘__morestack_release_segments’:
/tmp/testcase.c:9:1: internal compiler error: in plus_constant, at explow.c:88
 }
 ^
0x7321f3 plus_constant(machine_mode, rtx_def*, long)
    /export/gnu/import/git/gcc/gcc/explow.c:88
0x5fdee7 init_alias_analysis()
    /export/gnu/import/git/gcc/gcc/alias.c:2945
0xfce2ce cse_main
    /export/gnu/import/git/gcc/gcc/cse.c:6543
0xfd010e rest_of_handle_cse
    /export/gnu/import/git/gcc/gcc/cse.c:7435
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <http://gcc.gnu.org/bugs.html> for instructions.
[hjl@gnu-ivb-1 gcc]$


             reply	other threads:[~2012-12-04 21:01 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-04 21:01 hjl.tools at gmail dot com [this message]
2012-12-04 22:29 ` [Bug middle-end/55597] " hjl.tools at gmail dot com
2012-12-04 22:52 ` bonzini at gnu dot org
2012-12-04 23:25 ` [Bug target/55597] " steven at gcc dot gnu.org
2012-12-04 23:46 ` [Bug target/55597] " steven at gcc dot gnu.org
2012-12-04 23:50 ` [Bug middle-end/55597] " hjl.tools at gmail dot com
2012-12-05 11:34 ` [Bug middle-end/55597] [4.8 Regression] " ebotcazou at gcc dot gnu.org
2012-12-05 17:28 ` hjl.tools at gmail dot com
2012-12-05 17:56 ` hjl.tools at gmail dot com
2012-12-05 20:46 ` ubizjak at gmail dot com
2012-12-06  0:22 ` hjl.tools at gmail dot com
2012-12-06 15:05 ` jakub at gcc dot gnu.org
2012-12-06 20:14 ` ubizjak at gmail dot com
2012-12-06 22:05 ` uros at gcc dot gnu.org
2012-12-07  3:44 ` hjl.tools at gmail dot com
2012-12-07  8:11 ` uros at gcc dot gnu.org
2012-12-07  8:21 ` ubizjak 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-55597-4@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).