This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/78677] __gthread_key_create assumed not to fail in eh_globals.cc
- From: "redi at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Mon, 05 Dec 2016 10:29:25 +0000
- Subject: [Bug libstdc++/78677] __gthread_key_create assumed not to fail in eh_globals.cc
- Auto-submitted: auto-generated
- References: <bug-78677-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78677
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2016-12-05
Ever confirmed|0 |1
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Chris Johns from comment #0)
> Some operating system, for example RTEMS, may fail to create a POSIX key if
> not configured with enough resources. The lack of any error reporting in
> __eh_globals_init::__eh_globals_init() means exceptions are silently
> switched from thread safe to not being thread safe and this is not a concern
> for RTEMS.
I assume this is a typo and you mean this *is* a concern for RTEMS? :-)
> A way to report errors would be welcomed by RTEMS. We could hook this is a
> fatal error so the user is aware there is a critical issue that needs to be
> addressed.
I agree there should be some code to deal with the error there.
This seems like a specific example of the broader problem you described in PR
60645.