From: Pavel Roskin <proski@gnu.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH 2/2] Eliminate incorrect check for grub_I386_CHECK_REGPARM_BUG
Date: Fri, 22 May 2009 17:18:24 -0400 [thread overview]
Message-ID: <1243027104.2174.8.camel@mj> (raw)
In-Reply-To: <20090522043638.10755.42855.stgit@ct.roinet.com>
On Fri, 2009-05-22 at 00:36 -0400, Pavel Roskin wrote:
> NESTED_FUNC_ATTR is defined to "__attribute__ ((__regparm__ (1))" for
> i386 targets regardless of the outcome of the test. Since
> NESTED_FUNC_ATTR is on the way out, a better test won't be written.
>
> To be safe, define NESTED_FUNC_ATTR whenever we are compiling the
> specific file for i386 architecture, even the target platform is not
> i386 (i.e. compiling utilities when the host is i386 and the target is
> not).
>
> ChangeLog:
>
> * aclocal.m4 (grub_I386_CHECK_REGPARM_BUG): Remove.
> * configure.ac: Don't call grub_I386_CHECK_REGPARM_BUG. Define
> NESTED_FUNC_ATTR by AH_BOTTOM. Base NESTED_FUNC_ATTR value
> solely on the compile time architecture.
I've committed this with a minor change. regparm(1) is not used for the
utilities, as they are compiled without -mregparm(3). This fixes
grub-setup on i386.
We still need to get rid of NESTED_FUNC_ATTR eventually, but the
immediate user-visible issue is resolved now.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2009-05-22 21:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-22 4:36 [PATCH 1/2] Reduce the special variables area in kern/i386/pc/startup.S Pavel Roskin
2009-05-22 4:36 ` [PATCH 2/2] Eliminate incorrect check for grub_I386_CHECK_REGPARM_BUG Pavel Roskin
2009-05-22 21:18 ` Pavel Roskin [this message]
2009-05-22 20:50 ` [PATCH 1/2] Reduce the special variables area in kern/i386/pc/startup.S Pavel Roskin
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=1243027104.2174.8.camel@mj \
--to=proski@gnu.org \
--cc=grub-devel@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.