public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ralphengels at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/106908] libsupc++ wrong declaration of __unexpected_handler
Date: Mon, 12 Sep 2022 14:39:21 +0000	[thread overview]
Message-ID: <bug-106908-4-QD1cq08uCh@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106908-4@http.gcc.gnu.org/bugzilla/>

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.

      parent reply	other threads:[~2022-09-12 14:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-12 12:21 [Bug libstdc++/106908] New: " 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 message]

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-106908-4-QD1cq08uCh@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).