From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "Tomasz K³oczko" <kloczek@rudy.mif.pg.gda.pl>,
"Alan Cox" <laughing@shared-source.org>,
linux-kernel@vger.kernel.org
Subject: Re: Linux 2.2.20-pre4
Date: Tue, 19 Jun 2001 17:48:09 -0400 [thread overview]
Message-ID: <3B2FC899.3F0105F1@mandrakesoft.com> (raw)
In-Reply-To: <E15CS0l-0006co-00@the-village.bc.nu>
Alan Cox wrote:
>
> > On Tue, 19 Jun 2001, Alan Cox wrote:
> > [..]
> > > o Fix refclock build with newer gcc (Jari Ruusu)
> >
> > Is it mean now kernel 2.2 with prepatch is (or will be) gcc 3.0 ready ?
> > If not what must be fixed/chenged to be ready ?
>
> It wont build with gcc 3.0 yet. To start with gcc 3.0 will assume it can
> insert calls to 'memcpy'
IMHO omitting -fno-builtin when compiling the kernel was always a risky
proposition... Since we provide our own copies of many of the builtins
[which are used in the kernel] anyway... why not always -fno-builtin,
and then call __builtin_foo when we really want the compiler's version..
gcc 3.0 without -fno-builtin is perfectly allowed to assume it can
insert calls to memcpy..
--
Jeff Garzik | Andre the Giant has a posse.
Building 1024 |
MandrakeSoft |
next prev parent reply other threads:[~2001-06-19 21:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-19 14:29 Linux 2.2.20-pre4 Alan Cox
2001-06-19 15:22 ` Jochen Striepe
2001-06-19 15:23 ` Alan Cox
2001-06-19 16:26 ` Jochen Striepe
2001-06-19 16:42 ` Jochen Striepe
2001-06-19 20:03 ` Tomasz Kłoczko
2001-06-19 20:22 ` Alan Cox
2001-06-19 21:48 ` Jeff Garzik [this message]
2001-06-19 21:57 ` Alan Cox
2001-06-19 22:16 ` Jeff Garzik
2001-06-19 22:03 ` Philip Blundell
2001-06-19 22:18 ` Jeff Garzik
2001-06-20 21:23 ` Eric Lammerts
2001-06-21 8:43 ` Luigi Genoni
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=3B2FC899.3F0105F1@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=kloczek@rudy.mif.pg.gda.pl \
--cc=laughing@shared-source.org \
--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