From: Richard Biener <richard.guenther@gmail.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
richard.sandiford@arm.com
Subject: Re: Mostly rewrite genrecog
Date: Thu, 30 Apr 2015 12:33:00 -0000 [thread overview]
Message-ID: <CAFiYyc0hQFiJVTR+++V9TikOAEmnHvGNHbDyuQTJ+6aJZrV2Vg@mail.gmail.com> (raw)
In-Reply-To: <87y4l9hl8s.fsf@igel.home>
On Thu, Apr 30, 2015 at 2:08 PM, Andreas Schwab <schwab@linux-m68k.org> wrote:
> Richard Sandiford <richard.sandiford@arm.com> writes:
>
>> Andreas Schwab <schwab@linux-m68k.org> writes:
>>> Richard Sandiford <richard.sandiford@arm.com> writes:
>>>
>>>> /* Represents a test and the action that should be taken on the result.
>>>> If a transition exists for the test outcome, the machine switches
>>>> to the transition's target state. If no suitable transition exists,
>>>> the machine either falls through to the next decision or, if there are no
>>>> more decisions to try, fails the match. */
>>>> struct decision : list_head <transition>
>>>> {
>>>> decision (const test &);
>>>>
>>>> void set_parent (list_head <decision> *s);
>>>> bool if_statement_p (uint64_t * = 0) const;
>>>>
>>>> /* The state to which this decision belongs. */
>>>> state *s;
>>>>
>>>> /* Links to other decisions in the same state. */
>>>> decision *prev, *next;
>>>>
>>>> /* The test to perform. */
>>>> struct test test;
>>>> };
>>>
>>> ../../gcc/genrecog.c:1467: error: declaration of 'test decision::test'
>>> ../../gcc/genrecog.c:1051: error: changes meaning of 'test' from 'struct test'
>>>
>>> Bootstrap compiler is gcc 4.3.4.
>>
>> Bah. Does it like "::test test" instead of "struct test test"?
>
> Same error.
You have to use a different name I believe (or -fpermissive).
Richard.
> Andreas.
>
> --
> Andreas Schwab, schwab@linux-m68k.org
> GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
> "And now for something completely different."
next prev parent reply other threads:[~2015-04-30 12:22 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-27 10:20 Richard Sandiford
2015-04-28 23:18 ` Jeff Law
2015-04-29 13:59 ` Richard Sandiford
2015-04-29 8:52 ` Eric Botcazou
2015-04-29 13:51 ` Richard Sandiford
2015-04-30 10:44 ` Eric Botcazou
2015-04-30 6:54 ` Bin.Cheng
2015-04-30 11:58 ` Richard Sandiford
2015-04-30 7:17 ` Andreas Schwab
2015-04-30 7:58 ` Richard Sandiford
2015-04-30 12:10 ` Andreas Schwab
2015-04-30 12:33 ` Richard Biener [this message]
2015-04-30 16:27 ` Richard Sandiford
2015-05-01 12:42 ` Richard Sandiford
2015-05-01 13:57 ` Jeff Law
2015-05-07 8:59 ` [nvptx] " Thomas Schwinge
2015-05-07 9:14 ` Jakub Jelinek
2015-05-21 8:09 ` Thomas Schwinge
2015-05-21 11:57 ` Bernd Schmidt
2015-05-08 9:10 ` genrecog: Address -Wsign-compare diagnostics (was: Mostly rewrite genrecog) Thomas Schwinge
2015-05-08 14:43 ` genrecog: Address -Wsign-compare diagnostics Richard Sandiford
2015-05-08 18:39 ` Jeff Law
2015-05-16 8:13 ` Mostly rewrite genrecog Andreas Krebbel
2015-05-17 22:05 ` Richard Sandiford
2015-05-22 16:14 ` Andreas Krebbel
2015-05-22 16:32 ` Richard Sandiford
2015-05-29 17:39 ` RFA: Fix mode checks for possibly-constant predicates Richard Sandiford
2015-05-29 19:27 ` Richard Henderson
2015-06-03 7:23 ` Richard Sandiford
2015-06-03 9:39 ` Richard Sandiford
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=CAFiYyc0hQFiJVTR+++V9TikOAEmnHvGNHbDyuQTJ+6aJZrV2Vg@mail.gmail.com \
--to=richard.guenther@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=richard.sandiford@arm.com \
--cc=schwab@linux-m68k.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).