public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl at gcc dot gnu.org" <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 05:00:00 -0000 [thread overview] Message-ID: <bug-47502-4-Fuk7LtCTsk@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 #4 from hjl at gcc dot gnu.org <hjl at gcc dot gnu.org> 2011-01-28 02:15:25 UTC --- Author: hjl Date: Fri Jan 28 02:15:22 2011 New Revision: 169351 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=169351 Log: Never combine asm statement. gcc/ 2011-01-27 H.J. Lu <hongjiu.lu@intel.com> PR rtl-optimization/47502 * combine.c (cant_combine_insn_p): Never combine asm statement. gcc/testsuite/ 2011-01-27 H.J. Lu <hongjiu.lu@intel.com> PR rtl-optimization/47502 * gcc.target/i386/pr47502-1.c: New. * gcc.target/i386/pr47502-2.c: Likewise. Added: branches/x32/gcc/testsuite/gcc.target/i386/pr47502-1.c branches/x32/gcc/testsuite/gcc.target/i386/pr47502-2.c Modified: branches/x32/gcc/ChangeLog.x32 branches/x32/gcc/combine.c branches/x32/gcc/testsuite/ChangeLog.x32
next prev parent reply other threads:[~2011-01-28 2:15 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 2011-01-28 3:47 ` hjl.tools at gmail dot com 2011-01-28 5:00 ` hjl at gcc dot gnu.org [this message] 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-Fuk7LtCTsk@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).