public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "chefmax at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/68122] ICE in gcc/toplev.c:353 with -fsanitize=undefined and -fgnu-tm Date: Wed, 28 Oct 2015 07:50:00 -0000 [thread overview] Message-ID: <bug-68122-4-CyVwlH970N@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-68122-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68122 Maxim Ostapenko <chefmax at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |chefmax at gcc dot gnu.org --- Comment #2 from Maxim Ostapenko <chefmax at gcc dot gnu.org> --- $ cat tm-thread.c.019t.ubsan ;; Function main (main, funcdef_no=0, decl_uid=2229, cgraph_uid=0, symbol_order=1) main () { int D.2233; int cnt.0; int D.2234; int cnt.0_2; int _3; int _6; <bb 2>: __transaction_atomic // SUBCODE=[ GTMA_HAVE_LOAD GTMA_HAVE_STORE ] <bb 3>: cnt.0_2 = cnt; _3 = UBSAN_CHECK_ADD (cnt.0_2, 1); cnt = _3; __builtin__ITM_commitTransaction (); <bb 4>: _6 = 0; <L0>: return _6; } It seems that pass_ipa_tm tries to handle UBSAN_CHECK_ADD call and fails. Should we teach it to handle ubsan intrinsics? Or maybe just not instrument transaction clauses at all?
next prev parent reply other threads:[~2015-10-28 7:50 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-10-27 21:41 [Bug sanitizer/68122] New: " larsbj at gullik dot net 2015-10-28 7:50 ` chefmax at gcc dot gnu.org [this message] 2015-10-28 12:04 ` [Bug middle-end/68122] " rguenth at gcc dot gnu.org 2022-01-04 2:42 ` [Bug middle-end/68122] ICE in is_tm_pure_call " pinskia at gcc dot gnu.org 2023-11-27 8:57 ` 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-68122-4-CyVwlH970N@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: linkBe 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).