From: Iain Buclaw <ibuclaw@gdcproject.org>
To: Chen Gang <gang.chen.5i5j@gmail.com>
Cc: gdb-patches@sourceware.org, Pedro Alves <palves@redhat.com>,
Mark Kettenis <mark.kettenis@xs4all.nl>
Subject: Re: [PATCH v2] gdb/i387-tdep.c: Avoid warning for "-Werror=strict-overflow"
Date: Sun, 12 Oct 2014 17:48:00 -0000 [thread overview]
Message-ID: <CABOHX+fC88nCwHy12_J5bVsbhs64pqjdC3-k2e0wqkdpWXteHA@mail.gmail.com> (raw)
In-Reply-To: <543A9464.50308@gmail.com>
On 12 October 2014 15:47, Chen Gang <gang.chen.5i5j@gmail.com> wrote:
> On 10/12/14 22:13, Iain Buclaw wrote:
>> On 12 October 2014 14:28, Chen Gang <gang.chen.5i5j@gmail.com> wrote:
>>> 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:
>>>
>>
>> I had noted the same on GCC 5.0.0 development, found that the line
>> number in the warning was wrong and raised a bug
>> (https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63510), just didn't get
>> round to submitting a patch for gdb.
>>
>
> But for me, what compiler has done is correct: "-Werror=strict-overflow"
> need include "(X + c) >= X" for signed overflow. And our case matches
> this case:
>
The compiler has done right, but that still doesn't stop the reported
line number being wrong.
-- Iain.
next prev parent reply other threads:[~2014-10-12 17:48 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 [this message]
2014-10-13 15:16 ` Mark Kettenis
2014-10-13 15:59 ` Chen Gang
2014-10-14 21:31 ` Chen Gang
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=CABOHX+fC88nCwHy12_J5bVsbhs64pqjdC3-k2e0wqkdpWXteHA@mail.gmail.com \
--to=ibuclaw@gdcproject.org \
--cc=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