From: Joseph Myers <joseph@codesourcery.com>
To: Jeff Law <law@redhat.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PR middle-end/82123] 00/06 Use EVRP range data in sprintf warnings
Date: Wed, 21 Feb 2018 00:00:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1802202359090.7674@digraph.polyomino.org.uk> (raw)
In-Reply-To: <e8fcd96e-e3f8-c822-6434-7614804ce670@redhat.com>
Does this help with any of the cases in bug 80776 that weren't already
fixed, or are those distinct despite looking similar?
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2018-02-21 0:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-20 18:48 Jeff Law
2018-02-21 0:00 ` Joseph Myers [this message]
2018-02-21 2:38 ` Jeff Law
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=alpine.DEB.2.20.1802202359090.7674@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=law@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).