From: Joseph Myers <joseph@codesourcery.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Richard Biener <rguenther@suse.de>, <gcc-patches@gcc.gnu.org>,
Florian Weimer <fweimer@redhat.com>
Subject: Re: [PATCH] c-family, middle-end: Add __builtin_c[lt]zg (arg, 0ULL) exception
Date: Tue, 21 Nov 2023 00:12:18 +0000 [thread overview]
Message-ID: <f2b14cb8-5de3-651e-887a-33b78ba7a87@codesourcery.com> (raw)
In-Reply-To: <ZVsWoMqMJq2tZ8Mg@tucnak>
On Mon, 20 Nov 2023, Jakub Jelinek wrote:
> and be done with that. If there is an agreement we should do that
> for all 14 rather than just those 3 + the 2 ugly hacks (__builtin_c{l,t}zg with
> 0ULL second argument and __builtin_bit_complement), I can change the
I tend to agree with the "ugly hack" description of the 0ULL second
argument special case. __builtin_bit_complement seems reasonable enough
as a primitive for implementing such operations, but so does just defining
built-in functions in the front end for all 14 (or for all 14 except those
that are trivial wrappers round existing built-in functions without
needing to use ({}) or expand argument tokens more than once).
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2023-11-21 0:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-18 19:30 Jakub Jelinek
2023-11-20 7:44 ` Richard Biener
2023-11-20 7:49 ` Richard Biener
2023-11-20 8:19 ` Jakub Jelinek
2023-11-21 0:12 ` Joseph Myers [this message]
2023-11-21 8:30 ` Jakub Jelinek
2023-11-20 8:13 ` Jakub Jelinek
2023-11-20 8:18 ` Florian Weimer
2023-11-20 8:31 ` Jakub Jelinek
2023-11-20 8:37 ` Richard Biener
2023-11-20 8:48 ` Jakub Jelinek
2023-11-20 8:58 ` Richard Biener
2023-11-21 5:59 ` Martin Uecker
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=f2b14cb8-5de3-651e-887a-33b78ba7a87@codesourcery.com \
--to=joseph@codesourcery.com \
--cc=fweimer@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=rguenther@suse.de \
/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).