From: Jakub Jelinek <jakub@redhat.com>
To: gcc-patches@gcc.gnu.org, fortran@gcc.gnu.org
Subject: Re: [PATCH] fortran: Add -static-libquadmath support [PR46539]
Date: Wed, 17 Aug 2022 09:19:46 +0200 [thread overview]
Message-ID: <YvyWkm/+6vMbzt74@tucnak> (raw)
In-Reply-To: <YvuqJyvOMhN1QSy2@tucnak>
On Tue, Aug 16, 2022 at 04:31:03PM +0200, Jakub Jelinek via Gcc-patches wrote:
> So far slightly tested on x86_64-linux (and will bootstrap/regtest
> it there tonight), but I unfortunately don't have a way to test it
FYI, successfully bootstrapped/regtested on x86_64-linux and i686-linux.
> 2022-08-16 Francois-Xavier Coudert <fxcoudert@gcc.gnu.org>
> Jakub Jelinek <jakub@redhat.com>
>
> PR fortran/46539
> gcc/
> * common.opt (static-libquadmath): New option.
> * gcc.c (driver_handle_option): Always accept -static-libquadmath.
> * config/darwin.h (LINK_SPEC): Handle -static-libquadmath.
> gcc/fortran/
> * lang.opt (static-libquadmath): New option.
> * invoke.texi (-static-libquadmath): Document it.
> * options.c (gfc_handle_option): Error out if -static-libquadmath
> is passed but we do not support it.
> libgfortran/
> * acinclude.m4 (LIBQUADSPEC): From $FC -static-libgfortran -###
> output determine -Bstatic/-Bdynamic, -bstatic/-bdynamic,
> -aarchive_shared/-adefault linker support or Darwin remapping
> of -lgfortran to libgfortran.a%s and use that around or instead
> of -lquadmath in LIBQUADSPEC.
> * configure: Regenerated.
Jakub
next prev parent reply other threads:[~2022-08-17 7:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-16 14:31 Jakub Jelinek
2022-08-17 7:19 ` Jakub Jelinek [this message]
2022-08-17 7:55 ` Tobias Burnus
2022-08-17 8:28 ` Mikael Morin
2022-08-17 11:05 ` [PATCH] fortran, v2: " Jakub Jelinek
2022-08-18 10:35 ` Iain Sandoe
2022-08-18 10:41 ` Jakub Jelinek
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=YvyWkm/+6vMbzt74@tucnak \
--to=jakub@redhat.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@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).