From: "Manuel López-Ibáñez" <lopezibanez@gmail.com>
To: Martin Sebor <msebor@gmail.com>,
David Malcolm <dmalcolm@redhat.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Move class substring_loc from c-family into gcc
Date: Sat, 03 Sep 2016 09:22:00 -0000 [thread overview]
Message-ID: <067a2cb4-5380-34be-2ec6-d501010a3fb7@gmail.com> (raw)
In-Reply-To: <57CA035B.6080206@gmail.com>
On 02/09/16 23:55, Martin Sebor wrote:
>> diff --git a/gcc/substring-locations.h b/gcc/substring-locations.h
>> index f839c74..bb0de4f 100644
>> --- a/gcc/substring-locations.h
>> +++ b/gcc/substring-locations.h
>> @@ -20,6 +20,73 @@ along with GCC; see the file COPYING3. If not see
>> #ifndef GCC_SUBSTRING_LOCATIONS_H
>> #define GCC_SUBSTRING_LOCATIONS_H
>>
>> +#include <cpplib.h>
>> +
Is this header file going to be used in the middle-end? If so, then it is
suspicious that it includes cpplib.h. Otherwise, perhaps it should live in
c-family/
I'm not complaining about substring-locations.c because libcpp is already
linked with everything else even for other non-C languages, like Ada, but the
above is leaking all cpplib.h into the rest of the compiler, which defeats the
purpose of this in coretypes.h
/* Provide forward struct declaration so that we don't have to include
all of cpplib.h whenever a random prototype includes a pointer.
Note that the cpp_reader and cpp_token typedefs remain part of
cpplib.h. */
struct cpp_reader;
struct cpp_token;
Cheers,
Manuel.
next prev parent reply other threads:[~2016-09-03 9:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-25 15:40 David Malcolm
2016-08-25 15:54 ` [PATCH] Fixups for Martin's gimple-ssa-sprintf.c patch David Malcolm
2016-08-25 16:30 ` Martin Sebor
2016-08-31 16:23 ` Martin Sebor
2016-08-31 16:27 ` David Malcolm
2016-08-31 16:48 ` Martin Sebor
2016-09-02 23:57 ` [PATCH] Move class substring_loc from c-family into gcc Martin Sebor
2016-09-03 3:03 ` David Malcolm
2016-09-03 9:22 ` Manuel López-Ibáñez [this message]
2016-09-06 22:07 ` Martin Sebor
2016-09-07 17:19 ` [committed] " David Malcolm
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=067a2cb4-5380-34be-2ec6-d501010a3fb7@gmail.com \
--to=lopezibanez@gmail.com \
--cc=dmalcolm@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=msebor@gmail.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).