public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Earnshaw <Richard.Earnshaw@foss.arm.com>
To: Enrico Tabanelli <enrico.tabanelli3@unibo.it>,
	"gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: Re: Builiding not optimized Libgcc for ARM Cortex-M4 target
Date: Mon, 7 Dec 2020 13:00:45 +0000	[thread overview]
Message-ID: <74b8dfc5-9cd2-8b20-b2cb-852dda35ac4a@foss.arm.com> (raw)
In-Reply-To: <VE1PR01MB5933CFE57576E92D7372B2D4C3F20@VE1PR01MB5933.eurprd01.prod.exchangelabs.com>

On 03/12/2020 21:24, Enrico Tabanelli wrote:
> Hi Richard,
> 
> Do you know how to hack the build system properly to exclude the
> optimized routines?

Sorry, not in detail.  Most of the changes will probably be in
libgcc/config/arm; but you may also need to make changes to
gcc/config/arm/arm.c to handle the function names that are used when
calling the soft-float C code.

R.

> 
> Enrico
> ------------------------------------------------------------------------
> *From:* Richard Earnshaw <Richard.Earnshaw@foss.arm.com>
> *Sent:* Thursday, December 3, 2020 12:59 PM
> *To:* Enrico Tabanelli <enrico.tabanelli3@unibo.it>;
> gcc-help@gcc.gnu.org <gcc-help@gcc.gnu.org>
> *Subject:* Re: Builiding not optimized Libgcc for ARM Cortex-M4 target
>  
> On 24/11/2020 20:47, Enrico Tabanelli via Gcc-help wrote:
>> Good morning,
>> 
>> I am trying to compile Libgcc for the ARM Cortex-M4 target from scratch since I need to compare Floating Point SW emulation on an ARM Cortex-M4 and Risc-V based processors. By default, GCC includes an optimized version of the FP SW emulation routines, ieee754-sf.S, which is included in the ARM back-end of Libgcc. For my work, I would
> like to use the basic routines included in libgcc/softfp.
>> Does anyone know how to exclude ieee754-sf.S in the libgcc building process? In particular, how to configure GCC and if there is something to change inside the ARM back-end?
>> 
>> Thanks,
>> Enrico Tabanelli
>> 
> 
> I think you'd need to hack the build system.  I'm not aware of any
> standard configuration hooks to do this.
> 
> R.


      reply	other threads:[~2020-12-07 13:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-24 20:47 Enrico Tabanelli
2020-12-03 11:59 ` Richard Earnshaw
2020-12-03 21:24   ` Enrico Tabanelli
2020-12-07 13:00     ` Richard Earnshaw [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=74b8dfc5-9cd2-8b20-b2cb-852dda35ac4a@foss.arm.com \
    --to=richard.earnshaw@foss.arm.com \
    --cc=enrico.tabanelli3@unibo.it \
    --cc=gcc-help@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).