From: Jeff Law <law@redhat.com>
To: "Martin Liška" <mliska@suse.cz>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Remove Pascal language in source code.
Date: Thu, 13 Jul 2017 14:59:00 -0000 [thread overview]
Message-ID: <d005b3d1-45bb-815f-bb20-e41f6fdd19a0@redhat.com> (raw)
In-Reply-To: <b1d44588-5a54-a970-118c-292b372d5042@suse.cz>
On 07/11/2017 08:30 AM, Martin Liška wrote:
> Hi.
>
> Similar for GNU Pascal language.
>
> Patch can bootstrap on ppc64le-redhat-linux and survives regression tests.
>
> Ready to be installed?
>
> Martin
>
> gcc/ChangeLog:
>
> 2017-07-11 Martin Liska <mliska@suse.cz>
>
> * dbxout.c (get_lang_number): Do not handle GNU Pascal.
> * dbxout.h (extern void dbxout_stab_value_internal_label_diff):
> Remove N_SO_PASCAL.
> * dwarf2out.c (lower_bound_default): Do not handle
> DW_LANG_Pascal83.
> (gen_compile_unit_die): Likewise.
> * gcc.c: Remove default extension binding for GNU Pascal.
> * stmt.c: Remove Pascal language from a comment.
> * xcoffout.c: Likewise.
The only concern I'd have here is the bits in dbxout.[ch] might
effectively be the best documentation of the dbxout format that exists.
Thus, dropping something like N_SO_PASCAL loses that historical
documentation.
Even with that caveat, I think this should go into the trunk. In the
unlikely event we really need that historical record, we have svn/git.
jeff
next prev parent reply other threads:[~2017-07-13 14:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-11 14:30 Martin Liška
2017-07-11 14:42 ` [RFC] Remaining references of Pascal Martin Liška
2017-07-11 15:57 ` Jason Merrill
2017-07-13 8:10 ` [PATCH] Cleanup #2 of Pascal references Martin Liška
2017-07-13 13:37 ` Jason Merrill
2017-07-13 14:59 ` Jeff Law [this message]
2017-07-13 16:07 ` [PATCH] Remove Pascal language in source code Pedro Alves
2017-07-14 7:05 ` Martin Liška
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=d005b3d1-45bb-815f-bb20-e41f6fdd19a0@redhat.com \
--to=law@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=mliska@suse.cz \
/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).