From: David Woodhouse <dwmw2@infradead.org>
To: Russell King <rmk@arm.linux.org.uk>
Cc: mythos <papadako@csd.uoc.gr>, linux-kernel@vger.kernel.org
Subject: Re: Can't compile 2.4.3 with agcc
Date: Mon, 23 Apr 2001 16:52:53 +0100 [thread overview]
Message-ID: <24644.988041173@redhat.com> (raw)
In-Reply-To: <20010423154821.A26340@flint.arm.linux.org.uk>
In-Reply-To: <20010423154821.A26340@flint.arm.linux.org.uk> <Pine.GSO.4.33.0104231611090.15682-100000@iridanos.csd.uch.gr>
rmk@arm.linux.org.uk said:
> On Mon, Apr 23, 2001 at 04:13:47PM +0300, mythos wrote:
> > init/main.o(.text.init+0x65): undefined reference to `__buggy_fxsr_alignment'
> This is a FAQ! (sorry, but I don't know if it is in a FAQ or not).
> IIRC, you can't use pgcc to compile linux kernels.
Then the kernel should say so, rather than giving a cryptic message like
that, and containing code which isn't actually guaranteed to compile, even
with a compiler which _does_ align the structure as we want it.
Index: include/asm/bugs.h
===================================================================
RCS file: /inst/cvs/linux/include/asm-i386/bugs.h,v
retrieving revision 1.2.2.16
diff -u -r1.2.2.16 bugs.h
--- include/asm/bugs.h 2001/01/18 13:56:53 1.2.2.16
+++ include/asm/bugs.h 2001/04/23 15:45:28
@@ -80,8 +80,10 @@
* Verify that the FXSAVE/FXRSTOR data will be 16-byte aligned.
*/
if (offsetof(struct task_struct, thread.i387.fxsave) & 15) {
- extern void __buggy_fxsr_alignment(void);
- __buggy_fxsr_alignment();
+ printk(KERN_EMERG "ERROR: FXSAVE data are not 16-byte aligned in task_struct.\n");
+ printk(KERN_EMERG "This is usually caused by a buggy compiler (perhaps pgcc?)\n");
+ printk(KERN_EMERG "Cannot continue.\n");
+ for (;;) ;
}
if (cpu_has_fxsr) {
printk(KERN_INFO "Enabling fast FPU save and restore... ");
--
dwmw2
next prev parent reply other threads:[~2001-04-23 15:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-23 13:13 Can't compile 2.4.3 with agcc mythos
2001-04-23 14:48 ` Russell King
2001-04-23 15:27 ` Alan Cox
2001-04-23 15:52 ` David Woodhouse [this message]
2001-04-23 17:57 ` Ingo Oeser
2001-04-23 19:43 ` Alan Cox
2001-04-23 20:46 ` David Woodhouse
2001-04-23 21:03 ` Matan Ziv-Av
2001-04-23 21:16 ` David Woodhouse
2001-04-23 22:32 ` Andrzej Krzysztofowicz
2001-04-23 22:54 ` David Woodhouse
2001-04-24 8:53 ` Russell King
2001-04-24 12:37 ` David Woodhouse
2001-04-23 22:25 ` Horst von Brand
2001-04-23 22:35 ` David Woodhouse
2001-04-24 13:28 ` Horst von Brand
2001-04-24 13:30 ` David Woodhouse
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=24644.988041173@redhat.com \
--to=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=papadako@csd.uoc.gr \
--cc=rmk@arm.linux.org.uk \
/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.