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 inline-asm/23200] [4.3/4.4/4.5/4.6 Regression] rejects "i"(&var + 1) Date: Thu, 03 Feb 2011 13:23:00 -0000 [thread overview] Message-ID: <bug-23200-4-Fi9UpGifVk@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-23200-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23200 --- Comment #46 from Jakub Jelinek <jakub at gcc dot gnu.org> 2011-02-03 13:23:02 UTC --- Created attachment 23236 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=23236 gcc46-pr23200-2.patch Or we could perhaps for EXPAND_INITIALIZER just try harder to look at SSA_NAME definitions, as done in this patch. EXPAND_INITIALIZER expansion is used just in a couple of places, usually the expression is already known to be constant, and in stmt.c it is for asm inputs with constraints that allow neither a register nor memory.
next prev parent reply other threads:[~2011-02-03 13:23 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-23200-4@http.gcc.gnu.org/bugzilla/> 2011-02-03 13:19 ` jakub at gcc dot gnu.org 2011-02-03 13:23 ` jakub at gcc dot gnu.org [this message] 2011-02-04 15:51 ` jakub at gcc dot gnu.org 2011-02-04 15:53 ` [Bug inline-asm/23200] [4.3/4.4/4.5 " jakub at gcc dot gnu.org 2011-06-27 13:13 ` rguenth at gcc dot gnu.org 2012-03-13 13:17 ` [Bug inline-asm/23200] [4.5 " jakub at gcc dot gnu.org 2012-07-02 9:22 ` rguenth at gcc dot gnu.org [not found] <bug-23200-11104@http.gcc.gnu.org/bugzilla/> 2010-05-22 19:00 ` [Bug inline-asm/23200] [4.3/4.4/4.5/4.6 " rguenth at gcc dot gnu dot org 2010-08-18 22:43 ` pinskia at gcc dot gnu dot 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-23200-4-Fi9UpGifVk@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).