tags 625357 - moreinfo
retitle 62537 gcc -Wunused-but-set-variable warning is confusing
# bad error message
severity 625357 minor
quit
Steve McIntyre wrote:
> error = add_md5_entry(UNKNOWN, md5, file_name);
> return 0;
> }
>
> To explain a bit more: the warning reported by gcc (unhelpfull
On Thu, Jun 02, 2011 at 01:16:59PM -0500, Jonathan Nieder wrote:
>severity 625357 normal
>retitle 625357 gcc -Wunused-but-set-variable should not be implied by -Wall (?)
>tags 625357 = upstream moreinfo
>quit
>
>Hi again,
>
>Steve McIntyre wrote:
>
>> I'll remove the -Werror to stop gcc breaking th
On Wed, Jun 01, 2011 at 05:05:27PM -0500, Jonathan Nieder wrote:
>Hi Steve,
>
>Steve McIntyre wrote:
>
>> I'll remove the -Werror to stop gcc breaking the build here, but I
>> definitely believe that gcc is doing the wrong thing here.
>> Technically, yes - the variables are set but unused. However,
severity 625357 normal
retitle 625357 gcc -Wunused-but-set-variable should not be implied by -Wall (?)
tags 625357 = upstream moreinfo
quit
Hi again,
Steve McIntyre wrote:
> I'll remove the -Werror to stop gcc breaking the build here, but I
> definitely believe that gcc is doing the wrong thing
Hi Steve,
Steve McIntyre wrote:
> I'll remove the -Werror to stop gcc breaking the build here, but I
> definitely believe that gcc is doing the wrong thing here.
> Technically, yes - the variables are set but unused. However, this is
> a far higher level of pedantry than is warranted for -Wall.
Processing commands for cont...@bugs.debian.org:
> reassign 625357 gcc-4.6
Bug #625357 [jigit] jigit: ftbfs with gcc-4.6 -Werror
Bug reassigned from package 'jigit' to 'gcc-4.6'.
Bug No longer marked as found in versions jigit/1.18-1.
> thanks
Stopping processing here.
Please contact me if you ne
6 matches
Mail list logo
