From: Jonathan Wakely <jwakely@redhat.com>
To: sotrdg sotrdg <euloanty@live.com>
Cc: "unlvsur unlvsur via Libstdc++" <libstdc++@gcc.gnu.org>
Subject: Re: [PATCH] print extended assertion failures to stderr
Date: Thu, 4 Nov 2021 13:54:18 +0000 [thread overview]
Message-ID: <CACb0b4me=vaKF9c3xQ8P+G4-_t+1fUOa4jb4kNyK1pwngDQspA@mail.gmail.com> (raw)
In-Reply-To: <CH2PR02MB652243AC0DEAEA7FB99610E1B28D9@CH2PR02MB6522.namprd02.prod.outlook.com>
On Thu, 4 Nov 2021 at 13:53, sotrdg sotrdg via Libstdc++ <
libstdc++@gcc.gnu.org> wrote:
> I think We better put entire function
>
> __replacement_assert
>
> into other translation unit Instead of putting stderr?
>
Why?
next prev parent reply other threads:[~2021-11-04 13:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-04 13:53 sotrdg sotrdg
2021-11-04 13:54 ` Jonathan Wakely [this message]
[not found] ` <CH2PR02MB65229EA7D6AA4BCC9515F087B28D9@CH2PR02MB6522.namprd02.prod.outlook.com>
[not found] ` <CACb0b4m7oddSaVMqDG61gDQ_++pC4nrJYRpPE3U6E+QRbyVNQA@mail.gmail.com>
2021-11-04 14:17 ` sotrdg sotrdg
2021-11-04 15:13 ` Jonathan Wakely
-- strict thread matches above, loose matches on Subject: below --
2021-10-27 8:25 Jay Feldblum
2021-11-04 11:30 ` Jonathan Wakely
2021-11-04 23:44 ` Jonathan Wakely
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='CACb0b4me=vaKF9c3xQ8P+G4-_t+1fUOa4jb4kNyK1pwngDQspA@mail.gmail.com' \
--to=jwakely@redhat.com \
--cc=euloanty@live.com \
--cc=libstdc++@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).