From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: [musl] riscv32 v2
Date: Mon, 7 Sep 2020 14:09:02 -0400 [thread overview]
Message-ID: <20200907180902.GN3265@brightrain.aerifal.cx> (raw)
In-Reply-To: <e404278c-d143-467b-bf68-e3eb8953fff9@www.fastmail.com>
On Mon, Sep 07, 2020 at 07:27:37AM -0400, Stefan O'Rear wrote:
> On Fri, Sep 4, 2020, at 1:48 AM, Stefan O'Rear wrote:
> > Rich Felker's suggestion (on IRC) to use a 0-instruction __get_tp was
> > NOT implemented after discovering that it generates dramatically worse
> > code on clang and cannot easily be conditionalized. Bug reports to come.
>
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96952
> https://bugs.llvm.org/show_bug.cgi?id=47447
Thanks! I think the GCC issue & response to it supports my preference
not to use GCC __builtin_*, but I would like to see them fix it. The
form with __asm__("" : ...) is semantically correct and has always
worked, but I don't see enough benefit over the current non-empty asm
to justify accepting the worse codegen from llvm getting it wrong.
Maybe we can change it at some point in the future after llvm is
fixed, but it's really no big deal.
Rich
next prev parent reply other threads:[~2020-09-07 18:09 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-04 5:48 Stefan O'Rear
2020-09-07 10:47 ` Stefan O'Rear
2020-09-07 18:06 ` Rich Felker
2020-09-07 21:35 ` Arnd Bergmann
2020-09-07 21:45 ` Rich Felker
2020-09-07 21:58 ` Arnd Bergmann
2020-09-07 22:11 ` Rich Felker
2020-09-07 22:30 ` Arnd Bergmann
2020-09-08 1:02 ` Rich Felker
2020-09-08 7:00 ` Arnd Bergmann
2020-09-07 11:27 ` Stefan O'Rear
2020-09-07 18:09 ` Rich Felker [this message]
2020-09-08 1:54 ` Rich Felker
2020-09-09 6:07 ` Rich Felker
2020-09-09 20:28 ` Rich Felker
2020-09-09 21:28 ` Palmer Dabbelt
2020-09-09 21:36 ` Rich Felker
2020-09-09 23:08 ` Palmer Dabbelt
2020-09-10 7:36 ` Arnd Bergmann
2020-09-10 10:01 ` Vincenzo Frascino
2020-09-11 0:08 ` Palmer Dabbelt
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=20200907180902.GN3265@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).