From: Mark Eggleston <mark.eggleston@codethink.co.uk>
To: Fritz Reese <fritzoreese@gmail.com>, Jakub Jelinek <jakub@redhat.com>
Cc: fortran <fortran@gcc.gnu.org>, gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH, Fortran] pad char to int conversions with spaces instead of zeros (legacy)
Date: Mon, 10 Dec 2018 14:09:00 -0000 [thread overview]
Message-ID: <642cbe8d-d03f-3582-e830-84dba6330ee0@codethink.co.uk> (raw)
In-Reply-To: <cc881e3a-9fad-65a0-1135-989ad70e2574@codethink.co.uk>
On 06/12/2018 10:20, Mark Eggleston wrote:
>> Yes. Mark, you'll need to also patch iresolve.c (gfc_resolve_transfer)
>> to affect non-constant resolution.
> Thanks for the hint.
I've looked at gfc_resolve_transfer regarding handling of padding when a
character variable is passed to transfer instead of a literal. This
routine is not called so can't be where a variable would be handled.
Don't yet know where to make the change.
regards,
Mark
--
https://www.codethink.co.uk/privacy.html
next prev parent reply other threads:[~2018-12-10 14:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-04 14:47 Mark Eggleston
2018-12-04 15:11 ` Jakub Jelinek
2018-12-04 17:04 ` Fritz Reese
2018-12-06 2:27 ` Jerry DeLisle
2018-12-06 10:50 ` Jakub Jelinek
2018-12-06 10:54 ` Mark Eggleston
2018-12-07 1:57 ` Jerry DeLisle
2018-12-06 10:34 ` Mark Eggleston
2018-12-10 14:09 ` Mark Eggleston [this message]
2018-12-10 17:12 ` Jakub Jelinek
2018-12-10 19:44 ` Fritz Reese
2018-12-12 11:37 ` Mark Eggleston
2018-12-12 11:53 ` Jakub Jelinek
2018-12-12 12:06 ` Mark Eggleston
2018-12-12 12:12 ` Jakub Jelinek
2018-12-12 15:12 ` Mark Eggleston
2018-12-06 10:23 ` Mark Eggleston
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=642cbe8d-d03f-3582-e830-84dba6330ee0@codethink.co.uk \
--to=mark.eggleston@codethink.co.uk \
--cc=fortran@gcc.gnu.org \
--cc=fritzoreese@gmail.com \
--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).