public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libfortran/94694] [10 Regression][libgfortran] libgfortran does not compile on bare-metal aarch64-none-elf (newlib) Date: Wed, 22 Apr 2020 19:34:30 +0000 [thread overview] Message-ID: <bug-94694-4-cNAENQUNFp@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-94694-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94694 --- Comment #28 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>: https://gcc.gnu.org/g:1868599f8daf7798018ce8a8f314015f5a2ac520 commit r10-7893-g1868599f8daf7798018ce8a8f314015f5a2ac520 Author: Jakub Jelinek <jakub@redhat.com> Date: Wed Apr 22 19:17:15 2020 +0200 libgfortran: Provide some further math library fallbacks [PR94694] The following patch provides some further math library fallbacks. fmaf can be implemented using fma if available, fma and fmal can use x * y + z as fallback, it is not perfect, but e.g. glibc on various arches has been using that as fallback for many years, and copysign/copysignl/fabs/fabsl can be implemented using corresponding __builtin_* if we make sure that gcc expands it inline instead of using a library call (these days it is expanded inline on most targets). 2020-04-22 Jakub Jelinek <jakub@redhat.com> PR libfortran/94694 PR libfortran/94586 * configure.ac: Add math func checks for fmaf, fma and fmal. Add HAVE_INLINE_BUILTIN_COPYSIGN check. * c99_protos.h (copysign, fmaf, fma, fmal): Provide fallback prototypes. (HAVE_COPYSIGN, HAVE_FMAF, HAVE_FMA, HAVE_FMAL): Define if not defined and fallback version is provided. * intrinsics/c99_functions.c (copysign, fmaf, fma, fmal): Provide fallback implementations if possible * configure: Regenerated. * config.h.in: Regenerated. * math.m4 (GCC_CHECK_MATH_INLINE_BUILTIN_FALLBACK1, GCC_CHECK_MATH_INLINE_BUILTIN_FALLBACK2): New.
next prev parent reply other threads:[~2020-04-22 19:34 UTC|newest] Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-04-21 14:35 [Bug libfortran/94694] New: [libgfortran] " akrl at gcc dot gnu.org 2020-04-21 14:39 ` [Bug libfortran/94694] " akrl at gcc dot gnu.org 2020-04-21 14:40 ` [Bug libfortran/94694] [10 Regression][libgfortran] " ktkachov at gcc dot gnu.org 2020-04-21 15:05 ` rguenth at gcc dot gnu.org 2020-04-21 15:07 ` rguenth at gcc dot gnu.org 2020-04-21 15:32 ` jakub at gcc dot gnu.org 2020-04-21 15:40 ` rearnsha at gcc dot gnu.org 2020-04-21 15:55 ` rguenth at gcc dot gnu.org 2020-04-21 16:04 ` jakub at gcc dot gnu.org 2020-04-21 16:25 ` foreese at gcc dot gnu.org 2020-04-21 16:31 ` jakub at gcc dot gnu.org 2020-04-21 16:40 ` Andrea Corallo 2020-04-21 16:40 ` andrea.corallo at arm dot com 2020-04-21 16:45 ` jakub at gcc dot gnu.org 2020-04-21 17:04 ` foreese at gcc dot gnu.org 2020-04-21 17:13 ` jakub at gcc dot gnu.org 2020-04-21 17:14 ` jakub at gcc dot gnu.org 2020-04-21 17:23 ` jakub at gcc dot gnu.org 2020-04-21 17:37 ` rguenther at suse dot de 2020-04-21 17:42 ` jakub at gcc dot gnu.org 2020-04-21 18:10 ` foreese at gcc dot gnu.org 2020-04-21 19:06 ` jakub at gcc dot gnu.org 2020-04-21 19:40 ` jakub at gcc dot gnu.org 2020-04-21 21:03 ` foreese at gcc dot gnu.org 2020-04-21 22:43 ` jakub at gcc dot gnu.org 2020-04-22 11:21 ` andrea.corallo at arm dot com 2020-04-22 14:12 ` jakub at gcc dot gnu.org 2020-04-22 14:17 ` foreese at gcc dot gnu.org 2020-04-22 14:29 ` foreese at gcc dot gnu.org 2020-04-22 14:52 ` jakub at gcc dot gnu.org 2020-04-22 19:34 ` cvs-commit at gcc dot gnu.org [this message] 2020-04-23 14:12 ` cvs-commit at gcc dot gnu.org 2020-04-23 14:38 ` jakub at gcc dot gnu.org 2020-04-23 15:17 ` andrea.corallo at arm dot com
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=bug-94694-4-cNAENQUNFp@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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).