From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: Alexei Fedorov <Alexei.Fedorov@arm.com>
Cc: Leif Lindholm <leif.lindholm@linaro.org>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
"liming.gao@intel.com" <liming.gao@intel.com>,
"yonghong.zhu@intel.com" <yonghong.zhu@intel.com>,
Evan Lloyd <Evan.Lloyd@arm.com>
Subject: Re: [PATCH 2/2] BaseTools/tools_def AARCH64: avoid SIMD register in XIP code
Date: Thu, 13 Jul 2017 17:17:55 +0100 [thread overview]
Message-ID: <CAKv+Gu9HA1JFY+3Pn5SbjjpMQg7FytbL06oO3sG7pO1VpsNUZw@mail.gmail.com> (raw)
In-Reply-To: <HE1PR0802MB229990751B0C6A7C2EB9F91F9AAC0@HE1PR0802MB2299.eurprd08.prod.outlook.com>
On 13 July 2017 at 17:15, Alexei Fedorov <Alexei.Fedorov@arm.com> wrote:
> Hi,
>
> I've tried the patch & it turns out that options provided with
>
> DEFINE GCC_AARCH64_CC_XIPFLAGS = -mstrict-align -mgeneral-regs-only
>
> aren't picked when building library code with SIMD load/store instructions
> still being generated.
>
> Please see the attached assembly generated file for
> edk2\MdePkg\Library\UefiLib\UefiLibPrint.c.
>
What is wrong with SIMD registers being used in UefiLibPrint? The
report was about code that runs with the MMU off, right?
next prev parent reply other threads:[~2017-07-13 16:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-13 12:48 [PATCH 1/2] BaseTools/tools_def AARCH64: mark register x18 as reserved Ard Biesheuvel
2017-07-13 12:48 ` [PATCH 2/2] BaseTools/tools_def AARCH64: avoid SIMD register in XIP code Ard Biesheuvel
2017-07-13 14:11 ` Leif Lindholm
2017-07-13 16:15 ` Alexei Fedorov
2017-07-13 16:17 ` Ard Biesheuvel [this message]
[not found] ` <HE1PR0802MB2299B668C33778EC20CE6DDA9AAC0@HE1PR0802MB2299.eurprd08.prod.outlook.com>
2017-07-13 17:00 ` Ard Biesheuvel
2017-07-13 17:06 ` Alexei Fedorov
2017-07-13 17:31 ` Leif Lindholm
2017-07-13 20:09 ` Laszlo Ersek
2017-07-13 14:11 ` [PATCH 1/2] BaseTools/tools_def AARCH64: mark register x18 as reserved Leif Lindholm
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-list 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=CAKv+Gu9HA1JFY+3Pn5SbjjpMQg7FytbL06oO3sG7pO1VpsNUZw@mail.gmail.com \
--to=devel@edk2.groups.io \
/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