public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Pierre-Marie de Rodat <pmderodat@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r13-606] [Ada] arm-qnx-7.1: undefined reference to fma* symbols Date: Wed, 18 May 2022 08:44:44 +0000 (GMT) [thread overview] Message-ID: <20220518084444.02CEE3858C53@sourceware.org> (raw) https://gcc.gnu.org/g:db67182120993abaff6bbaa1a64f1ba931a8380b commit r13-606-gdb67182120993abaff6bbaa1a64f1ba931a8380b Author: Doug Rupp <rupp@adacore.com> Date: Thu Apr 7 11:08:56 2022 -0700 [Ada] arm-qnx-7.1: undefined reference to fma* symbols Configure the arm-qnx runtime packages to avoid generating these symbols. gcc/ada/ * Makefile.rtl (arm-qnx): Use default (non-fma) target pair. Diff: --- gcc/ada/Makefile.rtl | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/gcc/ada/Makefile.rtl b/gcc/ada/Makefile.rtl index 7acb159f7ec..7b84ee5bd37 100644 --- a/gcc/ada/Makefile.rtl +++ b/gcc/ada/Makefile.rtl @@ -1510,7 +1510,6 @@ ifeq ($(strip $(filter-out arm aarch64 %qnx,$(target_cpu) $(target_os))),) LIBGNAT_TARGET_PAIRS = \ a-intnam.ads<libgnarl/a-intnam__qnx.ads \ a-nallfl.ads<libgnat/a-nallfl__wraplf.ads \ - s-dorepr.adb<libgnat/s-dorepr__fma.adb \ s-inmaop.adb<libgnarl/s-inmaop__posix.adb \ s-intman.adb<libgnarl/s-intman__qnx.adb \ s-osinte.adb<libgnarl/s-osinte__qnx.adb \ @@ -1534,6 +1533,10 @@ ifeq ($(strip $(filter-out arm aarch64 %qnx,$(target_cpu) $(target_os))),) else EH_MECHANISM=-gcc SIGTRAMP_OBJ=sigtramp-qnx.o + # "fma*" instructions not available for ARM fpu=vfpv3 + # but not an issue on AARCH64. + LIBGNAT_TARGET_PAIRS += \ + s-dorepr.adb<libgnat/s-dorepr__fma.adb LIBGNAT_TARGET_PAIRS += $(GNATRTL_128BIT_PAIRS) EXTRA_GNATRTL_NONTASKING_OBJS = $(GNATRTL_128BIT_OBJS) # Temporarily restrict shared library build to aarch64 (V303-025)
reply other threads:[~2022-05-18 8:44 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220518084444.02CEE3858C53@sourceware.org \ --to=pmderodat@gcc.gnu.org \ --cc=gcc-cvs@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).