From: Benjamin Peterson <benjamin@python.org>
To: Rich Felker <dalias@aerifal.cx>
Cc: musl@lists.openwall.com
Subject: Re: [PATCH] always reset DST rules during tzset
Date: Sat, 15 Sep 2018 13:20:12 -0400 (EDT) [thread overview]
Message-ID: <20180915172013.1237B102D7@mailuser.nyi.internal> (raw)
In-Reply-To: <20180915011634.GP1878@brightrain.aerifal.cx>
> This looks right, but is there a reason you swapped the for loop out
> for memsets?
I thought it might generate better code due to store merging. But I definitely
forgot about -ffreestanding.
My latest patch switches back to the loop.
prev parent reply other threads:[~2018-09-15 17:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-14 22:46 Benjamin Peterson
2018-09-15 1:16 ` Rich Felker
[not found] ` <20180915170524.18964-1-benjamin@python.org>
2018-09-15 17:05 ` [PATCH v2] " Benjamin Peterson
2018-09-15 17:20 ` Benjamin Peterson [this message]
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=20180915172013.1237B102D7@mailuser.nyi.internal \
--to=benjamin@python.org \
--cc=dalias@aerifal.cx \
--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).