From: Thomas Koenig <tkoenig@netcologne.de>
To: Jakub Jelinek <jakub@redhat.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>,
"fortran@gcc.gnu.org" <fortran@gcc.gnu.org>
Subject: Re: [power-ieee128, committed] Enable conversion selection via environment variable
Date: Tue, 11 Jan 2022 22:44:56 +0100 [thread overview]
Message-ID: <6463eaab-8f1d-8acf-562a-1bbc8fcc579a@netcologne.de> (raw)
In-Reply-To: <20220111131937.GW2646553@tucnak>
On 11.01.22 14:19, Jakub Jelinek via Fortran wrote:
> On Mon, Jan 10, 2022 at 11:44:13PM +0100, Thomas Koenig wrote:
>> Hello world,
>>
>> I have just pushed the attched patch to the branch.
>
> Thanks.
>
> Here is a patch to fix up the ppc64be vs. ppc64le byteswapping
> of IBM extended real(kind=16) and complex(kind=16).
> Similarly to the BT_COMPLEX case it halves size and doubles nelems
> for the bswap_array calls. Of course for r16_ibm and r16_ieee conversions
> one needs to make sure it is only done when the on file data is in that
> format and not in IEEE quad.
The patch is OK.
>> So... time to merge the branch into trunk before stage 4
>> kicks in?
>
> IMHO yes. We need to git merge master; git rebase of course
> before trying to cherry-pick those commits into trunk and pushing there.
I would prefer if somebody else did this - my lack of git-fu would
forseeably lead to some unforseen problems :-)
Best regards
Thomas
next prev parent reply other threads:[~2022-01-11 21:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-10 22:44 Thomas Koenig
2022-01-11 13:19 ` Jakub Jelinek
2022-01-11 21:44 ` Thomas Koenig [this message]
2022-01-11 23:07 ` 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=6463eaab-8f1d-8acf-562a-1bbc8fcc579a@netcologne.de \
--to=tkoenig@netcologne.de \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
/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).