public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/98861] I want deterministic exceptions (Herbception)
Date: Thu, 28 Jan 2021 17:56:57 +0000	[thread overview]
Message-ID: <bug-98861-4-Iqevjq6vO5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98861-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #15 from Jonathan Wakely <redi at gcc dot gnu.org> ---
> > (In reply to cqwrteur from comment #12)
> > > stdio.h should not get included in any circumstances for EH. You are
> > > implementing the operating system, but you need to enable EH by the standard
> > > and EH relies on stdio. Chicken-egg problem.
> > 
> > It doesn't depend on stdio though. What are you talking about?
> 
> https://github.com/gcc-mirror/gcc/blob/
> e11e5d3889f9e54c547efee50fa1b72b50f0f265/libstdc%2B%2B-v3/libsupc%2B%2B/
> vterminate.cc#L93

Which is disabled in freestanding, and can be optionally disabled in hosted.

This is an OPTIONAL feature of libstdc++, not something that exception handling
intrinsically relies on. If you don't want it, you don't have to use it.

And if you're implementing the OS then you're using freestanding and it's
automatically disabled. Looks at line 27 in that file.

Once again you are talking out of your backside.

Stop wasting our time.

  parent reply	other threads:[~2021-01-28 17:56 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-28  0:46 [Bug c++/98861] New: " unlvsur at live dot com
2021-01-28  7:42 ` [Bug c++/98861] " rguenth at gcc dot gnu.org
2021-01-28  9:56 ` redi at gcc dot gnu.org
2021-01-28 10:00 ` unlvsur at live dot com
2021-01-28 10:03 ` unlvsur at live dot com
2021-01-28 10:08 ` unlvsur at live dot com
2021-01-28 10:17 ` unlvsur at live dot com
2021-01-28 15:50 ` mpolacek at gcc dot gnu.org
2021-01-28 15:50 ` unlvsur at live dot com
2021-01-28 15:51 ` unlvsur at live dot com
2021-01-28 16:01 ` mpolacek at gcc dot gnu.org
2021-01-28 17:24 ` redi at gcc dot gnu.org
2021-01-28 17:31 ` unlvsur at live dot com
2021-01-28 17:33 ` unlvsur at live dot com
2021-01-28 17:43 ` redi at gcc dot gnu.org
2021-01-28 17:48 ` unlvsur at live dot com
2021-01-28 17:56 ` redi at gcc dot gnu.org [this message]
2021-01-28 17:58 ` unlvsur at live dot com
2021-01-28 18:00 ` unlvsur at live dot com
2021-01-28 18:02 ` redi at gcc dot gnu.org
2021-01-28 18:03 ` redi at gcc dot gnu.org
2021-01-28 18:11 ` unlvsur at live dot com
2021-01-28 18:19 ` redi at gcc dot gnu.org
2021-01-28 18:21 ` redi at gcc dot gnu.org
2021-01-28 18:24 ` jakub at gcc dot gnu.org
2021-01-28 18:31 ` unlvsur at live dot com
2021-01-28 18:32 ` unlvsur at live dot com
2021-01-28 18:39 ` redi at gcc dot gnu.org
2021-01-28 18:47 ` unlvsur at live dot com
2021-01-28 18:49 ` unlvsur at live dot com
2021-01-28 20:04 ` unlvsur at live dot com
2021-01-28 20:25 ` unlvsur at live dot com
2021-01-29 21:56 ` unlvsur at live dot com
2021-01-29 21:58 ` mpolacek 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-98861-4-Iqevjq6vO5@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).