From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Christophe de Dinechin <dinechin@redhat.com>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: sign-compare warning for short and char
Date: Tue, 20 Feb 2018 19:49:00 -0000 [thread overview]
Message-ID: <CAH6eHdR2C7uoPo+zu6QOA4wP4WEkr+nUe4972+remEEnogRH8Q@mail.gmail.com> (raw)
In-Reply-To: <1FE711F4-D99F-47DB-8434-DFB7C96D82E8@redhat.com>
On 20 February 2018 at 15:43, Christophe de Dinechin wrote:
> I posted here because I saw it as a possible diagnostic bug / limitation. Do such things go to gcc-help? Or is it that you thought I was asking for the correct option?
Bug reports and enhancement requests go to bugzilla not here, and
questions about using GCC (including warnings and "why doesn't this
work?" stuff) belongs on gcc-help.
Although arguably this question is somewhere halfway between gcc@ and gcc-help@
prev parent reply other threads:[~2018-02-20 19:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-20 14:44 Christophe de Dinechin
2018-02-20 15:15 ` Jonathan Wakely
2018-02-20 15:43 ` Christophe de Dinechin
2018-02-20 19:49 ` Jonathan Wakely [this message]
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=CAH6eHdR2C7uoPo+zu6QOA4wP4WEkr+nUe4972+remEEnogRH8Q@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=dinechin@redhat.com \
--cc=gcc@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: 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).