public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "unlvsur at live dot com" <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 18:11:53 +0000 [thread overview]
Message-ID: <bug-98861-4-5x6e8zs3G4@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 #20 from cqwrteur <unlvsur at live dot com> ---
(In reply to Jonathan Wakely from comment #19)
> (In reply to cqwrteur from comment #16)
> > That does not work in the real-world since your libstdc++'s freestanding
> > header never works correctly, (you get compilation errors).
>
> Try reporting a bug about *that* next time (except don't, I don't want any
> more stupidity from you).
Let me be more clear.
1. Freestanding C++ in the current situation is very problematic. (You do not
have memcpy, you do not have std::move. You do not have std::forward. You do
not have std::addressof(). you do not have std::array.) However, you have an
exception handling support.
2. What's the point of reporting a bug when building libstdc++ with GNU newlib
just works much better and you have an entire hosted toolchain that will not
break compilation? The only problem is that you never enable EH.
I did report bugs before. However, it was not fixed. I am not going to try it
again tbh since newlib works just fine.
http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2018/p1105r0.html
Bare metal gcc 4.8 with newlib
undefined reference to "__exidx_end"
undefined reference to "__exidx_start"
undefined reference to "_exit"
undefined reference to "_sbrk"
undefined reference to "_kill"
undefined reference to "_getpid"
undefined reference to "_write"
undefined reference to "_close"
undefined reference to "_fstat"
undefined reference to "_isatty"
undefined reference to "_lseek"
undefined reference to "_read"
next prev parent reply other threads:[~2021-01-28 18:11 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
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 [this message]
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-5x6e8zs3G4@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).