From: DJ Delorie <dj@redhat.com>
To: Wilco Dijkstra <Wilco.Dijkstra@arm.com>
Cc: Szabolcs.Nagy@arm.com, libc-alpha@sourceware.org
Subject: Re: [PATCH 06/16] malloc: Ensure the generic mtag hooks are not used
Date: Fri, 05 Mar 2021 13:15:07 -0500 [thread overview]
Message-ID: <xnv9a5tql0.fsf@rhel8.vm> (raw)
In-Reply-To: <VE1PR08MB559919F209E1DEF9EE16D3E783969@VE1PR08MB5599.eurprd08.prod.outlook.com> (message from Wilco Dijkstra on Fri, 5 Mar 2021 15:16:40 +0000)
Wilco Dijkstra <Wilco.Dijkstra@arm.com> writes:
> No this works fine. -O0 optimizes if (0) like you'd expect. You do need a bit
> of hacking to do it, I tried:
Did you try it on the oldest version of gcc that glibc still supports?
next prev parent reply other threads:[~2021-03-05 18:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-05 15:16 Wilco Dijkstra
2021-03-05 18:15 ` DJ Delorie [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-03-05 19:01 Wilco Dijkstra
2021-03-04 16:30 [PATCH 00/16] memory tagging improvements Szabolcs Nagy
2021-03-04 16:31 ` [PATCH 06/16] malloc: Ensure the generic mtag hooks are not used Szabolcs Nagy
2021-03-05 1:05 ` DJ Delorie
2021-03-05 12:44 ` Szabolcs Nagy
2021-03-05 20:30 ` DJ Delorie
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=xnv9a5tql0.fsf@rhel8.vm \
--to=dj@redhat.com \
--cc=Szabolcs.Nagy@arm.com \
--cc=Wilco.Dijkstra@arm.com \
--cc=libc-alpha@sourceware.org \
/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 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).