From: Jakub Jelinek <jakub@redhat.com>
To: Jerry DeLisle <jvdelisle@charter.net>
Cc: Fritz Reese <fritzoreese@gmail.com>,
mark.eggleston@codethink.co.uk,
fortran <fortran@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>,
Jeff Law <law@redhat.com>
Subject: Re: [PATCH, Fortran] pad char to int conversions with spaces instead of zeros (legacy)
Date: Thu, 06 Dec 2018 10:50:00 -0000 [thread overview]
Message-ID: <20181206103312.GP12380@tucnak> (raw)
In-Reply-To: <3666ba47-343a-21ea-cdba-43d9d5a6709f@charter.net>
On Wed, Dec 05, 2018 at 06:27:00PM -0800, Jerry DeLisle wrote:
> I disagree completely. I assume the idea of -fdec-pad-with-spaces is to
> accomodate some old dec fortran code. The only reason to use some other
> character is if someone is writing new dec fortran code, which is implying
> encouraging people to be writing non standard conforming code.
>
> Even if it is conforming in the sense that it is processor dependent you are
> encouraging people to create new non portable code across compilers. Please
> just stay consistent with Intel.
So do you prefer to always use ' ' instead of '\0', or decide based on -fdec
without a separate option controlling that?
Jakub
next prev parent reply other threads:[~2018-12-06 10:50 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 [this message]
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
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=20181206103312.GP12380@tucnak \
--to=jakub@redhat.com \
--cc=fortran@gcc.gnu.org \
--cc=fritzoreese@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jvdelisle@charter.net \
--cc=law@redhat.com \
--cc=mark.eggleston@codethink.co.uk \
/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).