public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "steven at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/19204] [m68k] pea can force reloads that cause inefficient code Date: Sat, 26 Feb 2011 00:18:00 -0000 [thread overview] Message-ID: <bug-19204-4-BQ9isBrH6O@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-19204-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19204 Steven Bosscher <steven at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |SUSPENDED --- Comment #6 from Steven Bosscher <steven at gcc dot gnu.org> 2011-02-26 00:17:55 UTC --- Also fine, not closed. Great to see that you pay enough attention to stop the reporter from closing his own PRs. I wish you would be just as fast with actually doing something about them. It is not even clear whether these problems still exist! If this still not OK with you, I suggest you do something about these 15+ years old problems, or close these and re-file under your own account. They may not bother you but I don't want them anymore in my list.
next prev parent reply other threads:[~2011-02-26 0:18 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-19204-4@http.gcc.gnu.org/bugzilla/> 2011-02-25 23:15 ` steven at gcc dot gnu.org 2011-02-26 0:13 ` schwab@linux-m68k.org 2011-02-26 0:18 ` steven at gcc dot gnu.org [this message] [not found] <bug-19204-280@http.gcc.gnu.org/bugzilla/> 2010-02-12 22:02 ` steven at gcc dot gnu dot org 2010-02-12 22:02 ` steven at gcc dot gnu dot org 2004-12-30 12:20 [Bug target/19204] New: " steven at gcc dot gnu dot org 2004-12-31 13:34 ` [Bug target/19204] " schwab at suse dot de 2005-06-19 14:49 ` pinskia at gcc dot 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-19204-4-BQ9isBrH6O@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).