public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/52708] suboptimal code with __builtin_constant_p
Date: Mon, 26 Mar 2012 08:23:00 -0000 [thread overview]
Message-ID: <bug-52708-4-XH2lCP9jdW@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52708-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52708
Richard Guenther <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2012-03-26
Ever Confirmed|0 |1
--- Comment #2 from Richard Guenther <rguenth at gcc dot gnu.org> 2012-03-26 08:17:39 UTC ---
Hm. We delay evaluating __builtin_constant_p to make it possible for inlining
to lead to simplifications that result in a constant. We could of course
evaluate early if there are any side-effects in its argument, but that would
change outcome in existing code bases.
What do you think specifies the behavior you are expecting? Nothing
explicitely
says that the argument is not evaluated or that its side-effects are discarded.
next prev parent reply other threads:[~2012-03-26 8:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-25 15:38 [Bug c/52708] New: " tijl at coosemans dot org
2012-03-25 20:49 ` [Bug c/52708] " tijl at coosemans dot org
2012-03-26 8:23 ` rguenth at gcc dot gnu.org [this message]
2012-03-27 11:42 ` tijl at coosemans dot org
2013-11-10 19:48 ` pinskia at gcc dot gnu.org
2021-07-25 2:15 ` [Bug tree-optimization/52708] " pinskia at gcc dot gnu.org
2023-09-02 18:25 ` pinskia 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-52708-4-XH2lCP9jdW@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).