public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/39252] Request new feature __builtin_not_reached();
Date: Fri, 20 Feb 2009 09:57:00 -0000 [thread overview]
Message-ID: <20090220095715.1240.qmail@sourceware.org> (raw)
In-Reply-To: <bug-39252-3556@http.gcc.gnu.org/bugzilla/>
------- Comment #8 from rguenth at gcc dot gnu dot org 2009-02-20 09:57 -------
Though __builtin_not_reached () can be used to implement __builtin_assume (),
so it may be more generally useful. if (i > 0) __builtin_not_reached (); will
make GCC assume that i <= 0 on the other edge (of course we'd have to preserve
this until some point to take advantage of it).
--
rguenth at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Ever Confirmed|0 |1
Last reconfirmed|0000-00-00 00:00:00 |2009-02-20 09:57:15
date| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39252
next prev parent reply other threads:[~2009-02-20 9:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-19 20:42 [Bug c/39252] New: " hpa at zytor dot com
2009-02-19 20:46 ` [Bug c/39252] " hjl dot tools at gmail dot com
2009-02-19 20:51 ` hjl dot tools at gmail dot com
2009-02-19 21:50 ` pinskia at gcc dot gnu dot org
2009-02-19 21:58 ` hpa at zytor dot com
2009-02-19 22:13 ` hpa at zytor dot com
2009-02-19 22:14 ` pinskia at gcc dot gnu dot org
2009-02-19 22:21 ` hpa at zytor dot com
2009-02-19 23:02 ` jakub at gcc dot gnu dot org
2009-02-20 4:34 ` hpa at zytor dot com
2009-02-20 9:57 ` rguenth at gcc dot gnu dot org [this message]
2009-03-01 22:34 ` hpa at zytor dot com
2009-03-01 22:42 ` rguenth at gcc dot gnu dot org
2009-06-09 20:12 ` daney at gcc dot gnu dot org
2009-06-09 20:16 ` daney at gcc dot gnu dot org
2009-06-11 23:56 ` [Bug c/39252] Request new feature __builtin_unreachable () daney at gcc dot gnu dot org
2009-06-12 0:29 ` daney at gcc dot gnu dot 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=20090220095715.1240.qmail@sourceware.org \
--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).