From: Marek Polacek <polacek@redhat.com>
To: Gerald Pfeifer <gerald@pfeifer.com>
Cc: David Malcolm <dmalcolm@redhat.com>,
Martin Sebor <msebor@gmail.com>,
gcc-patches@gcc.gnu.org, Joseph Myers <joseph@codesourcery.com>,
Martin Sebor <msebor@redhat.com>,
Jason Merrill <jason@redhat.com>
Subject: Re: C/C++ PATCH to implement -Wmultistatement-macros (PR c/80116)
Date: Mon, 17 Jul 2017 09:26:00 -0000 [thread overview]
Message-ID: <20170717092555.GN2890@redhat.com> (raw)
In-Reply-To: <alpine.LSU.2.21.1707100054460.5621@anthias.pfeifer.com>
On Mon, Jul 17, 2017 at 10:15:40AM +0200, Gerald Pfeifer wrote:
> On Sat, 10 Jun 2017, Gerald Pfeifer wrote:
> > I'm curious to see how many issues this is going to find in real-world
> > code out there!
>
> This is a bit anecdotal, but your code did find one real issue in Wine:
>
> https://www.winehq.org/pipermail/wine-patches/2017-July/163551.html
> (and https://www.winehq.org/pipermail/wine-patches/2017-July/163550.html )
>
> The first patch was accepted, the second (but earlier one) not.
Thanks, good to see that. It's also found some bugs in glibc. Would love
to hear about kernel, too.
Marek
next prev parent reply other threads:[~2017-07-17 9:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-08 16:49 Marek Polacek
2017-06-08 17:24 ` David Malcolm
2017-06-08 18:10 ` Martin Sebor
2017-06-09 22:03 ` Gerald Pfeifer
2017-06-13 13:46 ` Marek Polacek
2017-07-17 8:15 ` Gerald Pfeifer
2017-07-17 9:26 ` Marek Polacek [this message]
2017-06-13 10:05 ` Marek Polacek
2017-06-13 15:29 ` Joseph Myers
2017-06-19 10:01 ` Marek Polacek
2017-06-26 9:40 ` Marek Polacek
2017-06-26 13:13 ` David Malcolm
2017-06-10 0:47 ` Jason Merrill
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=20170717092555.GN2890@redhat.com \
--to=polacek@redhat.com \
--cc=dmalcolm@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=jason@redhat.com \
--cc=joseph@codesourcery.com \
--cc=msebor@gmail.com \
--cc=msebor@redhat.com \
/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: link
Be 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).