public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "machens at tuhh dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/59131] New: Compiler segfaults while generating code to save local variables in transactional section
Date: Thu, 14 Nov 2013 14:15:00 -0000	[thread overview]
Message-ID: <bug-59131-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 59131
           Summary: Compiler segfaults while generating code to save local
                    variables in transactional section
           Product: gcc
           Version: 4.7.3
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: machens at tuhh dot de

I've analyzed code generated to save and restore local variables in
transactional sections and wrote some tests with very much local variables
(exceeding the capacity of the CPU registers). At some point the compiler
segfaulted. I've attached the code to allow you to further investigate it.



/usr/bin/g++-4.7 -fgnu-tm -Wall -g -O3 -o gnutm-test compiler-segfaults.c -litm


             reply	other threads:[~2013-11-14 14:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-14 14:15 machens at tuhh dot de [this message]
2013-11-15 12:55 ` [Bug c++/59131] " machens at tuhh dot de
2013-11-15 15:13 ` paolo.carlini at oracle dot com
2013-11-27 17:14 ` aldyh at gcc dot gnu.org
2013-11-27 17:19 ` aldyh at gcc dot gnu.org
2014-07-10  8:57 ` patrick.marlier at gmail dot com
2014-07-10 11:39 ` patrick.marlier at gmail dot com
2014-07-10 11:42 ` mpolacek 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-59131-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).