From: Bernd Edlinger <bernd.edlinger@hotmail.de>
To: Jakub Jelinek <jakub@redhat.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
Jason Merrill <jason@redhat.com>,
Jonathan Wakely <jwakely@redhat.com>
Subject: Re: [C++ PATCH] Fix option handling when -std=gnu++14 is not used (PR 69865)
Date: Fri, 19 Feb 2016 15:31:00 -0000 [thread overview]
Message-ID: <HE1PR07MB0905B4BEFDABD6F63786507FE4A00@HE1PR07MB0905.eurprd07.prod.outlook.com> (raw)
In-Reply-To: <20160219152243.GP3017@tucnak.redhat.com>
On 19.02.2016 16:22, Jakub Jelinek wrote:
> On Fri, Feb 19, 2016 at 03:09:25PM +0000, Bernd Edlinger wrote:
>> Hmm... wait a moment.
>> How about that?
>
> Guess it is mostly reasonable (still, this is C++ FE, so I'd prefer
> Jason to ack it), except for:
>
>> +#define libc_name_p Perfect_Hash::libc_name_p
>
Yeee. Right.
> this. Doesn't that cause
> Perfect_Hash::libc_name_p (register const char *str, register unsigned int len)
> to expand as
> Perfect_Hash:: Perfect_Hash::libc_name_p (register const char *str, register unsigned int len)
> ?
>
> So, I think better might be something like:
>
> --- gcc/cp/Make-lang.in.jj 2016-01-04 14:55:57.000000000 +0100
> +++ gcc/cp/Make-lang.in 2016-02-19 16:21:11.538734055 +0100
> @@ -112,7 +112,7 @@ else
> # deleting the $(srcdir)/cp/cfns.h file.
> $(srcdir)/cp/cfns.h:
> endif
> - gperf -o -C -E -k '1-6,$$' -j1 -D -N 'libc_name_p' -L ANSI-C \
> + gperf -o -C -E -k '1-6,$$' -j1 -D -N 'libc_name_p' -L C++ \
> $(srcdir)/cp/cfns.gperf --output-file $(srcdir)/cp/cfns.h
>
> #\f
> --- gcc/cp/except.c.jj 2016-01-04 14:55:57.000000000 +0100
> +++ gcc/cp/except.c 2016-02-19 16:20:37.134205968 +0100
> @@ -1040,7 +1040,8 @@ nothrow_libfn_p (const_tree fn)
> unless the system headers are playing rename tricks, and if
> they are, we don't want to be confused by them. */
> id = DECL_NAME (fn);
> - return !!libc_name_p (IDENTIFIER_POINTER (id), IDENTIFIER_LENGTH (id));
> + return !!libc_name::libc_name_p (IDENTIFIER_POINTER (id),
> + IDENTIFIER_LENGTH (id));
> }
>
> /* Returns nonzero if an exception of type FROM will be caught by a
> --- gcc/cp/cfns.gperf.jj 2016-02-19 14:41:14.000000000 +0100
> +++ gcc/cp/cfns.gperf 2016-02-19 16:19:34.841060418 +0100
> @@ -1,3 +1,5 @@
> +%language=C++
> +%define class-name libc_name
> %{
I like this idea with class-name.
Will post an updated patch in a minute.
Thanks
Bernd.
next prev parent reply other threads:[~2016-02-19 15:31 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-19 10:50 Bernd Edlinger
2016-02-19 10:56 ` Jakub Jelinek
2016-02-19 11:09 ` Bernd Edlinger
2016-02-19 11:31 ` Jakub Jelinek
2016-02-19 11:53 ` Bernd Edlinger
2016-02-19 11:59 ` Jakub Jelinek
2016-02-19 12:10 ` Bernd Edlinger
2016-02-19 12:22 ` Jakub Jelinek
2016-02-19 12:26 ` Jakub Jelinek
2016-02-19 15:09 ` Bernd Edlinger
2016-02-19 15:22 ` Jakub Jelinek
2016-02-19 15:31 ` Bernd Edlinger [this message]
2016-02-19 15:51 ` Bernd Edlinger
2016-02-19 16:03 ` Jason Merrill
2016-02-19 16:10 ` Jakub Jelinek
2016-02-19 16:19 ` Bernd Edlinger
2016-02-19 19:37 ` Bernd Edlinger
2016-02-19 19:47 ` Jason Merrill
2016-02-20 6:38 ` Bernd Edlinger
2016-02-25 15:27 ` Jakub Jelinek
2016-02-19 16:39 ` Jakub Jelinek
2016-02-19 17:26 ` Bernd Edlinger
2016-02-19 15:09 ` Bernd Edlinger
2016-02-19 13:07 ` Bernd Edlinger
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=HE1PR07MB0905B4BEFDABD6F63786507FE4A00@HE1PR07MB0905.eurprd07.prod.outlook.com \
--to=bernd.edlinger@hotmail.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=jason@redhat.com \
--cc=jwakely@redhat.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).