public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kevin at planetsaphire dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/23605] memset() Optimization on x86-32 bit
Date: Sun, 28 Aug 2005 20:28:00 -0000 [thread overview]
Message-ID: <20050828202621.3342.qmail@sourceware.org> (raw)
In-Reply-To: <20050828200424.23605.kevin@planetsaphire.com>
------- Additional Comments From kevin at planetsaphire dot com 2005-08-28 20:26 -------
(In reply to comment #1)
> Are you compiling your source at -O0 or GCC at -O0? If the former, then this
is most likely not a bug.
-O2 does not do any optimization at all, and -O0 optimizes the code to a certain
extent. The testcase I submitted was compiled with the -O0 flag.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23605
next prev parent reply other threads:[~2005-08-28 20:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-28 20:08 [Bug c/23605] New: " kevin at planetsaphire dot com
2005-08-28 20:16 ` [Bug target/23605] " pinskia at gcc dot gnu dot org
2005-08-28 20:26 ` kevin at planetsaphire dot com
2005-08-28 20:28 ` kevin at planetsaphire dot com [this message]
2005-08-28 20:34 ` pinskia at gcc dot gnu dot org
2005-08-28 20:37 ` kevin at planetsaphire dot com
2005-08-28 20:45 ` pinskia at gcc dot gnu dot org
2005-08-28 22:18 ` kevin at planetsaphire dot com
2005-08-28 23:00 ` pinskia at gcc dot gnu dot org
2005-08-28 23:03 ` pinskia at gcc dot gnu dot org
2005-08-28 23:25 ` ian at airs dot com
2005-08-28 23:42 ` ian at airs dot com
2005-08-29 0:36 ` kevin at planetsaphire dot com
2005-08-29 0:49 ` kevin at planetsaphire dot com
[not found] <bug-23605-11252@http.gcc.gnu.org/bugzilla/>
2005-11-02 17:16 ` pinskia at gcc dot gnu dot org
2006-09-18 1:45 ` pinskia at gcc dot gnu dot org
[not found] <bug-23605-4@http.gcc.gnu.org/bugzilla/>
2012-01-11 14:21 ` rguenth 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=20050828202621.3342.qmail@sourceware.org \
--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).