From: Mark H Weaver <mhw@netris.org>
To: Leo Famulari <leo@famulari.name>,
Liliana Marie Prikler <liliana.prikler@ist.tugraz.at>
Cc: 51591@debbugs.gnu.org
Subject: bug#51591: webkitgtk fails to build on i686-linux; possibly a clang issue
Date: Fri, 05 Nov 2021 15:16:02 -0400 [thread overview]
Message-ID: <87bl2yv2eq.fsf@netris.org> (raw)
In-Reply-To: <YYVazYsMPEGN59+8@jasmine.lan>
Leo Famulari <leo@famulari.name> writes:
> On Fri, Nov 05, 2021 at 09:08:05AM +0100, Liliana Marie Prikler wrote:
>> I did some static code analysis and it seems we could comment out the
>> line
>> CHECK_FOR_SSE2()
>> in Source/cmake/DetectSSE2.cmake. In my personal opinion, we should
>> probably do so on all platforms.
>
> Do we not use SSE2 on x86_64?
SSE2 is guaranteed feature of the AMD64 (a.k.a. x86_64) architecture,
and it's a big help to use it, even where SIMD vector operations are not
needed. It would be a bad idea to disable it outright.
I think we should hold out for a better solution than simply disabling
SSE2 support on all systems.
Thanks,
Mark
--
Disinformation flourishes because many people care deeply about injustice
but very few check the facts. Ask me about <https://stallmansupport.org>.
next prev parent reply other threads:[~2021-11-05 19:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-03 18:25 bug#51591: webkitgtk fails to build on i686-linux; possibly a clang issue Mark H Weaver
2021-11-03 21:04 ` Mark H Weaver
2021-11-04 8:03 ` Liliana Marie Prikler
2021-11-04 23:15 ` Mark H Weaver
2021-11-05 8:08 ` Liliana Marie Prikler
2021-11-05 16:24 ` Leo Famulari
2021-11-05 19:16 ` Mark H Weaver [this message]
2021-11-05 19:42 ` Mark H Weaver
2021-11-05 20:11 ` Maxime Devos
2021-11-06 6:09 ` Mark H Weaver
2021-11-07 5:46 ` Mark H Weaver
2021-11-06 7:34 ` Mark H Weaver
2021-11-05 2:38 ` Maxim Cournoyer
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bl2yv2eq.fsf@netris.org \
--to=mhw@netris.org \
--cc=51591@debbugs.gnu.org \
--cc=leo@famulari.name \
--cc=liliana.prikler@ist.tugraz.at \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).