public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mmitchel at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/26658] [4.0/4.1/4.2/4.3 Regression] memcpy/memset are not inlining with -march=athlon-xp and size of 128
Date: Wed, 14 Feb 2007 09:10:00 -0000 [thread overview]
Message-ID: <20070214090426.3515.qmail@sourceware.org> (raw)
In-Reply-To: <bug-26658-12348@http.gcc.gnu.org/bugzilla/>
--
mmitchel at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|4.1.2 |4.1.3
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26658
next prev parent reply other threads:[~2007-02-14 9:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-12 20:11 [Bug regression/26658] New: perfomance regression between gcc 3.4.5 and 4.* nbkolchin at gmail dot com
2006-03-12 20:12 ` [Bug regression/26658] " nbkolchin at gmail dot com
2006-03-12 20:13 ` nbkolchin at gmail dot com
2006-03-12 20:14 ` nbkolchin at gmail dot com
2006-03-12 21:07 ` rguenth at gcc dot gnu dot org
2006-03-12 21:12 ` rguenth at gcc dot gnu dot org
2006-06-04 19:52 ` [Bug regression/26658] [4.0/4.1/4.2 Regression] " jsm28 at gcc dot gnu dot org
2006-06-04 19:56 ` [Bug target/26658] " pinskia at gcc dot gnu dot org
2006-07-05 17:52 ` mmitchel at gcc dot gnu dot org
2006-08-27 21:59 ` [Bug target/26658] [4.0/4.1/4.2 Regression] memcpy/memset are not inlining with -march=athlon-xp and size of 128 pinskia at gcc dot gnu dot org
2007-02-14 9:10 ` mmitchel at gcc dot gnu dot org [this message]
2007-11-07 9:15 ` [Bug target/26658] [4.0/4.1/4.2/4.3 " jakub at gcc dot gnu dot org
2008-01-13 15:42 ` [Bug target/26658] [4.1/4.2/4.3 " rguenth 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=20070214090426.3515.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).