https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108099
--- Comment #4 from Moritz Klammler ---
I see, sorry for wasting your time. I forgot that there is a differently
spelled keyword in addition to the builtin(?) typedef. Since 'unsigned' got
accepted even with the typedef, it didn't occur to me no
++
Assignee: unassigned at gcc dot gnu.org
Reporter: moritz.klammler at cetitec dot com
Target Milestone: ---
There seems to be a problem in the parser regarding typedefs involving
__int128_t prefixed with the signed keyword.
$ cat test.ii
using i128 = signed __int128_t;
$ g
: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: moritz.klammler at cetitec dot com
Target Milestone: ---
After upgrading from GCC 8.3 to GCC 9.1 today, our code started to break. We
were able to eventually condense it down
