public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mexas at bristol dot ac.uk" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/55221] [regression] gcc-4.6-20121102/gcc/rtl.h:2105: error: 'FIRST_PSEUDO_REGISTER' undeclared here (not in a fnction) Date: Thu, 08 Nov 2012 09:49:00 -0000 [thread overview] Message-ID: <bug-55221-4-Iv0mLU9Vmb@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-55221-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55221 --- Comment #1 from Anton Shterenlikht <mexas at bristol dot ac.uk> 2012-11-08 09:49:08 UTC --- On the same system gcc47 updated fine to gcc-4.7.3.20121103
next prev parent reply other threads:[~2012-11-08 9:49 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-11-06 12:57 [Bug rtl-optimization/55221] New: " mexas at bristol dot ac.uk 2012-11-08 9:49 ` mexas at bristol dot ac.uk [this message] 2012-11-09 10:40 ` [Bug rtl-optimization/55221] " mexas at bristol dot ac.uk 2012-11-09 10:47 ` mexas at bristol dot ac.uk 2013-01-28 17:19 ` thierry at FreeBSD dot org 2013-07-08 13:43 ` mexas at bristol dot ac.uk
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-55221-4-Iv0mLU9Vmb@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).