public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gjl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/54888] GCC with -Os is faster than -O3 on some AVR code
Date: Sat, 02 Feb 2013 14:21:00 -0000 [thread overview]
Message-ID: <bug-54888-4-EFsVZkmTcQ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54888-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54888
Georg-Johann Lay <gjl at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
CC|gjl at gcc dot gnu.org |
Resolution| |INVALID
--- Comment #6 from Georg-Johann Lay <gjl at gcc dot gnu.org> 2013-02-02 14:21:27 UTC ---
Closed as invalid. No answer and no valid test case for over 3 months now.
prev parent reply other threads:[~2013-02-02 14:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-10 14:51 [Bug c/54888] New: " mojo at world3 dot net
2012-10-10 14:51 ` [Bug c/54888] " mojo at world3 dot net
2012-10-21 20:41 ` [Bug target/54888] " gjl at gcc dot gnu.org
2012-10-22 12:41 ` mojo at world3 dot net
2012-10-22 12:56 ` rguenth at gcc dot gnu.org
2012-10-22 20:11 ` gjl at gcc dot gnu.org
2013-02-02 14:21 ` gjl at gcc dot gnu.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-54888-4-EFsVZkmTcQ@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: link
Be 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).