https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80243
Martin Sebor <msebor at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |WAITING Last reconfirmed| |2017-03-30 Ever confirmed|0 |1 --- Comment #7 from Martin Sebor <msebor at gcc dot gnu.org> --- I'm afraid comment #6 still doesn't give us enough to go on. It looks like a bunch of syntax errors for a source file that doesn't even seem obviously related to the snippets posted in comment #0 and comment #1. What we need to confirm and investigate a suspected GCC problem is a standalone test case and the command line options used to invoke the compiler so we can reproduce the errors. Quoting from the What we need section in https://gcc.gnu.org/bugs: * the options given when GCC was configured/built; * the complete command line that triggers the bug; * the compiler output (error messages, warnings, etc.); and * the preprocessed file (*.i*) that triggers the bug Quoting from From What we do not want on the same page: * A code snippet that won't cause the compiler to produce the exact output mentioned in the bug report. The last item on the first list can be obtained by preprocessing the source file with the -E option. Note, however, that preprocessing atoi64.cpp and providing atoi64.i is not going to help here because of the syntax errors. You need to investigate and (unless they are caused by a compiler bug) fix those yourself first. It is very unlikely that the syntax errors in comment #6 are caused by a compiler bug.