public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/52141] [trans-mem] ICE due to asm statement in trans-mem.c:expand_block_tm Date: Tue, 07 Feb 2012 09:31:00 -0000 [thread overview] Message-ID: <bug-52141-4-TiVTsYqW9d@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-52141-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52141 --- Comment #1 from Richard Guenther <rguenth at gcc dot gnu.org> 2012-02-07 09:30:45 UTC --- Might I suggest to instead of case GIMPLE_ASM: gcc_unreachable (); use case GIMPLE_ASM: sorry ("asm statements not allowed in transactions"); ? It's not a compiler but a user error (well, usually). Btw, what you really want is some simple IPA propagation of the various transaction attributes similar to how we handle pure/const.
next prev parent reply other threads:[~2012-02-07 9:31 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-02-06 20:50 [Bug middle-end/52141] New: " patrick.marlier at gmail dot com 2012-02-07 9:31 ` rguenth at gcc dot gnu.org [this message] 2012-02-07 17:16 ` [Bug middle-end/52141] " rth at gcc dot gnu.org 2012-02-20 23:46 ` aldyh at gcc dot gnu.org 2012-02-21 0:23 ` 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-52141-4-TiVTsYqW9d@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).