public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aldyh at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/106654] [C++23] P1774 - Portable assumptions
Date: Sat, 17 Sep 2022 11:34:10 +0000	[thread overview]
Message-ID: <bug-106654-4-bdmvgqe333@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106654-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 from Aldy Hernandez <aldyh at gcc dot gnu.org> ---
You could provide an API to access the different relations that hold in either
the outline function, or the .IFN_ASSUME construct.  Then ranger could use that
API to access and record the different assertions.  I'd hate for ranger to have
to deconstruct some functions for clues.

Silly question, why can't you expand the [[assume]] construct into:

if (x > 5)
  __builtin_unreachable ();

...like we always have.  Then no changes are needed to ranger :).  Or does this
have to do with the whole side-effect thing?

  parent reply	other threads:[~2022-09-17 11:34 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-16 17:20 [Bug c++/106654] New: " mpolacek at gcc dot gnu.org
2022-09-14  9:52 ` [Bug c++/106654] " jakub at gcc dot gnu.org
2022-09-14 11:23 ` rguenth at gcc dot gnu.org
2022-09-14 11:26 ` rguenth at gcc dot gnu.org
2022-09-14 11:54 ` jakub at gcc dot gnu.org
2022-09-16  9:20 ` pilarlatiesa at gmail dot com
2022-09-16 16:48 ` jakub at gcc dot gnu.org
2022-09-17 11:34 ` aldyh at gcc dot gnu.org [this message]
2022-09-17 12:09 ` jason at gcc dot gnu.org
2022-09-17 12:12 ` aldyh at gcc dot gnu.org
2022-09-17 12:29 ` jason at gcc dot gnu.org
2022-09-17 18:32 ` aldyh at gcc dot gnu.org
2022-09-21 17:49 ` jakub at gcc dot gnu.org
2022-10-06  7:01 ` cvs-commit at gcc dot gnu.org
2022-10-07 14:20 ` jakub at gcc dot gnu.org
2022-10-08 10:45 ` jakub at gcc dot gnu.org
2022-10-18  8:40 ` cvs-commit at gcc dot gnu.org
2022-10-20  0:37 ` cvs-commit at gcc dot gnu.org
2022-10-20 19:43 ` cvs-commit at gcc dot gnu.org
2022-11-19  9:24 ` jakub at gcc dot gnu.org
2022-11-28 22:32 ` 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-106654-4-bdmvgqe333@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).