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 c++/50943] asm goto in templated code causes internal compiler segfaults Date: Tue, 01 Nov 2011 13:16:00 -0000 [thread overview] Message-ID: <bug-50943-4-H4wUr6MERE@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-50943-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50943 Richard Guenther <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2011-11-01 Ever Confirmed|0 |1 Known to fail| |4.7.0 --- Comment #1 from Richard Guenther <rguenth at gcc dot gnu.org> 2011-11-01 13:15:42 UTC --- Confirmed. The frontend fails to re-map the labels in the asm goto statement leading to disagreement at gimplification time: stmt <cleanup_point_expr 0x14248dbb8 type <void_type 0x14233abd0 void> side-effects tree_1 arg 0 <asm_expr 0x142324b40 type <void_type 0x14233abd0 void> side-effects public .. arg 4 <tree_list 0x14248dac8 purpose <string_cst 0x142489f40 constant "other"> value <label_decl 0x14248e080 other>> ... stmt <label_expr 0x14248dc08 type <void_type 0x14233abd0 void> side-effects arg 0 <label_decl 0x14248e200 other type <void_type 0x14233abd0 void> VOID file t.ii line 7 col 1 align 1 context <function_decl 0x142481500 work> initial <error_mark 0x142329d68>> t.ii:7:1>
next prev parent reply other threads:[~2011-11-01 13:16 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-11-01 12:02 [Bug c++/50943] New: " dummyddd at gmail dot com 2011-11-01 13:16 ` rguenth at gcc dot gnu.org [this message] 2011-11-02 21:31 ` [Bug c++/50943] " paolo.carlini at oracle dot com 2011-11-07 23:48 ` 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-50943-4-H4wUr6MERE@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).