From: FX <fxcoudert@gmail.com>
To: fortran@gcc.gnu.org
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [patch, Fortran] IEEE support for aarch64-apple-darwin
Date: Wed, 15 Dec 2021 09:59:53 +0100 [thread overview]
Message-ID: <5DDE9803-FBAF-4D97-840B-B109D534FE6D@gmail.com> (raw)
In-Reply-To: <93D8CCF9-4230-4517-A993-A811092ADC4B@gmail.com>
ping for that patch
(don’t mind the ChangeLog question, I’ve figured it out, will include proper ChangeLog in the commit)
> Le 6 déc. 2021 à 17:32, FX <fxcoudert@gmail.com> a écrit :
>
> Hi everyone,
>
> Since support for target aarch64-apple-darwin has been submitted for review, it’s time to submit the Fortran part, i.e. enabling IEEE support on that target.
>
> The patch has been in use now for several months, in a developer branch shipped by some distros on macOS (including Homebrew). It was authored more than a year ago, but I figured it wasn’t relevant to submit until the target was actually close to be in trunk: https://github.com/iains/gcc-darwin-arm64/commit/b107973550d3d9a9ce9acc751adbbe2171d13736
>
> Bootstrapped and tested on aarch64-apple-darwin20 (macOS Big Sur) and aarch64-apple-darwin21 (macOS Monterey).
>
> OK to merge?
> Can someone point me to the right way of formatting ChangeLogs and commit entries, nowadays?
>
>
> Thanks,
> FX
>
> <b107973550d3d9a9ce9acc751adbbe2171d13736.patch>
next prev parent reply other threads:[~2021-12-15 8:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-06 16:32 FX
2021-12-08 15:36 ` Richard Earnshaw
2021-12-08 15:47 ` FX
2021-12-08 16:08 ` Richard Earnshaw
2021-12-15 8:59 ` FX [this message]
2021-12-19 21:03 ` Thomas Koenig
2021-12-19 23:50 ` FX
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=5DDE9803-FBAF-4D97-840B-B109D534FE6D@gmail.com \
--to=fxcoudert@gmail.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).