From: Andi Kleen <ak@muc.de>
To: "Jan Beulich" <JBeulich@novell.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: i386 entry.S problems
Date: Mon, 27 Sep 2004 12:58:57 +0200 [thread overview]
Message-ID: <m3acvcf05q.fsf@averell.firstfloor.org> (raw)
In-Reply-To: <2J0sK-6Ot-5@gated-at.bofh.it> (Jan Beulich's message of "Mon, 27 Sep 2004 12:00:14 +0200")
"Jan Beulich" <JBeulich@novell.com> writes:
>
> I don't think so. Otherwise, why would arch/i386/Makefile specifically
> deal with this situation?
It shouldn't be enabled for 2.95, there are known miscompilations
caused by it there. The i386 Makefile enforces this:
cflags-$(CONFIG_REGPARM) += $(shell if [ $(GCC_VERSION) -ge 0300 ] ; then echo "-mregparm=3"; fi ;)
However this points to a bug in that when someone sets this
on 2.95 the assembly functions who check for CONFIG_REGPARM
explicitely will be subtly miscompiled. Perhaps having
a #error for this case would be better, although that
would break allyesconfig on prehistoric compilers. Maybe
it needs to be special cased in autoconf.h
-Andi
next parent reply other threads:[~2004-09-27 10:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2J0sK-6Ot-5@gated-at.bofh.it>
2004-09-27 10:58 ` Andi Kleen [this message]
2004-09-27 11:19 i386 entry.S problems Jan Beulich
-- strict thread matches above, loose matches on Subject: below --
2004-09-27 9:50 Jan Beulich
[not found] <s157d11c.077@emea1-mh.id2.novell.com>
2004-09-27 9:00 ` Christoph Hellwig
2004-09-27 7:40 Jan Beulich
2004-09-27 7:37 Jan Beulich
[not found] <2HZ5Q-3MU-17@gated-at.bofh.it>
[not found] ` <2HZSa-4nZ-63@gated-at.bofh.it>
[not found] ` <2IFew-HK-9@gated-at.bofh.it>
2004-09-26 11:38 ` Andi Kleen
2004-09-24 15:25 Jan Beulich
2004-09-24 14:12 Jan Beulich
2004-09-24 14:57 ` Arjan van de Ven
2004-09-24 15:36 ` Alan Cox
2004-09-26 11:13 ` Ingo Molnar
2004-09-24 19:12 ` Christoph Hellwig
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=m3acvcf05q.fsf@averell.firstfloor.org \
--to=ak@muc.de \
--cc=JBeulich@novell.com \
--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