public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/47502] [x32] can’t find a register in class ‘SIREG’ while reloading ‘asm’ Date: Fri, 28 Jan 2011 03:27:00 -0000 [thread overview] Message-ID: <bug-47502-4-6eTElxVWMw@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-47502-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47502 --- Comment #2 from H.J. Lu <hjl.tools at gmail dot com> 2011-01-28 00:16:53 UTC --- It is a bad idea for combine to replace pseudo registers in asm statements with hard registers, which is the job of RA.
next prev parent reply other threads:[~2011-01-28 0:17 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-01-28 0:23 [Bug target/47502] New: " hjl.tools at gmail dot com 2011-01-28 3:23 ` [Bug rtl-optimization/47502] " hjl.tools at gmail dot com 2011-01-28 3:27 ` hjl.tools at gmail dot com [this message] 2011-01-28 3:47 ` hjl.tools at gmail dot com 2011-01-28 5:00 ` hjl at gcc dot gnu.org 2011-03-21 8:06 ` hjl at gcc dot gnu.org 2011-04-02 5:47 ` hjl at gcc dot gnu.org 2011-07-28 14:01 ` hjl.tools at gmail dot com
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-47502-4-6eTElxVWMw@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).