public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Danny Smith <dannysmith@clear.net.nz> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: ada/9911: gnatmake fails to link when GCC configured with --with-sjlj-exceptions=yes Date: Mon, 03 Mar 2003 03:16:00 -0000 [thread overview] Message-ID: <20030303031600.10318.qmail@sources.redhat.com> (raw) The following reply was made to PR ada/9911; it has been noted by GNATS. From: Danny Smith <dannysmith@clear.net.nz> To: gcc-gnats@gcc.gnu.org, hainque@gnat.com, gcc-bugs@gcc.gnu.org, dave.anglin@nrc.ca, nobody@gcc.gnu.org, gcc-prs@gcc.gnu.org Cc: Subject: Re: ada/9911: gnatmake fails to link when GCC configured with --with-sjlj-exceptions=yes Date: Mon, 03 Mar 2003 03:12:36 +0000 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=g cc&pr=9911 This patch (against 3.3 branch) fixes. 2003-03-03 Danny Smith <dannysmith@users.sourceforge.net> * raise.c (_Unwind_RaiseException): New function to wrap _Unwind_SjLj_RaiseException for sjlj eh model. Index: raise.c =================================================================== RCS file: /cvs/gcc/gcc/gcc/ada/raise.c,v retrieving revision 1.5 diff -c -3 -p -r1.5 raise.c *** raise.c 23 Oct 2002 07:33:28 -0000 1.5 --- raise.c 3 Mar 2003 03:02:55 -0000 *************** __gnat_eh_personality (version, actions, *** 596,601 **** --- 596,611 ---- return _URC_INSTALL_CONTEXT; } + /* If __USING_SJLJ_EXCEPTIONS__ _Unwind_SjLj_RaiseException is exported + from libgcc.a */ + #ifdef __USING_SJLJ_EXCEPTIONS__ + _Unwind_Reason_Code + _Unwind_RaiseException (e) + struct _Unwind_Exception *e; + { + return _Unwind_SjLj_RaiseException (e); + } + #endif #else /* IN_RTS - For eh personality routine */
next reply other threads:[~2003-03-03 3:16 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-03-03 3:16 Danny Smith [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-03-04 20:21 bosch 2003-03-03 1:46 dave.anglin
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=20030303031600.10318.qmail@sources.redhat.com \ --to=dannysmith@clear.net.nz \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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: linkBe 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).