public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Chen Gang S <gang.chen@sunrus.com.cn>
To: Iain Buclaw <ibuclaw@gdcproject.org>
Cc: gdb-patches@sourceware.org, Pedro Alves <palves@redhat.com>,
	 Mark Kettenis <mark.kettenis@xs4all.nl>,
	gcc-help@gcc.gnu.org
Subject: Re: [PATCH v2] gdb/i387-tdep.c: Avoid warning for "-Werror=strict-overflow"
Date: Fri, 09 Jan 2015 21:50:00 -0000	[thread overview]
Message-ID: <54B04ED2.6010000@sunrus.com.cn> (raw)
In-Reply-To: <546018BB.7090601@gmail.com>


At present, for gcc version 5.0.0 20150109 (experimental) (GCC), can not
find this warning again. So this thread can be ended. If it will appear
again in the future, I shall analyze it again only within gcc wide.

And sorry for having delayed a long time for it.

Thanks.

On 11/10/14 09:45, Chen Gang wrote:
> Hello Iain:
> 
> Is this bug still alive (I joined in bug 63510)? If it is, I shall try
> to fix it within this month (within 2014-11-30).
> 
> At present, its status is:
> 
>  - gcc members think that what compiler has done is correct, but need
>    improve its report line number:
> 
>      https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63510
> 
>  - gdb members might think what compiler has done is incorrect (need not
>    report warning).
> 
>  - for me, I agree with gcc members' opinion, and shall try to improve
>    its report line number.
> 
> 
> Welcome any ideas, suggestions and completions, in time.
> 
> Thanks.
> 
> On 10/13/14 7:45, Chen Gang wrote:
>> Oh, really it is. Originally, I skipped it (do not know it should be as an issue, too). Also sorry for my poor English: misunderstand what you said (this patch can still continue, although gcc 5 has another issue).
>>
>> And next, I shall try to fix it, based on what bugzilla has done. But excuse me, I have no enough time resource on it, so maybe can not finish within this month (try to finish within next month) .
>>
>> Thanks
>>
>> Send from Lenovo A788t.
>>
>>
>> Iain Buclaw <ibuclaw@gdcproject.org> wrote:
>>
>> 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.
>>
> 
> Thanks.
> 

-- 
Chen Gang

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

-- 
Chen Gang

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

  reply	other threads:[~2015-01-09 21:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-12 23:48 Chen Gang
2014-11-10  1:39 ` Chen Gang
2015-01-09 21:50   ` Chen Gang S [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-10-16  0:03 Chen Gang
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
2014-10-15 18:47     ` Joel Brobecker
2014-10-15 18:59       ` Mark Kettenis

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=54B04ED2.6010000@sunrus.com.cn \
    --to=gang.chen@sunrus.com.cn \
    --cc=gcc-help@gcc.gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=ibuclaw@gdcproject.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).