From: Matti Aarnio <matti.aarnio@zmailer.org>
To: Shawn Starr <Shawn.Starr@Home.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [CONT PROBLEM] 2.4.1-pre3 - Undefined symbol `__buggy_fxsr_alignment'
Date: Fri, 12 Jan 2001 23:20:44 +0200 [thread overview]
Message-ID: <20010112232044.L25659@mea-ext.zmailer.org> (raw)
In-Reply-To: <3A5E4B1D.5EF1B0EB@Home.net> <3A5E7DB2.A7126A68@Home.net> <3A5E7EC4.39CC7298@Home.net> <3A5F62C6.FF3EE6B1@Home.net>
In-Reply-To: <3A5F62C6.FF3EE6B1@Home.net>; from Shawn.Starr@Home.net on Fri, Jan 12, 2001 at 03:02:15PM -0500
On Fri, Jan 12, 2001 at 03:02:15PM -0500, Shawn Starr wrote:
> Nope, its not ;/
>
> Im on a Intel Pentium 200Mhz PC, 64MB RAM,
>
> init/main.o: In function `check_fpu':
> init/main.o(.text.init+0x53): undefined reference to `__buggy_fxsr_alignment'
> make: *** [vmlinux] Error 1
>
> same fatal error. Where is this function defined in the i386 asm header?
It should not be present at all in the objects.
The compiler optimizer should remove that call,
which is just an example of similar kind of "if
optimizer fails, here is cannon-fodder to alert
users about it."
> If so, I could fix this and submit a patch.
> /* Enable FXSR and company _before_ testing for FP problems. */
> /*
> * 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();
>
> Where is this function? Where is it defined? When i grep the whole dir
> i dont see this function anywhere?
See the comment above the offsetof() call.
Now think. Figure out why things are at wrong offset.
Has something been added into task_struct lately ?
Or to thread_struct, which actually is processor context
data where this 'thread.i386.fxsave' thing resides ?
Oh yes, if compilation DOES NOT happen with -O flag,
this will also happen..
> Shawn.
/Matti Aarnio
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-12 21:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-12 0:09 Critical compile bug: 2.4.1-pre2 alpha Shawn Starr
2001-01-12 3:44 ` [PROBLEM] 2.4.1-pre2 - Undefined symbol `__buggy_fxsr_alignment' Shawn Starr
2001-01-12 3:49 ` [PROBLEM] 2.4.1-pre2 - Undefined symbol `__buggy_fxsr_alignment' - (FIXED) Shawn Starr
2001-01-12 20:02 ` [CONT PROBLEM] 2.4.1-pre3 - Undefined symbol `__buggy_fxsr_alignment' Shawn Starr
2001-01-12 21:20 ` Matti Aarnio [this message]
2001-01-12 21:30 ` Shawn Starr
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=20010112232044.L25659@mea-ext.zmailer.org \
--to=matti.aarnio@zmailer.org \
--cc=Shawn.Starr@Home.net \
--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
all inboxes | Powered by JetHome®