public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "reichelt at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/31748] New: [4.2/4.3 regression] bad diagnostic for invalid private clause Date: Sun, 29 Apr 2007 10:54:00 -0000 [thread overview] Message-ID: <bug-31748-1771@http.gcc.gnu.org/bugzilla/> (raw) A bad diagnostic is issued on mainline and the 4.2 branch for the following code snippet (compile with -fopenmp): ======================== struct A; void foo() { #pragma omp parallel private(A) ; } ======================== bug.cc: In function 'void foo()': bug.cc:5: error: '#'type_decl' not supported by dump_expr#<expression error>' is not a variable in clause 'private' -- Summary: [4.2/4.3 regression] bad diagnostic for invalid private clause Product: gcc Version: 4.3.0 Status: UNCONFIRMED Keywords: diagnostic, monitored, openmp Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: reichelt at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31748
next reply other threads:[~2007-04-29 10:54 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-04-29 10:54 reichelt at gcc dot gnu dot org [this message] 2007-04-29 10:55 ` [Bug c++/31748] " reichelt at gcc dot gnu dot org 2007-04-30 18:53 ` mmitchel at gcc dot gnu dot org 2007-05-01 13:08 ` jakub at gcc dot gnu dot org 2007-05-14 21:30 ` mmitchel at gcc dot gnu dot org 2007-07-02 13:00 ` jakub at gcc dot gnu dot org 2007-07-02 13:02 ` jakub at gcc dot gnu dot org 2007-07-02 13:02 ` jakub at gcc dot gnu dot 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-31748-1771@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).