public inbox for newlib@sourceware.org
 help / color / mirror / Atom feed
From: Jordi Sanfeliu <jordi@fibranet.cat>
To: newlib@sourceware.org
Subject: Re: undefined reference to '__builtin_mul_overflow'
Date: Fri, 25 Feb 2022 16:07:38 +0100	[thread overview]
Message-ID: <13657b8c-c380-8c88-f212-c3dce8fb41ee@fibranet.cat> (raw)
In-Reply-To: <d17e3a3b-056d-b7b1-0207-0ffc76be11b1@embedded-brains.de>

Hello Sebastian,

I appreciate your quick reply.


On 2/25/22 13:03, Sebastian Huber wrote:

> this builtin is available since GCC 5. Maybe you should update your GCC 
> version or implement __builtin_mul_overflow() in your operating system.
> 

Understood, time to upgrade the toolchain.

Just curiosity, what if I comment out these lines that are using that 
function?

Does this will suppose a malfunction later? I mean, is this function 
required to have a working Newlib 4.1.0 implementation?

Thanks.

-- 
Jordi Sanfeliu
FIBRANET Network Services Provider
https://www.fibranet.cat

      reply	other threads:[~2022-02-25 15:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-25 11:24 Jordi Sanfeliu
2022-02-25 12:03 ` Sebastian Huber
2022-02-25 15:07   ` Jordi Sanfeliu [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=13657b8c-c380-8c88-f212-c3dce8fb41ee@fibranet.cat \
    --to=jordi@fibranet.cat \
    --cc=newlib@sourceware.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).