From: Andrew Haley <aph@redhat.com>
To: Christophe Saout <christophe@saout.de>
Cc: Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>,
gcc@gcc.gnu.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
jakub@redhat.com, Gerold Jury <gerold.ml@inode.at>,
Jan Hubicka <hubicka@ucw.cz>, Andrew Morton <akpm@osdl.org>
Subject: Re: [BUG mm] "fixed" i386 memcpy inlining buggy
Date: Wed, 6 Apr 2005 13:36:05 +0100 [thread overview]
Message-ID: <16979.55221.574028.90931@cuddles.cambridge.redhat.com> (raw)
In-Reply-To: <1112789157.32279.13.camel@leto.cs.pocnet.net>
I'm having a little difficulty understanding what this is for. Is it
that gcc's builtin memcpy expander generates bad code, or that older
versions of gcc generate bad code, or what? gcc generates too much
code?
Andrew.
next prev parent reply other threads:[~2005-04-06 12:37 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-29 14:37 memcpy(a,b,CONST) is not inlined by gcc 3.4.1 in Linux kernel Denis Vlasenko
2005-03-29 15:06 ` Richard Guenther
2005-03-29 15:08 ` Nathan Sidwell
2005-03-29 15:13 ` Jakub Jelinek
2005-03-29 15:42 ` Andrew Pinski
2005-03-30 2:27 ` Gerold Jury
2005-03-30 6:15 ` Denis Vlasenko
2005-04-01 21:43 ` Jan Hubicka
2005-04-02 12:18 ` Denis Vlasenko
2005-04-02 12:26 ` Denis Vlasenko
2005-04-05 16:34 ` [BUG mm] "fixed" i386 memcpy inlining buggy Christophe Saout
2005-04-06 10:14 ` Denis Vlasenko
2005-04-06 11:05 ` Dave Korn
2005-04-06 11:13 ` Dave Korn
2005-04-06 11:53 ` Dave Korn
2005-04-06 11:56 ` Dave Korn
2005-04-06 13:18 ` Richard B. Johnson
2005-04-06 14:16 ` Denis Vlasenko
2005-04-06 12:05 ` Christophe Saout
2005-04-06 12:36 ` Andrew Haley [this message]
2005-04-06 15:18 ` Paolo Bonzini
2005-04-06 16:11 ` Denis Vlasenko
2005-03-29 20:22 ` [PATCH] fix i386 memcpy Denis Vlasenko
2005-03-29 20:24 ` Denis Vlasenko
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=16979.55221.574028.90931@cuddles.cambridge.redhat.com \
--to=aph@redhat.com \
--cc=akpm@osdl.org \
--cc=christophe@saout.de \
--cc=gcc@gcc.gnu.org \
--cc=gerold.ml@inode.at \
--cc=hubicka@ucw.cz \
--cc=jakub@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vda@port.imtp.ilyichevsk.odessa.ua \
/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
all inboxes | Powered by JetHome®