From: Jakub Jelinek <jakub@redhat.com>
To: Sebastian Huber <sebastian.huber@embedded-brains.de>
Cc: GCC Development <gcc@gcc.gnu.org>
Subject: Re: _Unwind_Resume() references in libgcc division functions
Date: Tue, 21 Jun 2022 15:24:16 +0200 [thread overview]
Message-ID: <YrHGgJluozl/eS8H@tucnak> (raw)
In-Reply-To: <0da8d95f-7102-4324-2737-82ff3c4b7e27@embedded-brains.de>
On Tue, Jun 21, 2022 at 03:13:19PM +0200, Sebastian Huber wrote:
> Hello,
>
> I noticed that several division related routines provided by libgcc such as
> __divdi3, __moddi3 and __umoddi3 have references to _Unwind_Resume for the
> sparc-rtems target. For example:
That is because:
ifeq ($(LIB2_DIVMOD_EXCEPTION_FLAGS),)
# Provide default flags for compiling divmod functions, if they haven't been
# set already by a target-specific Makefile fragment.
LIB2_DIVMOD_EXCEPTION_FLAGS := -fexceptions -fnon-call-exceptions
endif
which is there so that e.g. Ada or other -fnon-call-exceptions languages can
have properly working divisions.
Jakub
next prev parent reply other threads:[~2022-06-21 13:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-21 13:13 Sebastian Huber
2022-06-21 13:24 ` Jakub Jelinek [this message]
2022-06-21 13:44 ` Sebastian Huber
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=YrHGgJluozl/eS8H@tucnak \
--to=jakub@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=sebastian.huber@embedded-brains.de \
/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).