https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63198
Patrick Palka changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63198
--- Comment #7 from CVS Commits ---
The master branch has been updated by Patrick Palka :
https://gcc.gnu.org/g:6e92a6a2a72d3b7a5e1b29042d8a6a43fe1085aa
commit r14-4111-g6e92a6a2a72d3b7a5e1b29042d8a6a43fe1085aa
Author: Patrick Palka
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63198
--- Comment #6 from Thomas Bernard thomas at famillebernardgouriou dot fr ---
The assignment operator is an operator which always has side effects. That is
why it is considered dependent during template definitions to prevent early
instanciations
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63198
--- Comment #5 from Thomas Bernard thomas at famillebernardgouriou dot fr ---
I think I found the root of the problem. I'm preparing a patch.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63198
--- Comment #4 from Thomas Bernard thomas at famillebernardgouriou dot fr ---
I investigated a bit further and I come up to the same conclusion as Bob
Abeles.
Having an assignment operator inside the decltype makes gcc believe the type is
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63198
Thomas Bernard thomas at famillebernardgouriou dot fr changed:
What|Removed |Added
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63198
--- Comment #2 from Bob Abeles eightycc at gmail dot com ---
This bug occurs when cp/parser.c:cp_parser_name() while parsing 'decltype(y =
y)::t1' is called on 't1'. Earlier, the decltype has been determined to be
dependent (it isn't actually in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63198
Jonathan Wakely redi at gcc dot gnu.org changed:
What|Removed |Added
Keywords||rejects-valid
