public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "patrick.marlier at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libitm/61594] ICE (assertion failure) in trans-mem.c
Date: Thu, 03 Jul 2014 09:19:00 -0000	[thread overview]
Message-ID: <bug-61594-4-TpBiQG4RBH@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61594-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61594

--- Comment #1 from Patrick Marlier <patrick.marlier at gmail dot com> ---
Created attachment 33058
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=33058&action=edit
reduced testcase

$ xgcc -Wall -Wextra -Wfatal-errors -O2 -fgnu-tm -S pr61594.c
pr61594.c: In function ‘fn1’:
pr61594.c:12:40: internal compiler error: in requires_barrier, at
trans-mem.c:1517
 __attribute__((transaction_safe)) void fn1() { fn2(""); }
>From gcc-bugs-return-455556-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jul 03 09:19:52 2014
Return-Path: <gcc-bugs-return-455556-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 3841 invoked by alias); 3 Jul 2014 09:19:50 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 3772 invoked by uid 48); 3 Jul 2014 09:19:41 -0000
From: "A.Finch at lancaster dot ac.uk" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/61674] The destructor of a simple class is removed by optimization
Date: Thu, 03 Jul 2014 09:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 4.8.2
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: A.Finch at lancaster dot ac.uk
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-61674-4-q43wo4gc8e@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-61674-4@http.gcc.gnu.org/bugzilla/>
References: <bug-61674-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-07/txt/msg00147.txt.bz2
Content-length: 539

https://gcc.gnu.org/bugzilla/show_bug.cgi?ida674

--- Comment #6 from Alex Finch <A.Finch at lancaster dot ac.uk> ---

I guess I should have made that clear. The class has a static variable:
static int fLockCount;

which counts how many times an object of the class is created.
If it is >1, then IsLocked() returns true. The destructor has a line
 --fLockCount;
which is not executed if the destructor is not called. This breaks the program.
The destructor should not be optimised out precisely because it modifies the
static variable.


  reply	other threads:[~2014-07-03  9:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-24 16:08 [Bug libitm/61594] New: " hammacher at cs dot uni-saarland.de
2014-07-03  9:19 ` patrick.marlier at gmail dot com [this message]
2014-07-03 12:11 ` [Bug libitm/61594] " patrick.marlier at gmail dot com
2015-01-23 14:58 ` torvald at gcc dot gnu.org
2015-01-23 15:11 ` patrick.marlier at gmail dot com
2015-01-26 10:29 ` hammacher at cs dot uni-saarland.de
2015-01-26 13:05 ` torvald at gcc dot gnu.org
2015-01-26 13:06 ` torvald at gcc dot gnu.org
2022-01-07  5:13 ` pinskia at gcc dot gnu.org
2022-01-31 16:10 ` marxin 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-61594-4-TpBiQG4RBH@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).