From: Andi Kleen <ak@muc.de>
To: akpm@osdl.org
Cc: linux-kernel@vger.kernel.org
Subject: gcc 3.5 compile fixes
Date: Fri, 09 Jul 2004 12:25:56 +0200 [thread overview]
Message-ID: <m3r7rlpjd7.fsf@averell.firstfloor.org> (raw)
I tried to compile 2.6.7-bk9 with a recent gcc 3.5 snapshot on i386
and x86-64. It gave a lot of warnings and a lot of compile errors
for make allyesconfig.
On x86-64 it miscompiled the kernel (due to kernel bugs); I will send
fixes for that separately.
Most compile errors were about mixing extern and static declarations
of the same symbol. I fixed this all except for the au88x0 driver
in ALSA which had a too broken module setup (someone else will have
to tackle that)
I got one gcc internal compiler error while compiling the sunrpc
gss module. I filed an gcc bug for that.
One problem was that it didn't always inline fix_to_virt() which
resulted in undefined symbols. (gcc 3.4 and up doesn't set always
inline for normal inline). I fixed this by defining a new macro
__always_inline in compiler.h and using that for fix_to_virt
Another issue (I think already fixed in -mm) was that memmove()
needs to be moved out of line.
The result were a lot of patches for a lot of files. Instead
of spamming l-k with them all I put them in
http://www.firstfloor.org/~andi/35/
Andrew, please consider adding them to your tree.
The resulting i386 kernel booted on one machine; but failed to find
the SCSI disks on another (didn't investigate what the problem
was on the later, some more work needed on that)
-Andi
next reply other threads:[~2004-07-09 10:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-09 10:25 Andi Kleen [this message]
2004-07-09 14:39 ` gcc 3.5 compile fixes Felipe Alfaro Solana
2004-07-10 4:52 ` Andi Kleen
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=m3r7rlpjd7.fsf@averell.firstfloor.org \
--to=ak@muc.de \
--cc=akpm@osdl.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