From: Thomas Koenig <tkoenig@netcologne.de>
To: sgk@troutmask.apl.washington.edu, fortran@gcc.gnu.org,
gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Shuffle ieee_arithmetic.F90
Date: Thu, 20 Dec 2018 13:43:00 -0000 [thread overview]
Message-ID: <89749152-f94d-9a4b-2286-51d58fcd43c1@netcologne.de> (raw)
In-Reply-To: <20181219050639.GA98555@troutmask.apl.washington.edu>
Hi Steve,
> The attach patch shuffles lines around to eliminate 80
> lines of #ifdef...#endif; thereby making the file more
> readable. Tested on i586-*-freebsd and x86_64-*-freebsd.
> Patch is a pre-requisite to fixing issues and adding
> missing functionality. OK to commit?
>
> 2018-12-18 Steven G. Kargl <kargl@gcc.gnu.org>
>
> * libgfortran/ieee/ieee_arithmetic.F90: Re-organize file to
> eliminate excessive #ifdef ... #endif.
>
OK. Thanks for the patch!
Regards
Thomas
next prev parent reply other threads:[~2018-12-20 13:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-19 5:06 Steve Kargl
2018-12-20 13:43 ` Thomas Koenig [this message]
2018-12-20 17:46 ` Steve Kargl
2018-12-20 19:40 ` Steve Kargl
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=89749152-f94d-9a4b-2286-51d58fcd43c1@netcologne.de \
--to=tkoenig@netcologne.de \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=sgk@troutmask.apl.washington.edu \
/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).