public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Richard Biener <rguenther@suse.de>
Cc: Jakub Jelinek <jakub@redhat.com>,
	 "Joseph S. Myers" <joseph@codesourcery.com>,
	 gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] c-family, middle-end: Add __builtin_c[lt]zg (arg, 0ULL) exception
Date: Mon, 20 Nov 2023 09:18:57 +0100	[thread overview]
Message-ID: <87zfz8rg5q.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <nycvar.YFH.7.77.849.2311200741000.8772@jbgna.fhfr.qr> (Richard Biener's message of "Mon, 20 Nov 2023 07:44:18 +0000 (UTC)")

* Richard Biener:

> Ugh.  First of all I don't like that the exception is applied during
> folding.  As for the problem of multi evaluation can't consumers use
> stmt expressions for this, say
>
> {( auto __tem = value; __builtin_xyz (__tem, __typeof (__tem)); ... )}
>
> ?  Thus use 'auto' to avoid spelling 'value' multiple times?

{( … )} cannot be used in a constant expression, but the new macros are
supposed to be usable there.

Thanks,
Florian


  parent reply	other threads:[~2023-11-20  8:19 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
2023-11-21  8:30         ` Jakub Jelinek
2023-11-20  8:13   ` Jakub Jelinek
2023-11-20  8:18   ` Florian Weimer [this message]
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=87zfz8rg5q.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=joseph@codesourcery.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).