public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/25814] Request for warning for parser ambiguity of function declarations and variable declarations with initializations Date: Thu, 22 Oct 2020 15:02:44 +0000 [thread overview] Message-ID: <bug-25814-4-OyBT6SUaDZ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-25814-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=25814 Marek Polacek <mpolacek at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED Assignee|unassigned at gcc dot gnu.org |mpolacek at gcc dot gnu.org --- Comment #18 from Marek Polacek <mpolacek at gcc dot gnu.org> --- I now have a patch.
next prev parent reply other threads:[~2020-10-22 15:02 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-25814-4@http.gcc.gnu.org/bugzilla/> 2020-03-12 11:59 ` jakub at gcc dot gnu.org 2020-08-26 12:22 ` mpolacek at gcc dot gnu.org 2020-08-27 11:12 ` dmalcolm at gcc dot gnu.org 2020-08-27 14:33 ` mpolacek at gcc dot gnu.org 2020-10-22 15:02 ` mpolacek at gcc dot gnu.org [this message] 2020-11-05 20:56 ` cvs-commit at gcc dot gnu.org 2020-11-05 20:59 ` mpolacek at gcc dot gnu.org 2006-01-17 0:42 [Bug c++/25814] New: Request for new warning Raimund dot Merkert at baesystems dot com 2006-01-17 0:58 ` [Bug c++/25814] Request for warning for parser ambiguity of function declarations and variable declarations with initializations pinskia at gcc dot gnu dot org 2006-01-17 4:01 ` gdr at cs dot tamu dot edu 2006-01-17 12:33 ` Raimund dot Merkert at baesystems dot com 2006-02-02 19:54 ` pinskia at gcc dot gnu dot org 2006-03-08 5:07 ` bangerth at dealii dot org 2006-11-14 15:36 ` wolfgang dot roemer at gmx dot net 2006-11-14 15:52 ` Raimund dot Merkert at baesystems dot com
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-25814-4-OyBT6SUaDZ@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).