This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH 0/4] bitpos expansion summary reloaded
- From: Jan Kratochvil <jan dot kratochvil at redhat dot com>
- To: Siddhesh Poyarekar <siddhesh at redhat dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Tue, 6 Nov 2012 21:01:17 +0100
- Subject: Re: [PATCH 0/4] bitpos expansion summary reloaded
- References: <20120927190053.1e7de264@spoyarek> <20120929173938.GA2987@host2.jankratochvil.net> <20120929181141.GA4009@host2.jankratochvil.net> <20120930065211.GA21118@host2.jankratochvil.net> <20121003184155.03dceed4@spoyarek> <20121003195627.GA17283@host2.jankratochvil.net> <20121004071314.GA4292@host2.jankratochvil.net> <20121021130546.02ea680c@spoyarek> <20121025155412.GA16619@host2.jankratochvil.net> <20121025222123.68c7b118@spoyarek>
On Thu, 25 Oct 2012 18:51:23 +0200, Siddhesh Poyarekar wrote:
> On Thu, 25 Oct 2012 17:54:12 +0200, Jan wrote:
> > we will go with the fix without the full -Wconversion fix.
> >
> > As most of the patches are very mechanical could you write a script
> > which will try to separate the "clear" and human-review parts?
> >
> > "clear" I find that the patch is understood by the script (that is it
> > is some s/int/LONGEST/ etc.) and that it does remove >= 1
> > -Wconversion warnings.
> >
> > Otherwise I will write such script. I hope it would "approve" most
> > of the patches.
>
> It would be great if you could do this. I won't be able to get on it
> this week.
I have created the scripts below so far:
http://people.redhat.com/jkratoch/conversiontest.pl
http://people.redhat.com/jkratoch/buffer.c
http://people.redhat.com/jkratoch/conversionsplit.pl
But it will be still several weeks of work to split and verify all the patch
chunks and after it is all done GDB will be still buggy wrt the 64-bit offsets
safety as was shown below.
Therefore going to drop it and start just normally fixing all the warnings for
-Wconversion -Wno-sign-conversion where the number of warnings is several
times larger but each such warning is simple and clear to fix. Unless someone
has a better idea.
Regards,
Jan