From: Bill Pringlemeir <bpringle@sympatico.ca>
To: "J . A . Magallon" <jamagallon@able.es>
Cc: linux-kernel@vger.kernel.org
Subject: Re: APIC, AMD-K6/2 -mcpu=586...
Date: 18 May 2001 15:20:26 -0400 [thread overview]
Message-ID: <m23da2mpl1.fsf@sympatico.ca> (raw)
In-Reply-To: <m2u22ibww6.fsf@sympatico.ca> <m2d796twqe.fsf@sympatico.ca> <20010518203446.A1066@werewolf.able.es> <m2eltm335t.fsf@sympatico.ca>
In-Reply-To: Bill Pringlemeir's message of "18 May 2001 14:47:26 -0400"
>>>>> "JAM" == J A Magallon <jamagallon@able.es> writes:
JAM> That is not the problem. The problem is that the registers have
JAM> to lay in a defined way, transcribed to a C struct, and that
JAM> pgcc lays badly that struct.
WJP> Yes, I understand that. I was showing a way to find the value
WJP> of padding needed to align the register store in the structure.
WJP> Perhaps I should have shown a mod to asm/processor.h,
[snip]
WJP> I was describing a way to make things independent of the
WJP> compiler layout of the structs. However, this complicates the
WJP> build process, and people might not like the padding due to
WJP> cache alignment details.
Sorry, they would obviously declare it as such if the kernel developers
wanted to.
/* floating point info */
unsigned char fpAlign[0] __attribute__ ((aligned (16)));
union i387_union i387;
This is a much simpler way of achieving what I was trying to explain
previously. I think that this syntax has been in the GCC extensions
for some time.
regards,
Bill Pringlemeir.
prev parent reply other threads:[~2001-05-18 19:22 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
2001-05-18 18:34 ` J . A . Magallon
2001-05-18 18:47 ` Bill Pringlemeir
2001-05-18 19:20 ` Bill Pringlemeir [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=m23da2mpl1.fsf@sympatico.ca \
--to=bpringle@sympatico.ca \
--cc=jamagallon@able.es \
--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