mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Brian Gerst <bgerst@didntduck.org>
To: "Igor Yu. Zhbanov" <bsg@uniyar.ac.ru>
Cc: "Randy.Dunlap" <rddunlap@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: __buggy_fxsr_alignment() not found.
Date: Thu, 04 Mar 2004 08:21:14 -0500	[thread overview]
Message-ID: <40472D4A.9000607@quark.didntduck.org> (raw)
In-Reply-To: <Pine.GSO.3.96.SK.1040304140003.4028A-100000@univ.uniyar.ac.ru>

Igor Yu. Zhbanov wrote:
> On Mon, 1 Mar 2004, Randy.Dunlap wrote:
> 
> 
>>On Sun, 29 Feb 2004 20:02:12 +0300 (MSK) Igor Yu. Zhbanov wrote:
>>
>>| Hello!
>>| My system is:
>>| AMD K6-II 450
>>| Linux-2.4.24
>>| glibc-2.2.5
>>| 
>>| I cannot compile 2.4.24 kernel because linker says:
>>| init/main.o: In function `check_fpu':
>>| init/main.o(.text.init+0x53): undefined reference to `__buggy_fxsr_alignment'
>>| 
>>| It's prototype is in inculude/asm-i386/bugs.h:
>>| -----
>>| /* 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();
>>| -----
>>| But there is no realisation of this function in source files.
>>| When I comment the lines above, everything works.
>>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>This function is not supposed to be defined anywhere.
>>It is there to indicate a build error and to keep the kernel
>>build from completing successfully.
>>
>>For some reason, with your config (and CPU arch.) and compiler,
>>the 'fxsave' field is not on a 16-byte alignment.  Have you applied
>>any patches to 2.4.24?  What version of gcc are you using (gcc -v)?
>>
> 
> 
> My compiler is pgcc-2.95.3 (gcc optimized for Pentium).
> And I use security patch from OpenWall.
> Here is my config file:

Get a newer compiler.  It's either not getting the alignment of 
thread.i387.fxsave right or not optimizing the test away properly.

--
				Brian Gerst

      parent reply	other threads:[~2004-03-04 13:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-29 17:02 Igor Yu. Zhbanov
2004-02-29 17:54 ` Michael Frank
2004-03-01 20:24 ` Randy.Dunlap
2004-03-04 11:01   ` Igor Yu. Zhbanov
2004-03-04 13:18     ` Mikael Pettersson
2004-03-04 13:21     ` Brian Gerst [this message]

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=40472D4A.9000607@quark.didntduck.org \
    --to=bgerst@didntduck.org \
    --cc=bsg@uniyar.ac.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rddunlap@osdl.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®