From: Chen Gang <gang.chen.5i5j@gmail.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: amodra@gmail.com, gbenson@redhat.com, michael.sturm@intel.com,
brobecker@adacore.com, walfred.tedeschi@intel.com,
binutils@sourceware.org, gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb/i387-tdep.c: Avoid warning for "-Werror=strict-overflow"
Date: Fri, 03 Oct 2014 16:02:00 -0000 [thread overview]
Message-ID: <542EC9FC.8050107@gmail.com> (raw)
In-Reply-To: <201410031546.s93FknOM002165@glazunov.sibelius.xs4all.nl>
On 10/3/14 23:46, Mark Kettenis 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.
>
> Sorry, but obfuscating code to make compilers happy is *not* the way to go.
>
OK, I can understand, but for me, these is no other better ways for it,
except let gdb give up "-Werror" (if always need "--disable-werror"
during "configure").
Thanks.
>> 2014-10-03 Chen Gang <gang.chen.5i5j@gmail.com>
>>
>> *i387-tdep.c (i387_supply_fsave): Avoid warning for
>> "-Werror=strict-overflow"
>> ---
>> gdb/i387-tdep.c | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/gdb/i387-tdep.c b/gdb/i387-tdep.c
>> index d66ac6a..c89e647 100644
>> --- a/gdb/i387-tdep.c
>> +++ b/gdb/i387-tdep.c
>> @@ -454,7 +454,7 @@ i387_supply_fsave (struct regcache *regcache, int regnum, const void *fsave)
>>
>> gdb_assert (tdep->st0_regnum >= I386_ST0_REGNUM);
>>
>> - for (i = I387_ST0_REGNUM (tdep); i < I387_XMM0_REGNUM (tdep); i++)
>> + for (i = I387_ST0_REGNUM (tdep); I387_XMM0_REGNUM (tdep) - i > 0; i++)
>> if (regnum == -1 || regnum == i)
>> {
>> if (fsave == NULL)
>> @@ -507,7 +507,7 @@ i387_collect_fsave (const struct regcache *regcache, int regnum, void *fsave)
>>
>> gdb_assert (tdep->st0_regnum >= I386_ST0_REGNUM);
>>
>> - for (i = I387_ST0_REGNUM (tdep); i < I387_XMM0_REGNUM (tdep); i++)
>> + for (i = I387_ST0_REGNUM (tdep); I387_XMM0_REGNUM (tdep) - i > 0; i++)
>> if (regnum == -1 || regnum == i)
>> {
>> /* Most of the FPU control registers occupy only 16 bits in
>> --
>> 1.8.5.2 (Apple Git-48)
>>
--
Chen Gang
Open, share, and attitude like air, water, and life which God blessed
next prev parent reply other threads:[~2014-10-03 16:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-03 15:24 Chen Gang
2014-10-03 15:46 ` Mark Kettenis
2014-10-03 16:02 ` Chen Gang [this message]
2014-10-03 16:44 ` Joel Brobecker
2014-10-03 18:47 ` Pedro Alves
2014-10-04 5:12 ` Chen Gang
2014-10-06 8:41 ` Pedro Alves
2014-10-06 13:29 ` Chen Gang
2014-10-10 11:22 ` Chen Gang
2014-10-09 10:06 ` Walfred Tedeschi
2014-10-09 11:20 ` 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=542EC9FC.8050107@gmail.com \
--to=gang.chen.5i5j@gmail.com \
--cc=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=brobecker@adacore.com \
--cc=gbenson@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
--cc=michael.sturm@intel.com \
--cc=walfred.tedeschi@intel.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