From: Steve Kargl <sgk@troutmask.apl.washington.edu>
To: FX <fxcoudert@gmail.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>, gfortran <fortran@gcc.gnu.org>
Subject: Re: [libgfortran,patch] Remove never-used debugging code
Date: Tue, 25 Aug 2015 16:58:00 -0000 [thread overview]
Message-ID: <20150825165509.GA86137@troutmask.apl.washington.edu> (raw)
In-Reply-To: <6F486B34-1368-4E04-884C-597222EBD1A8@gmail.com>
On Tue, Aug 25, 2015 at 06:17:13PM +0200, FX wrote:
> Turns out I missed some of the dead code. And I now also fixed comments and some formatting.
> libgfortran/runtime/environ.c is now much more readable than before.
> The patch is still a no-op, in terms of user functionality.
> OK to commit to trunk?
>
Certainly, the dead code can go. But,is this changing
the library ABI?
troutmask:fvwm:kargl[764] nm /mnt/sgk/work/6/lib/libgfortran.a | grep show_
0000000000000000 T _gfortrani_show_variables
0000000000000000 t show_boolean
0000000000000000 t show_integer
0000000000000000 t show_sep
0000000000000000 t show_string
0000000000000000 T _gfortrani_show_locus
--
Steve
next prev parent reply other threads:[~2015-08-25 16:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-24 18:49 FX
2015-08-25 16:25 ` FX
2015-08-25 16:58 ` Steve Kargl [this message]
2015-08-25 17:10 ` FX
2015-08-25 18:01 ` Steve Kargl
2015-08-26 7:07 ` FX
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=20150825165509.GA86137@troutmask.apl.washington.edu \
--to=sgk@troutmask.apl.washington.edu \
--cc=fortran@gcc.gnu.org \
--cc=fxcoudert@gmail.com \
--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).