public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug libstdc++/106908] New: libsupc++ wrong declaration of __unexpected_handler
@ 2022-09-12 12:21 ralphengels at gmail dot com
  2022-09-12 14:30 ` [Bug libstdc++/106908] " redi at gcc dot gnu.org
  2022-09-12 14:39 ` ralphengels at gmail dot com
  0 siblings, 2 replies; 3+ messages in thread
From: ralphengels at gmail dot com @ 2022-09-12 12:21 UTC (permalink / raw)
  To: gcc-bugs

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

            Bug ID: 106908
           Summary: libsupc++ wrong declaration of __unexpected_handler
           Product: gcc
           Version: 12.2.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libstdc++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: ralphengels at gmail dot com
  Target Milestone: ---

the declaration of __unexpected_handler in unwind-cxx.h is wrongly declared as 
extern std::terminate_handler __unexpected_handler;
should be
extern std::unexpected_handler __unexpected_handler;

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug libstdc++/106908] libsupc++ wrong declaration of __unexpected_handler
  2022-09-12 12:21 [Bug libstdc++/106908] New: libsupc++ wrong declaration of __unexpected_handler ralphengels at gmail dot com
@ 2022-09-12 14:30 ` redi at gcc dot gnu.org
  2022-09-12 14:39 ` ralphengels at gmail dot com
  1 sibling, 0 replies; 3+ messages in thread
From: redi at gcc dot gnu.org @ 2022-09-12 14:30 UTC (permalink / raw)
  To: gcc-bugs

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

Jonathan Wakely <redi at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |INVALID

--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Not a bug, this is intentional.

std::unexpected_handler does not exist in C++17 and later, so using
terminate_handler means the code compiles for any version of C++. The two types
are identical, so it doesn't matter.

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug libstdc++/106908] libsupc++ wrong declaration of __unexpected_handler
  2022-09-12 12:21 [Bug libstdc++/106908] New: libsupc++ wrong declaration of __unexpected_handler ralphengels at gmail dot com
  2022-09-12 14:30 ` [Bug libstdc++/106908] " redi at gcc dot gnu.org
@ 2022-09-12 14:39 ` ralphengels at gmail dot com
  1 sibling, 0 replies; 3+ messages in thread
From: ralphengels at gmail dot com @ 2022-09-12 14:39 UTC (permalink / raw)
  To: gcc-bugs

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

--- Comment #2 from ralphengels at gmail dot com <ralphengels at gmail dot com> ---
ah my bad then i just thought it looked suspicious especially since i been
having problems building gnat. For some reason it tries to link to the static
libgcc library and aborts due to an exception. So i had to change the
GCC_LINKER_FLAGS to force -shared-libgcc. so when i spotted this i assumed a
typo might have occured breaking the exception handlers.

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2022-09-12 14:39 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-09-12 12:21 [Bug libstdc++/106908] New: libsupc++ wrong declaration of __unexpected_handler ralphengels at gmail dot com
2022-09-12 14:30 ` [Bug libstdc++/106908] " redi at gcc dot gnu.org
2022-09-12 14:39 ` ralphengels at gmail dot com

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).