public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andrew Sutton <asutton@lock3software.com>
To: Jonathan Wakely <jwakely@redhat.com>
Cc: Jason Merrill <jason@redhat.com>,
	gcc Patches <gcc-patches@gcc.gnu.org>,
	 Jeff Chapman <JAChapmanII@gmail.com>
Subject: Re: contracts library support (was Re: [PATCH] PING implement pre-c++20 contracts)
Date: Fri, 16 Jul 2021 09:18:37 -0400	[thread overview]
Message-ID: <CAMJpcpX24C_o0EdsXvMRKdDYhoPn=NZfb6LyQdD4d0nmAWkDpg@mail.gmail.com> (raw)
In-Reply-To: <CACb0b4=5whmLC1FocWMo7FVh_naS9V6nXRM+AAx4RKyBfOwFVQ@mail.gmail.com>

> Is just using std::terminate as the handler viable? Or if we're sure
> contracts in some form will go into the IS eventually, and the
> signature won't change, we could just add it in __cxxabiv1:: as you
> suggested earlier.

No, the handler needs to be configurable (at least quietly) in order
to support experimentation by SG21. No idea if it will stay that way.

Andrew

      reply	other threads:[~2021-07-16 13:19 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-13 19:23 [PATCH] implement pre-c++20 contracts Jeff Chapman
2019-12-10  5:58 ` Jason Merrill
2019-12-10  6:20   ` Jason Merrill
2020-03-24 14:23   ` Andrew Sutton
2020-05-07 15:56   ` Jeff Chapman
2020-07-10 17:53     ` Jeff Chapman
2020-07-28 12:52       ` Jeff Chapman
2020-12-02 20:33       ` Jason Merrill
2020-12-03 17:07         ` Andrew Sutton
2020-12-03 17:41           ` Jason Merrill
2020-12-04 13:35             ` Jeff Chapman
2021-01-04 14:58               ` [PATCH] PING " Jeff Chapman
2021-01-05 21:27                 ` Jason Merrill
2021-01-18 14:56                 ` Jason Merrill
2021-03-01 13:12                   ` Jeff Chapman
2021-03-26  2:53                     ` Jason Merrill
2021-04-30 17:44                       ` Jeff Chapman
2021-05-14 20:54                         ` Jason Merrill
2021-05-14 21:09                           ` Marek Polacek
2021-05-17 22:06                           ` Jason Merrill
2021-05-28 13:18                             ` Jeff Chapman
     [not found]                               ` <CAMJpcpX7zAbHr79sZefXRSn2bxFg+ei9YUzMoapShctq=TwgGQ@mail.gmail.com>
2021-07-01 15:14                                 ` Jason Merrill
2021-07-01 16:27                                   ` Andrew Sutton
2021-07-02 15:09                                     ` Jason Merrill
2021-07-02 15:30                                       ` Andrew Sutton
2021-07-05 19:07                                 ` contracts library support (was Re: [PATCH] PING implement pre-c++20 contracts) Jason Merrill
2021-07-06 20:47                                   ` Jason Merrill
2021-07-12 19:58                                   ` Jonathan Wakely
2021-07-14  3:56                                     ` Jason Merrill
2021-07-14 10:55                                       ` Jonathan Wakely
2021-07-16 13:18                                         ` Andrew Sutton [this message]

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='CAMJpcpX24C_o0EdsXvMRKdDYhoPn=NZfb6LyQdD4d0nmAWkDpg@mail.gmail.com' \
    --to=asutton@lock3software.com \
    --cc=JAChapmanII@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jason@redhat.com \
    --cc=jwakely@redhat.com \
    /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).