public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/112296] __builtin_constant_p doesn't propagate through member functions
Date: Mon, 06 Nov 2023 07:27:55 +0000	[thread overview]
Message-ID: <bug-112296-4-lijTd2Q42w@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112296-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112296

--- Comment #14 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Richard Biener <rguenth@gcc.gnu.org>:

https://gcc.gnu.org/g:442715708911ed6cc6f3785e3996a62f5ee7f21f

commit r14-5143-g442715708911ed6cc6f3785e3996a62f5ee7f21f
Author: Richard Biener <rguenther@suse.de>
Date:   Fri Nov 3 08:11:05 2023 +0100

    middle-end/112296 - __builtin_constant_p and side-effects

    The following tries to clarify the __builtin_constant_p documentation,
    stating that the argument expression is not evaluated and side-effects
    are discarded.  I'm struggling to find the correct terms matching
    what the C language standard would call things so I'd appreciate
    some help here.

    OK for trunk?

    Shall we diagnose arguments with side-effects?  It seems to me
    such use is usually unintended?  I think rather than dropping
    side-effects as a side-effect of folding the frontend should
    discard them at parsing time instead, no?

    Thanks,
    Richard.

            PR middle-end/112296
            * doc/extend.texi (__builtin_constant_p): Clarify that
            side-effects are discarded.

  parent reply	other threads:[~2023-11-06  7:27 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-30 14:22 [Bug c++/112296] New: " barry.revzin at gmail dot com
2023-10-30 14:26 ` [Bug c++/112296] " rguenth at gcc dot gnu.org
2023-10-30 14:46 ` redi at gcc dot gnu.org
2023-10-30 14:49 ` redi at gcc dot gnu.org
2023-10-31  8:29 ` [Bug tree-optimization/112296] " rguenth at gcc dot gnu.org
2023-10-31  9:29 ` rguenth at gcc dot gnu.org
2023-10-31  9:36 ` rguenth at gcc dot gnu.org
2023-10-31 13:51 ` rth at gcc dot gnu.org
2023-10-31 13:57 ` rguenth at gcc dot gnu.org
2023-10-31 14:05 ` rth at gcc dot gnu.org
2023-10-31 14:13 ` rguenth at gcc dot gnu.org
2023-10-31 14:23 ` rguenth at gcc dot gnu.org
2023-10-31 16:55 ` joseph at codesourcery dot com
2023-11-03  7:11 ` rguenth at gcc dot gnu.org
2023-11-06  7:27 ` cvs-commit at gcc dot gnu.org [this message]
2023-11-06  7:38 ` rguenth at gcc dot gnu.org

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=bug-112296-4-lijTd2Q42w@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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).