public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/114779] __builtin_constant_p does not work in inline functions
Date: Fri, 19 Apr 2024 08:42:41 +0000	[thread overview]
Message-ID: <bug-114779-4-JtVyxE5Cir@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114779-4@http.gcc.gnu.org/bugzilla/>

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jakub at gcc dot gnu.org

--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
That has nothing to do with inline functions and everything to do with pointer
arguments to __builtin_constant_p.  The builtin behaved that way since at least
1998.
The current version still has
  /* If this expression has side effects, show we don't know it to be a
     constant.  Likewise if it's a pointer or aggregate type since in
     those case we only want literals, since those are only optimized
     when generating RTL, not later.
     And finally, if we are compiling an initializer, not code, we
     need to return a definite result now; there's not going to be any
     more optimization done.  */
  if (TREE_SIDE_EFFECTS (arg)
      || AGGREGATE_TYPE_P (TREE_TYPE (arg))
      || POINTER_TYPE_P (TREE_TYPE (arg))
      || cfun == 0
      || folding_initializer
      || force_folding_builtin_constant_p)
    return integer_zero_node;
What triggers here is the POINTER_TYPE_P (TREE_TYPE (arg)) case.  So, the
builtin is immediately folded into 0 in that case.

  reply	other threads:[~2024-04-19  8:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-19  8:28 [Bug tree-optimization/114779] New: " gjl at gcc dot gnu.org
2024-04-19  8:42 ` jakub at gcc dot gnu.org [this message]
2024-04-19  8:44 ` [Bug tree-optimization/114779] " gjl at gcc dot gnu.org
2024-04-19  8:49 ` jakub at gcc dot gnu.org
2024-04-19  8:55 ` gjl at gcc dot gnu.org
2024-04-19  9:03 ` jakub at gcc dot gnu.org
2024-04-19  9:20 ` gjl at gcc dot gnu.org
2024-04-19  9:38 ` hubicka at gcc dot gnu.org
2024-04-19 10:10 ` rguenth at gcc dot gnu.org
2024-04-19 10:43 ` gjl at gcc dot gnu.org
2024-04-19 11:36 ` gjl 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-114779-4-JtVyxE5Cir@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).