public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Sebastian Huber <sebastian.huber@embedded-brains.de>
To: Jakub Jelinek <jakub@redhat.com>
Cc: GCC Development <gcc@gcc.gnu.org>
Subject: Re: _Unwind_Resume() references in libgcc division functions
Date: Tue, 21 Jun 2022 15:44:34 +0200	[thread overview]
Message-ID: <652cffb2-2f0c-8f17-258b-bec6f24ca406@embedded-brains.de> (raw)
In-Reply-To: <YrHGgJluozl/eS8H@tucnak>

On 21/06/2022 15:24, Jakub Jelinek wrote:
> 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.

Thanks for the hint. It seems also the optimization level has an impact. 
The _Unwind_Resume dependency is only present if I use 
CFLAGS_FOR_TARGET="-O0 -g".

-- 
embedded brains GmbH
Herr Sebastian HUBER
Dornierstr. 4
82178 Puchheim
Germany
email: sebastian.huber@embedded-brains.de
phone: +49-89-18 94 741 - 16
fax:   +49-89-18 94 741 - 08

Registergericht: Amtsgericht München
Registernummer: HRB 157899
Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler
Unsere Datenschutzerklärung finden Sie hier:
https://embedded-brains.de/datenschutzerklaerung/

      reply	other threads:[~2022-06-21 13:44 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
2022-06-21 13:44   ` Sebastian Huber [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=652cffb2-2f0c-8f17-258b-bec6f24ca406@embedded-brains.de \
    --to=sebastian.huber@embedded-brains.de \
    --cc=gcc@gcc.gnu.org \
    --cc=jakub@redhat.com \
    /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).