public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dimhen at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/56961] New: cycle between do_spec_1() / process_brace_body() / handle_braces()
Date: Mon, 15 Apr 2013 07:39:00 -0000	[thread overview]
Message-ID: <bug-56961-4@http.gcc.gnu.org/bugzilla/> (raw)


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

             Bug #: 56961
           Summary: cycle between do_spec_1() / process_brace_body() /
                    handle_braces()
    Classification: Unclassified
           Product: gcc
           Version: 4.9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: dimhen@gmail.com


$ cat x.cpp 
struct foo { };
  typedef struct
  {
      volatile foo fields;
  }
  CSPHandleState;
  CSPHandleState a;
  void
  fn1 ()
  {
      CSPHandleState b;
      b.fields = foo();
  }


$ g++ -O0 -c x.cpp 
x.cpp: In function 'void fn1()':
x.cpp:12:16: error: passing 'volatile foo' as 'this' argument of 'foo&
foo::operator=(const foo&)' discards qualifiers [-fpermissive]
       b.fields = foo();
                ^
g++: internal compiler error: Segmentation fault (program cc1plus)
0x40950c execute
    /home/dimhen/src/gcc-current/gcc/gcc.c:2822
0x409769 do_spec_1
    /home/dimhen/src/gcc-current/gcc/gcc.c:4614
0x40c4d9 process_brace_body
    /home/dimhen/src/gcc-current/gcc/gcc.c:5871
0x40c4d9 handle_braces
    /home/dimhen/src/gcc-current/gcc/gcc.c:5785
0x40a1fa do_spec_1
    /home/dimhen/src/gcc-current/gcc/gcc.c:5268
0x40c4d9 process_brace_body
    /home/dimhen/src/gcc-current/gcc/gcc.c:5871
0x40c4d9 handle_braces
    /home/dimhen/src/gcc-current/gcc/gcc.c:5785
0x40a1fa do_spec_1
    /home/dimhen/src/gcc-current/gcc/gcc.c:5268
0x40a5eb do_spec_1
    /home/dimhen/src/gcc-current/gcc/gcc.c:5373
0x40c4d9 process_brace_body
    /home/dimhen/src/gcc-current/gcc/gcc.c:5871
0x40c4d9 handle_braces
    /home/dimhen/src/gcc-current/gcc/gcc.c:5785
0x40a1fa do_spec_1
    /home/dimhen/src/gcc-current/gcc/gcc.c:5268
0x40c4d9 process_brace_body
    /home/dimhen/src/gcc-current/gcc/gcc.c:5871
0x40c4d9 handle_braces
    /home/dimhen/src/gcc-current/gcc/gcc.c:5785
0x40a1fa do_spec_1
    /home/dimhen/src/gcc-current/gcc/gcc.c:5268
0x40c4d9 process_brace_body
    /home/dimhen/src/gcc-current/gcc/gcc.c:5871
0x40c4d9 handle_braces
    /home/dimhen/src/gcc-current/gcc/gcc.c:5785
0x40a1fa do_spec_1
    /home/dimhen/src/gcc-current/gcc/gcc.c:5268
0x40c4d9 process_brace_body
    /home/dimhen/src/gcc-current/gcc/gcc.c:5871
0x40c4d9 handle_braces
    /home/dimhen/src/gcc-current/gcc/gcc.c:5785
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.

Thanks to David Blaikie for reduced testcase
(http://lists.cs.uiuc.edu/pipermail/cfe-users/2013-April/000085.html)


             reply	other threads:[~2013-04-15  7:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-15  7:39 dimhen at gmail dot com [this message]
2013-04-15  7:45 ` [Bug c++/56961] Segfault with volatile field pinskia at gcc dot gnu.org
2013-04-15  7:50 ` [Bug c++/56961] stack overflow in gimplifier " pinskia at gcc dot gnu.org
2013-04-15  8:01 ` dimhen at gmail dot com
2014-01-06 19:33 ` dimhen at gmail dot com
2014-06-05 12:16 ` paolo.carlini at oracle dot com
2014-06-05 12:29 ` rguenth at gcc dot gnu.org
2014-06-05 12:33 ` rguenth at gcc dot gnu.org
2014-06-05 12:35 ` rguenth at gcc dot gnu.org
2014-06-05 12:39 ` rguenth at gcc dot gnu.org
2014-06-05 14:16 ` paolo.carlini at oracle dot com
2014-06-05 17:35 ` paolo at gcc dot gnu.org
2014-06-05 17:36 ` paolo.carlini at oracle 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-56961-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).