public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "doko at debian dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/97742] New: endless loop with code reduced by creduce/cvise Date: Fri, 06 Nov 2020 10:20:31 +0000 [thread overview] Message-ID: <bug-97742-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97742 Bug ID: 97742 Summary: endless loop with code reduced by creduce/cvise Product: gcc Version: 10.2.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: other Assignee: unassigned at gcc dot gnu.org Reporter: doko at debian dot org Target Milestone: --- Created attachment 49514 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=49514&action=edit preprocessed source seen with the gcc-10 branch, seen while reducing via cvise/creduce $ g++ -c -std=c++17 -fconcepts -Wall search_collection_test.ii In file included from search_collection_test.ii:689: /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:1148:13: error: expected primary-expression before ‘namespace’ /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:1150:11: error: expected ‘;’ before ‘namespace’ /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:1165:12: error: expected primary-expression before ‘namespace’ In file included from search_collection_test.ii:689: /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:1187:11: error: expected ‘;’ before ‘namespace’ /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:1191:13: error: expected primary-expression before ‘namespace’ [...] the compiler continues to emit error messages, doesn't terminate. compiler configured with --enable-checking=yes,extra,rtl
next reply other threads:[~2020-11-06 10:20 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-06 10:20 doko at debian dot org [this message] 2020-11-06 12:15 ` [Bug c++/97742] " marxin at gcc dot gnu.org 2020-11-06 12:20 ` marxin at gcc dot gnu.org 2020-12-07 12:45 ` [Bug c++/97742] [10/11 Regression] " rguenth at gcc dot gnu.org 2021-01-14 9:36 ` rguenth at gcc dot gnu.org 2021-01-21 18:06 ` mpolacek at gcc dot gnu.org 2021-02-11 13:53 ` jakub at gcc dot gnu.org 2021-02-12 3:14 ` mpolacek at gcc dot gnu.org 2021-02-12 8:58 ` cvs-commit at gcc dot gnu.org 2021-02-12 8:59 ` [Bug c++/97742] [10 " jakub at gcc dot gnu.org 2021-03-19 23:29 ` cvs-commit at gcc dot gnu.org 2021-03-20 8:07 ` jakub at gcc dot gnu.org 2021-04-27 10:44 ` redi at gcc dot gnu.org
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=bug-97742-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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: linkBe 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).