From: Jim Wilson <jim.wilson@linaro.org>
To: James Greenhalgh <james.greenhalgh@arm.com>
Cc: Kyrylo Tkachov <Kyrylo.Tkachov@arm.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
Alan Lawrence <Alan.Lawrence@arm.com>
Subject: Re: [PATCH, AARCH64] make stdarg functions work with +nofp
Date: Tue, 16 Jun 2015 21:05:00 -0000 [thread overview]
Message-ID: <CABXYE2UEMBuzJubcVsvuUzzRZ4UmXQKtVbDA6j8zmP_bUdy6nQ@mail.gmail.com> (raw)
In-Reply-To: <20150616084626.GA31077@arm.com>
On Tue, Jun 16, 2015 at 1:46 AM, James Greenhalgh
<james.greenhalgh@arm.com> wrote:
> I'm happy for this to be backported.
Thanks. Applied.
> I think Grub probably wants to change if they want to be safe, from
> what I've read it looks like they are hoping to use something like a
> standard printf without touching the FP registers, which is suspect...
Grub has its own printf code, as it can't use glibc, and the
grub_printf function doesn't support FP format codes. So this should
not be a problem for grub.
FYI In the git tree, grub changed from using +nofp to
-mgeneral-regs-only on June 2, because the kernel uses
-mgeneral-regs-only, and because +nofp was broken in gcc-5-branch.
But we still needed the patch backported for people who could not or
didn't want to upgrade grub.
Jim
prev parent reply other threads:[~2015-06-16 20:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-23 7:00 Jim Wilson
2015-06-02 9:44 ` James Greenhalgh
2015-06-02 10:45 ` Kyrill Tkachov
2015-06-02 11:03 ` James Greenhalgh
2015-06-09 5:18 ` Jim Wilson
2015-06-16 8:48 ` James Greenhalgh
2015-06-16 21:05 ` Jim Wilson [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=CABXYE2UEMBuzJubcVsvuUzzRZ4UmXQKtVbDA6j8zmP_bUdy6nQ@mail.gmail.com \
--to=jim.wilson@linaro.org \
--cc=Alan.Lawrence@arm.com \
--cc=Kyrylo.Tkachov@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=james.greenhalgh@arm.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).