public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "nickc at redhat dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/49801] df_live_verify_transfer_functions fails with to use of CC_REGNUM and checking enabled in rx backend Date: Tue, 04 Oct 2011 09:09:00 -0000 [thread overview] Message-ID: <bug-49801-4-efIQhiOrbw@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-49801-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49801 Nick Clifton <nickc at redhat dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nickc at redhat dot com --- Comment #2 from Nick Clifton <nickc at redhat dot com> 2011-10-04 09:08:57 UTC --- Hi Paulo, Is this bug still reproducible for you ? I tried building an rx-elf toolchain from the current 4.6 branch sources and I could not reproduce the problem... Cheers Nick
next prev parent reply other threads:[~2011-10-04 9:09 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-07-21 8:47 [Bug c/49801] New: " Paulo.Matos at csr dot com 2011-07-21 9:03 ` [Bug c/49801] " Paulo.Matos at csr dot com 2011-08-11 8:45 ` [Bug middle-end/49801] " Paulo.Matos at csr dot com 2011-10-04 9:09 ` nickc at redhat dot com [this message] 2011-10-05 11:08 ` Paulo.Matos at csr dot com 2011-10-06 14:22 ` nickc at redhat dot com 2011-10-06 14:25 ` nickc at redhat dot com 2011-10-06 21:37 ` rth at gcc dot gnu.org 2011-10-06 21:59 ` rth at gcc dot gnu.org 2011-10-07 7:35 ` bonzini at gnu dot org 2011-10-10 13:31 ` nickc at gcc dot gnu.org 2011-10-10 13:35 ` nickc at redhat dot com 2011-10-11 7:50 ` nickc at gcc dot gnu.org 2011-10-17 15:28 ` Paulo.Matos at csr dot com 2012-01-20 9:01 ` bonzini at 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-49801-4-efIQhiOrbw@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).