public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bill Pringlemeir <bpringle@sympatico.ca>
To: linux-kernel@vger.kernel.org
Subject: Re: APIC, AMD-K6/2 -mcpu=586...
Date: 18 May 2001 13:04:09 -0400	[thread overview]
Message-ID: <m2d796twqe.fsf@sympatico.ca> (raw)
In-Reply-To: <m2u22ibww6.fsf@sympatico.ca>
In-Reply-To: Bill Pringlemeir's message of "18 May 2001 09:38:01 -0400"

>>>>> "WJP" == Bill Pringlemeir <bpringle@sympatico.ca> writes:
[snip]
 WJP> I have the 2.4.4 distribution from kernel.org.

 WJP>  "http://www.kernel.org/pub/linux/kernel/v2.4/"

 WJP> I have a Mandrake system and selected the AMD processors and
 WJP> APIC option.  The egcs-2.91.66 compiler with -mcpu=586.  It
 WJP> appears that the structure alignment of the floating point

Sorry,

I compiled from a user account and `/usr/bin' was before
`/usr/local/bin' on my path.  I had actually installed the tools as
per Documentation/Changes, honest! I was compiling with the
pgcc-2.91.66 and not egcs-2.91.66.  The root account was set up to use
egcs-2.91.66.

Why don't the build scripts run a dummy file to determine where the 
floating point registers should be placed?

...
const int value = offsetof(struct task_struct, thread.i387.fxsave) & 15;
...

VAL = objdump --all-headers foo.o | grep value | cut -c 48-57
PAD_SIZE = objdump --start-address=$VAL --disassemble-all foo.o | cut...

Or perhaps some better method for determining the offset on the host,

Compiling and execute won't work in cross development mode...

int main(){return offsetof(struct task_struct, thread.i387.fxsave) & 15;}

Perhaps this is a bit much to demand, instead of having a specific
compiler.

fwiw,
Bill Pringlemeir.




  reply	other threads:[~2001-05-18 17:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-18 13:38 APIC, AMD-K6/2 -mcpu=586 Bill Pringlemeir
2001-05-18 17:04 ` Bill Pringlemeir [this message]
2001-05-18 18:34   ` J . A . Magallon
2001-05-18 18:47     ` Bill Pringlemeir
2001-05-18 19:20       ` Bill Pringlemeir

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=m2d796twqe.fsf@sympatico.ca \
    --to=bpringle@sympatico.ca \
    --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