From: Harald Anlauf <anlauf@gmx.de>
To: fortran@gcc.gnu.org
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] PR fortran/83079 - ICE and wrong code with TRANSFER and character(kind=4)
Date: Sat, 15 Jan 2022 21:50:42 +0100 [thread overview]
Message-ID: <8ab08d9a-ac48-6e52-37e5-297264f3b904@gmx.de> (raw)
Message-ID: <20220115205042.DRWMP0-iX7nrFPxe-IU3MJpmslC3ZcBcU6OY4paY4M4@z> (raw)
In-Reply-To: <trinity-765c74d7-b1c4-4db3-a3ed-683cddd99750-1641935832234@3c-app-gmx-bs15>
An early *ping* ...
Am 11.01.22 um 22:17 schrieb Harald Anlauf via Fortran:
> Dear Fortranners,
>
> when digging into the issue pointed out in the PR by Gerhard it turned
> out that there were several issues with the TRANSFER intrinsics in the
> case MOLD was CHARACTER(kind=4). Default CHARACTER was fine, though.
>
> - the size of the result was wrongly calculated
> - the string length used in temporaries was wrong
> - the result characteristics was wrong
>
> Fortunately, the few fixes were very local and needed only fix-ups of
> the respective computations.
>
> Since the details of which issue would show up seemed to depend on the
> properties of a the arguments to TRANSFER, I wrote an extended testcase
> which is a "hull" of what I used in debugging.
>
> (The testcase was and can be cross-checked with the NAG compiler.)
>
> Regtested on x86_64-pc-linux-gnu. OK for mainline?
>
> Thanks,
> Harald
>
next prev parent reply other threads:[~2022-01-15 20:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-11 21:17 Harald Anlauf
2022-01-15 20:50 ` Harald Anlauf [this message]
2022-01-15 20:50 ` Harald Anlauf
2022-01-15 21:28 ` Thomas Koenig
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=8ab08d9a-ac48-6e52-37e5-297264f3b904@gmx.de \
--to=anlauf@gmx.de \
--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).