Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Chen Gang <gang.chen.5i5j@gmail.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: gdb-patches@sourceware.org, palves@redhat.com
Subject: Re: [PATCH v2] gdb/i387-tdep.c: Avoid warning for "-Werror=strict-overflow"
Date: Tue, 14 Oct 2014 21:31:00 -0000	[thread overview]
Message-ID: <543D960F.3@gmail.com> (raw)
In-Reply-To: <543BF857.9080805@gmail.com>

On 10/14/2014 12:05 AM, Chen Gang wrote:
> On 10/13/14 23:16, Mark Kettenis wrote:
>>> Date: Sun, 12 Oct 2014 21:28:40 +0800
>>> From: Chen Gang <gang.chen.5i5j@gmail.com>
>>>
>>> gdb requires "-Werror", and I387_ST0_REGNUM (tdep) is 'variable', then
>>> compiler can think that I387_ST0_REGNUM (tdep) may be a large number,
>>> which may cause issue, so report warning.
>>>
>>> Need fix this warning, and still keep the code clear enough for readers.
>>> The related warning under Darwin with gnu built gcc:
>>
>> Sorry, I disagree with this approach.  I think your compiler is really
>> being unhelpful here.  See if a newer GCC version of the compiler
>> still triggers that warning.  If so, complain to the GCC people.
>>
> 
> Excuse me, I do not dare to complain it to gcc members, because for me,
> the compiler's printing is obviously, and proofs itself is correct. If I
> ask a quite obvious question to them, I guess, I will be complained.
> 
> Hmm... But I may have an additional trying: Use original gcc and provide
> "-Werror=strict-overflow" to see what will happen.
> 
>  - If it will report warning too, I can ask gcc members why integrate
>    "-Wstrict-overflow" to -Wall.
> 
>  - If it will not report warning, it means original gcc also integrate
>    "-Wstrict-overflow" or have no this option. And for me, I prefer to
>    use "#pragma GCC diagnostic ignored ... " for our code.

After use "gcc version 4.8.3 20140624 (Red Hat 4.8.3-1) (GCC)" with
"-Wstrict-overflow", it supports this flag, and does not report warning.

For me, either "$pragma GCC diagnostic ignored ..." or continuing this
patch. At present, I don't know any other ways for it.

Thanks.
-- 
Chen Gang

Open share and attitude like air water and life which God blessed


  reply	other threads:[~2014-10-14 21:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-12 13:22 Chen Gang
2014-10-12 14:13 ` Iain Buclaw
2014-10-12 14:41   ` Chen Gang
2014-10-12 17:48     ` Iain Buclaw
2014-10-13 15:16 ` Mark Kettenis
2014-10-13 15:59   ` Chen Gang
2014-10-14 21:31     ` Chen Gang [this message]
2014-10-15 18:47     ` Joel Brobecker
2014-10-15 18:59       ` Mark Kettenis
2014-10-12 23:48 Chen Gang
2014-11-10  1:39 ` Chen Gang
2015-01-09 21:50   ` Chen Gang S
2014-10-16  0:03 Chen Gang

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=543D960F.3@gmail.com \
    --to=gang.chen.5i5j@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=mark.kettenis@xs4all.nl \
    --cc=palves@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