public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "olegendo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/61120] New: wide-int merge causes segfault in cc1
Date: Thu, 08 May 2014 23:01:00 -0000	[thread overview]
Message-ID: <bug-61120-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 61120
           Summary: wide-int merge causes segfault in cc1
           Product: gcc
           Version: 4.10.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: driver
          Assignee: unassigned at gcc dot gnu.org
          Reporter: olegendo at gcc dot gnu.org
                CC: kyrylo.tkachov at arm dot com, mikestump at comcast dot net,
                    rsandifo at redhat dot com, zadeck at naturalbridge dot com
            Target: sh*-*-*

Created attachment 32765
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=32765&action=edit
Test file

Compiling the attached preprocessed file with an r210113 SH cross compiler
causes the following:

xgcc: internal compiler error: Segmentation fault (program cc1)
0x8053cf0 execute
    ../../gcc-trunk2/gcc/gcc.c:2848
0x80540d4 do_spec_1
    ../../gcc-trunk2/gcc/gcc.c:4652
0x80565b1 process_brace_body
    ../../gcc-trunk2/gcc/gcc.c:5935
0x80565b1 handle_braces
    ../../gcc-trunk2/gcc/gcc.c:5849
0x8054604 do_spec_1
    ../../gcc-trunk2/gcc/gcc.c:5306
0x80565b1 process_brace_body
    ../../gcc-trunk2/gcc/gcc.c:5935
0x80565b1 handle_braces
    ../../gcc-trunk2/gcc/gcc.c:5849
0x8054604 do_spec_1
    ../../gcc-trunk2/gcc/gcc.c:5306
0x80545a9 do_spec_1
    ../../gcc-trunk2/gcc/gcc.c:5421
0x80565b1 process_brace_body
    ../../gcc-trunk2/gcc/gcc.c:5935
0x80565b1 handle_braces
    ../../gcc-trunk2/gcc/gcc.c:5849
0x8054604 do_spec_1
    ../../gcc-trunk2/gcc/gcc.c:5306
0x80565b1 process_brace_body
    ../../gcc-trunk2/gcc/gcc.c:5935
0x80565b1 handle_braces
    ../../gcc-trunk2/gcc/gcc.c:5849
0x8054604 do_spec_1
    ../../gcc-trunk2/gcc/gcc.c:5306
0x80565b1 process_brace_body
    ../../gcc-trunk2/gcc/gcc.c:5935
0x80565b1 handle_braces
    ../../gcc-trunk2/gcc/gcc.c:5849
0x8054604 do_spec_1
    ../../gcc-trunk2/gcc/gcc.c:5306
0x80565b1 process_brace_body
    ../../gcc-trunk2/gcc/gcc.c:5935
0x80565b1 handle_braces
    ../../gcc-trunk2/gcc/gcc.c:5849
Please submit a full bug report,
with preprocessed source if appropriate.

I'm a bit lost here.  If you need/have more info, please let me know.


             reply	other threads:[~2014-05-08 23:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-08 23:01 olegendo at gcc dot gnu.org [this message]
2014-05-09  0:09 ` [Bug driver/61120] " kkojima at gcc dot gnu.org
2014-05-09  0:30 ` glisse at gcc dot gnu.org
2014-05-09 11:05 ` rguenth 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-61120-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).