public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dicomj23 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/52094] internal compiler error: Segmentation fault (program cc1plus)
Date: Thu, 02 Feb 2012 10:04:00 -0000	[thread overview]
Message-ID: <bug-52094-4-LL8XIg2Gri@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52094-4@http.gcc.gnu.org/bugzilla/>

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

Dico <dicomj23 at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|g++ yields different        |internal compiler error:
                   |behaviour for postfix       |Segmentation fault (program
                   |increment and decrement     |cc1plus)
                   |operators with fundamental  |
                   |types vs. classes           |

--- Comment #1 from Dico <dicomj23 at gmail dot com> 2012-02-02 10:04:30 UTC ---
user:$ gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/i686-linux-gnu/4.6.1/lto-wrapper
Target: i686-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu/Linaro
4.6.1-9ubuntu3' --with-bugurl=file:///usr/share/doc/gcc-4.6/README.Bugs
--enable-languages=c,c++,fortran,objc,obj-c++,go --prefix=/usr
--program-suffix=-4.6 --enable-shared --enable-linker-build-id
--with-system-zlib --libexecdir=/usr/lib --without-included-gettext
--enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.6
--libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu
--enable-libstdcxx-debug --enable-libstdcxx-time=yes --enable-plugin
--enable-objc-gc --enable-targets=all --disable-werror --with-arch-32=i686
--with-tune=generic --enable-checking=release --build=i686-linux-gnu
--host=i686-linux-gnu --target=i686-linux-gnu
Thread model: posix
gcc version 4.6.1 (Ubuntu/Linaro 4.6.1-9ubuntu3) 
user:$ 



user$ gcc main.cpp & cat main.cpp
[1] 31057
namespace N { struct A { struct Inner; }; struct Inner {}; }
namespace NN { struct AA : N::A {}; struct AA::Inner : N::Inner {}; }

int main() { return 0; }
user$ gcc: internal compiler error: Segmentation fault (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-4.6/README.Bugs> for instructions.


  reply	other threads:[~2012-02-02 10:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-02  9:59 [Bug c++/52094] New: g++ yields different behaviour for postfix increment and decrement operators with fundamental types vs. classes dicomj23 at gmail dot com
2012-02-02 10:04 ` dicomj23 at gmail dot com [this message]
2012-02-02 10:23 ` [Bug c++/52094] ICE on definition of nested class in wrong namespace scope with wrong nested-name-qualifier redi at gcc dot gnu.org
2012-02-02 10:26 ` redi at gcc dot gnu.org
2012-02-02 10:34 ` dicomj23 at gmail dot com
2012-02-02 10:43 ` redi at gcc dot gnu.org
2013-09-29 19:15 ` arnaut.billings at yahoo dot com
2020-07-23 14:39 ` mpolacek at gcc dot gnu.org
2021-08-04 19:48 ` pinskia 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-52094-4-LL8XIg2Gri@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).