From: Adrian Bunk <bunk@stusta.de>
To: Andi Kleen <ak@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] kill IN_STRING_C
Date: Mon, 8 Nov 2004 19:34:49 +0100 [thread overview]
Message-ID: <20041108183449.GC15077@stusta.de> (raw)
In-Reply-To: <20041108175120.GB27525@wotan.suse.de>
On Mon, Nov 08, 2004 at 06:51:20PM +0100, Andi Kleen wrote:
> On Mon, Nov 08, 2004 at 05:31:01PM +0100, Adrian Bunk wrote:
> > On Mon, Nov 08, 2004 at 05:19:35PM +0100, Andi Kleen wrote:
> > > > Rethinking it, I don't even understand the sprintf example in your
> > > > changelog entry - shouldn't an inclusion of kernel.h always get it
> > > > right?
> > >
> > > Newer gcc rewrites sprintf(buf,"%s",str) to strcpy(buf,str) transparently.
> >
> > Which gcc is "Newer"?
>
> I saw it with 3.3-hammer, which had additional optimizations in this
> area at some point. Note that 3.3-hammer is widely used. I don't
> know if 3.4 does it in the same way.
Is this a -hammer specific problem?
If yes, does a -no-builtin-sprintf fix it?
Or is the problem a missing #include <linux/kernel.h> at the top of
include/linux/string.h?
> -Andi
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2004-11-08 18:37 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-07 14:24 [2.6 patch] kill IN_STRING_C Adrian Bunk
2004-11-08 13:44 ` Andi Kleen
2004-11-08 15:34 ` Adrian Bunk
2004-11-08 16:19 ` Andi Kleen
2004-11-08 16:31 ` Adrian Bunk
2004-11-08 17:51 ` Andi Kleen
2004-11-08 18:34 ` Adrian Bunk [this message]
2004-11-08 19:01 ` Andi Kleen
2004-11-08 23:38 ` Use -ffreestanding? Adrian Bunk
2004-11-09 5:01 ` Andi Kleen
2004-11-10 1:45 ` [2.6 patch] " Adrian Bunk
2004-11-10 1:51 ` Linus Torvalds
2004-11-10 1:57 ` Adrian Bunk
2004-11-10 21:01 ` Bill Davidsen
2004-11-08 18:04 ` [2.6 patch] kill IN_STRING_C Paweł Sikora
2004-11-08 18:31 ` Adrian Bunk
2004-11-08 19:12 ` linux-os
2004-11-08 21:27 ` Adrian Bunk
2004-11-08 22:15 ` linux-os
2004-11-08 22:29 ` Adrian Bunk
2004-11-08 22:57 ` linux-os
2004-11-08 23:08 ` Adrian Bunk
2004-11-09 12:44 ` linux-os
2004-11-09 13:43 ` linux-os
2004-11-08 18:22 ` linux-os
2004-11-08 19:31 ` Ryan Cumming
2004-11-09 13:58 ` Arnd Bergmann
2004-11-10 2:30 ` Adrian Bunk
[not found] ` <200411081942.38954.pluto@pld-linux.org>
[not found] ` <20041108185222.GE15077@stusta.de>
2004-11-08 19:11 ` Paweł Sikora
2004-11-08 21:25 ` Adrian Bunk
-- strict thread matches above, loose matches on Subject: below --
2004-11-08 18:43 Paweł Sikora
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=20041108183449.GC15077@stusta.de \
--to=bunk@stusta.de \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.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 NNTP newsgroup(s).