public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/55921] Crash in verify_ssa for asm to side-steps complex pessimization Date: Wed, 09 Jan 2013 18:39:00 -0000 [thread overview] Message-ID: <bug-55921-4-ylihM2u95r@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-55921-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55921 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |ASSIGNED Last reconfirmed| |2013-01-09 CC| |jakub at gcc dot gnu.org AssignedTo|unassigned at gcc dot |jakub at gcc dot gnu.org |gnu.org | Ever Confirmed|0 |1 --- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> 2013-01-09 18:38:04 UTC --- expand_complex_operations_1 needs to handle inline asm like expand_complex_move.
next prev parent reply other threads:[~2013-01-09 18:39 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-01-09 17:09 [Bug middle-end/55921] New: " amylaar at gcc dot gnu.org 2013-01-09 17:10 ` [Bug middle-end/55921] " amylaar at gcc dot gnu.org 2013-01-09 17:20 ` pinskia at gcc dot gnu.org 2013-01-09 18:39 ` jakub at gcc dot gnu.org [this message] 2013-01-09 20:29 ` [Bug middle-end/55921] [4.6/4.7/4.8 Regression] " jakub at gcc dot gnu.org 2013-01-09 20:32 ` jakub at gcc dot gnu.org 2013-01-10 9:26 ` jakub at gcc dot gnu.org 2013-01-10 9:32 ` [Bug middle-end/55921] [4.6/4.7 " jakub at gcc dot gnu.org 2013-01-12 2:03 ` danglin at gcc dot gnu.org 2013-01-30 2:57 ` danglin at gcc dot gnu.org 2013-02-01 14:09 ` jakub at gcc dot gnu.org 2013-02-01 14:30 ` [Bug middle-end/55921] [4.6 " jakub at gcc dot gnu.org 2013-04-03 18:20 ` jakub 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-55921-4-ylihM2u95r@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).