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 c++/45940] [trans-mem] Error of unsafe function even if annotated
Date: Thu, 25 Nov 2010 10:02:00 -0000	[thread overview]
Message-ID: <bug-45940-4-Fr2wRIsxzt@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-45940-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from Patrick Marlier <patrick.marlier at gmail dot com> 2010-11-25 09:57:32 UTC ---
Created attachment 22526
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=22526
another testcase

It seems not completely solved.

Here a another testcase.

With -O0, it complains about unsafe function even if annotated as
transaction_pure.

gcc -Wall -c -O0 -fgnu-tm unsafe.cpp -o unsafe
unsafe.cpp:38:54: error: unsafe function call ‘int
atomic_exchange_and_add(int*, int)’ within ‘transaction_safe’ function

With -O1, ICE in expand_block_tm().

gcc -Wall -c -O1 -fgnu-tm unsafe.cpp -o unsafe
unsafe.cpp: In function ‘int main()’:
unsafe.cpp:73:5: internal compiler error: in expand_block_tm, at
trans-mem.c:2254
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.

Vincent, please reopen the bug and in the bug description set version to
"trans-mem" (easier to find it).

Patrick Marlier.


  parent reply	other threads:[~2010-11-25  9:58 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-08 12:51 [Bug c++/45940] New: " vincent.gramoli at epfl dot ch
2010-11-04 14:37 ` [Bug c++/45940] " patrick.marlier at gmail dot com
2010-11-19 18:33 ` aldyh at gcc dot gnu.org
2010-11-23 13:59 ` aldyh at gcc dot gnu.org
2010-11-23 15:29 ` patrick.marlier at gmail dot com
2010-11-23 16:26 ` aldyh at gcc dot gnu.org
2010-11-24 14:01 ` aldyh at gcc dot gnu.org
2010-11-25 10:02 ` patrick.marlier at gmail dot com [this message]
2010-11-25 15:46 ` vincent.gramoli at epfl dot ch
2010-11-29 15:47 ` aldyh at gcc dot gnu.org
2010-11-29 16:27 ` aldyh at gcc dot gnu.org
2010-12-13 11:10 ` aldyh at gcc dot gnu.org
2010-12-13 14:16 ` aldyh at gcc dot gnu.org
2010-12-13 14:49 ` aldyh at gcc dot gnu.org
2010-12-13 14:50 ` aldyh at gcc dot gnu.org
2010-12-14 12:07 ` aldyh at gcc dot gnu.org
2011-01-14 18:28 ` aldyh at gcc dot gnu.org
2011-01-14 19:43 ` aldyh at gcc dot gnu.org
2011-01-20 10:41 ` vincent.gramoli at epfl dot ch
2011-01-20 14:44 ` aldyh at gcc dot gnu.org
2011-01-20 16:12 ` vincent.gramoli at epfl dot ch
2011-01-24 12:56 ` vincent.gramoli at epfl dot ch

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-45940-4-Fr2wRIsxzt@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).