From: Luca Barbato <lu_zero@gentoo.org>
To: musl@lists.openwall.com
Subject: Re: Current status: important changes since 0.9.11
Date: Fri, 19 Jul 2013 22:36:53 +0200 [thread overview]
Message-ID: <51E9A365.5090407@gentoo.org> (raw)
In-Reply-To: <20130719202645.GB3249@brightrain.aerifal.cx>
On 07/19/2013 10:26 PM, Rich Felker wrote:
> On Fri, Jul 19, 2013 at 10:19:11PM +0200, Luca Barbato wrote:
>> On 07/19/2013 09:54 PM, Rich Felker wrote:
>>> On Fri, Jul 19, 2013 at 09:49:42PM +0200, Luca Barbato wrote:
>>>> On 07/19/2013 08:53 PM, Rich Felker wrote:
>>>>> However I do also agree with you, and think simplicity/consistency
>>>>> possibly override reason #1 above, and #2 could easily be handled if
>>>>> some time is put into review and testing of the new code.
>>>>>
>>>>> Anyone else have opinions on the matter?
>>>>
>>>> According to what you said pathological compilers would be the problem here.
>>>
>>> Which comment are you referring to?
>>
>> I could be wrong and it wasn't from you. Anyway, I still consider
>> supporting pathological compilers (that botch the usage of inline asm
>> badly) the only reason to use full-asm.
>
> One could always pre-generate the asm using GCC or another compiler
> that can handle it. Actually even if we wanted to keep using per-arch
> hand-written asm, generating the initial draft of the asm for a new
> arch based on the C with inline asm would be a good idea..
Exactly.
> Indeed, this code takes about 1/100 of one percent of the time spent
> on exec... :)
I guess nobody should be against this change.
lu
next prev parent reply other threads:[~2013-07-19 20:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-19 16:12 Rich Felker
2013-07-19 18:39 ` Harald Becker
2013-07-19 18:53 ` Rich Felker
2013-07-19 19:40 ` Harald Becker
2013-07-19 19:49 ` Luca Barbato
2013-07-19 19:54 ` Rich Felker
2013-07-19 20:19 ` Luca Barbato
2013-07-19 20:26 ` Rich Felker
2013-07-19 20:36 ` Luca Barbato [this message]
2013-07-22 4:57 ` idunham
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=51E9A365.5090407@gentoo.org \
--to=lu_zero@gentoo.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).