public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "philb at gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/49422] [arm] unable to find a register to spill in class 'VFP_LO_REGS' Date: Wed, 22 Jun 2011 13:47:00 -0000 [thread overview] Message-ID: <bug-49422-4-ghErN5l6HY@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-49422-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49422 philb at gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID --- Comment #2 from philb at gnu dot org 2011-06-22 13:46:51 UTC --- I can't reproduce it now either. I think I must have been testing against a locally patched tree rather than the clean one by mistake. I'll close this bug until/unless I can reproduce the failure on a released version.
prev parent reply other threads:[~2011-06-22 13:47 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-06-15 13:32 [Bug target/49422] New: " philb at gnu dot org 2011-06-20 18:58 ` [Bug target/49422] " mikpe at it dot uu.se 2011-06-22 13:47 ` philb at gnu dot org [this message]
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-49422-4-ghErN5l6HY@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).