From: James Bottomley <James.Bottomley@steeleye.com>
To: PARISC list <parisc-linux@lists.parisc-linux.org>
Subject: [parisc-linux] gcc-3.3 and problems in the 64 bit kernel
Date: 13 Feb 2004 09:20:27 -0500 [thread overview]
Message-ID: <1076682028.2159.10.camel@mulgrave> (raw)
our 64 bit gcc-3.3 (all versions) has a miscompilation problem that
results in a BUG() in the 64 bit kernel. This shows up as:
kernel BUG at mm/shmem.c:585
The problem turns out to be that gcc-3.3 is violating the OPD rules for
static functions (OPD == Official Procedure Descriptor and is supposed
to ensure that there's only one function descriptor per function,
allowing pointers to function descriptors to be compared directly
instead of having to be dereferenced).
The problem is generated because this comparison:
if (inode->i_op->truncate == shmem_truncate)
which is a function pointer comparison is always false.
There are several other function pointer comparisons in the kernel which
are in danger of failing in this manner, so the resulting kernel will
not operate correctly.
Hopefully, the gcc people will be able to fix this, but in the mean time
people should stick to gcc-3.0 to compile 64 bit kernels. (gcc-3.3 is
fine for 32 bit parisc kernels).
James
reply other threads:[~2004-02-13 14:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1076682028.2159.10.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=parisc-linux@lists.parisc-linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.