public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Gary Zibrat" <gzibrat@google.com>
To: Andrew Fish <afish@apple.com>
Cc: devel@edk2.groups.io
Subject: Re: [edk2-devel] Why is specified -mno-sse on clang x64?
Date: Thu, 4 Apr 2019 13:09:29 -0700	[thread overview]
Message-ID: <CAHymY8K2=pgcU3umo2ZNEsTjZzAbMp6ddfvq0uFY3qb7AZv0Qg@mail.gmail.com> (raw)
In-Reply-To: <2A7A0205-FADC-4E8F-B744-E0B5C476A2C6@apple.com>

[-- Attachment #1: Type: text/plain, Size: 1136 bytes --]

It seems like the "-mno-mmx -msoft-float -mno-implicit-float" part of the
flags should be enough to handle that now.
Is it ok to take -mno-sse out (in my local branch) for new versions of
clang without having to worry about silent failures?
Since EFIAPI uses the windows ABI, it should be ok to use XMM registers for
integer operations.

On Thu, Apr 4, 2019 at 1:00 PM Andrew Fish <afish@apple.com> wrote:

> Gary,
>
> The edk2 is freestanding UEFI firmware and the runtime does not support
> floating point exceptions.
>
> I think a long time ago there was an optimization bug and the -mno-sse
> fixed it.
>
> The UEFI x64 ABI is Windows like and not Sys V like.
>
> Thanks,
>
> Andrew Fish
>
> On Apr 4, 2019, at 10:13 AM, Gary Zibrat via Groups.Io <
> gzibrat=google.com@groups.io> wrote:
>
> Does anyone know why -mno-sse is specified on Clang x64?
>
> https://github.com/tianocore/edk2/commit/6f756db5ea057ff10dd168c7627163cec046a3d9
> There doesn't seem to be a corresponding flag for other compilers.
>
> I ask because a commit in LLVM breaks compilation of EDK2:
> https://reviews.llvm.org/rL357317#change-QSW9B7DqCGUI
> 
>
>
>

[-- Attachment #2: Type: text/html, Size: 2099 bytes --]

  reply	other threads:[~2019-04-04 20:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-04 17:13 Why is specified -mno-sse on clang x64? Gary Zibrat
2019-04-04 20:00 ` [edk2-devel] " Andrew Fish
2019-04-04 20:09   ` Gary Zibrat [this message]
2019-04-04 20:12     ` Andrew Fish
2019-04-08 21:12       ` Gary Zibrat

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='CAHymY8K2=pgcU3umo2ZNEsTjZzAbMp6ddfvq0uFY3qb7AZv0Qg@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