public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/48604] [4.5/4.6 regression] wrong code with -frename-registers Date: Thu, 14 Apr 2011 10:56:00 -0000 [thread overview] Message-ID: <bug-48604-4-IaLXapFhLG@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-48604-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48604 Eric Botcazou <ebotcazou at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Known to work| |4.4.5 Target Milestone|4.6.1 |4.5.3 Summary|[4.6 regression] wrong code |[4.5/4.6 regression] wrong |with -frename-registers |code with | |-frename-registers Known to fail| |4.5.2, 4.6.0 --- Comment #3 from Eric Botcazou <ebotcazou at gcc dot gnu.org> 2011-04-14 10:56:04 UTC --- On the 4.5 branch: .L20: addi 0,1,304 mr 3,28 b _restgpr_18_x .size fmm_setup_mmu_fn, .-fmm_setup_mmu_fn
next prev parent reply other threads:[~2011-04-14 10:56 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-04-14 8:57 [Bug target/48604] New: [PowerPC] Wrong code with -frename-registers -Os sebastian.huber@embedded-brains.de 2011-04-14 10:31 ` [Bug rtl-optimization/48604] [4.6 regression] wrong code with -frename-registers ebotcazou at gcc dot gnu.org 2011-04-14 10:31 ` ebotcazou at gcc dot gnu.org 2011-04-14 10:56 ` ebotcazou at gcc dot gnu.org [this message] 2011-04-21 9:26 ` [Bug target/48604] [4.5/4.6/4.7 " rguenth at gcc dot gnu.org 2011-04-26 17:32 ` edmar at freescale dot com 2011-04-27 10:10 ` ebotcazou at gcc dot gnu.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-48604-4-IaLXapFhLG@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).