Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: Paul Koning <paulkoning@comcast.net>, gdb@sourceware.org
Subject: Re: GDB 8.1 build error
Date: Fri, 27 Apr 2018 20:41:00 -0000	[thread overview]
Message-ID: <9ed9617b-987e-3225-8518-a43eda0b5548@redhat.com> (raw)
In-Reply-To: <b02d45ab46b5a572724bccbbb5eed7d4@polymtl.ca>

On 04/27/2018 09:16 PM, Simon Marchi wrote:

> On clang at least, -Wnarrowing seems to generate an error by default, so -w doesn't affect it.  You get:
> 
>   no flag: error
>   -Wno-error=narrowing: warning
>   -Wno-error=narrowing -w: silent
> 
> So in this case, we would still need either -Wno-error=narrowing or -Wno-narrowing.
> 
> We can test if gcc behaves the same, we just need something that is an error by default but we can downgrade to a warning.  Do you have an idea of such diagnostic?

-Wnarrowing is on by default on gcc, and -w disables it.

Thanks,
Pedro Alves


  reply	other threads:[~2018-04-27 20:24 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-27 18:02 Paul Koning
2018-04-27 18:38 ` Simon Marchi
2018-04-27 18:57   ` Paul Koning
2018-04-27 19:01     ` Paul Koning
2018-04-27 19:08     ` Simon Marchi
2018-04-27 19:18       ` Paul Koning
2018-04-27 20:41       ` Paul Koning
2018-04-27 19:10     ` Simon Marchi
2018-04-27 19:10     ` Pedro Alves
2018-04-27 19:39       ` Simon Marchi
2018-04-27 20:00         ` Pedro Alves
2018-04-27 20:16         ` Pedro Alves
2018-04-27 20:24           ` Simon Marchi
2018-04-27 20:41             ` Pedro Alves [this message]
2018-04-27 20:48               ` Simon Marchi
2018-05-02  9:42                 ` Pedro Alves
2018-05-02 10:13                   ` Pedro Alves

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=9ed9617b-987e-3225-8518-a43eda0b5548@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb@sourceware.org \
    --cc=paulkoning@comcast.net \
    --cc=simon.marchi@polymtl.ca \
    /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