From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jun 2021, #02; Sun, 6)
Date: Wed, 09 Jun 2021 12:06:08 +0200 [thread overview]
Message-ID: <87fsxr2vwd.fsf@evledraar.gmail.com> (raw)
In-Reply-To: <YMCMixVw+2G59yQH@coredump.intra.peff.net>
On Wed, Jun 09 2021, Jeff King wrote:
> On Mon, Jun 07, 2021 at 04:10:17PM +0200, Ævar Arnfjörð Bjarmason wrote:
>
>> > * ab/trace2-squelch-gcc-warning (2021-05-21) 1 commit
>> > (merged to 'next' on 2021-05-28 at 6c7a015f99)
>> > + trace2: refactor to avoid gcc warning under -O3
>> >
>> > Workaround compiler warnings.
>> >
>> > Will cook in 'next'.
>>
>> Thanks.
>
> BTW, Ævar, are you planning to fix other -O3 problems? I happened to
> notice some today. One is new in pu (and I sent a message in that
> thread), but two are older. See this message from last year:
>
> https://lore.kernel.org/git/20200404142131.GA679473@coredump.intra.peff.net/
>
> (amusingly, it also mentions your trace2 one!). I'm happy to send
> patches, but I hadn't written them yet, and it occurred to me you might
> already have done so.
There hasn't been much of anything new in pu for a while :)
But no, please beat me to it. That trace2 one was a one-off I was
tackling because I ran into it when compiling revisions under -O3 with
t/perf/.
next prev parent reply other threads:[~2021-06-09 10:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-06 12:40 What's cooking in git.git (Jun 2021, #02; Sun, 6) Junio C Hamano
2021-06-07 14:10 ` Ævar Arnfjörð Bjarmason
2021-06-09 9:40 ` Jeff King
2021-06-09 10:06 ` Ævar Arnfjörð Bjarmason [this message]
2021-06-10 10:47 ` Jeff King
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=87fsxr2vwd.fsf@evledraar.gmail.com \
--to=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.