public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "roman at tsisyk dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/51347] New: [trans-mem] Segfault on templates with -O1 -fgnu-tm
Date: Tue, 29 Nov 2011 19:37:00 -0000 [thread overview]
Message-ID: <bug-51347-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51347
Bug #: 51347
Summary: [trans-mem] Segfault on templates with -O1 -fgnu-tm
Classification: Unclassified
Product: gcc
Version: 4.7.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: roman@tsisyk.com
Build: trunk Revision 181801
Created attachment 25946
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=25946
Testcase
I am doing some experiments with the transaction memory feature, which has
recently been merged to the main trunk. Currently, one of my tests causes g++
segfault.
---
main.cpp: In member function 'void BugContainer<ValueType>::bug() [with
ValueType = Info]':
main.cpp:35:1: internal compiler error: Segmentation fault
---
It is always reproducible and tested on various configurations.
I simplified code and made reduced testcase.
gcc from the trunk rev 181801 date 20111129.
Debian gcc-snapshot 20111114 has some problems.
--
Configured with: ../configure --prefix=/usr/lib/gcc-snapshot
--disable-bootstrap --enable-languages=c,c++ --enable-shared
--enable-linker-build-id --with-system-zlib --disable-nls --enable-clocale=gnu
--enable-libstdcxx-debug --enable-libstdcxx-time=yes --enable-plugin
--with-arch-directory=amd64 --with-arch-32=i586 --with-tune=generic
--disable-werror --enable-checking=yes --build=x86_64-linux-gnu
--host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
gcc version 4.7.0 20111129 (experimental) (GCC)
--
next reply other threads:[~2011-11-29 18:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-29 19:37 roman at tsisyk dot com [this message]
2011-11-29 19:43 ` [Bug c++/51347] " roman at tsisyk dot com
2011-12-03 2:24 ` patrick.marlier at gmail dot com
2011-12-03 10:37 ` roman at tsisyk dot com
2011-12-12 16:45 ` aldyh 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-51347-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).