linux-kernel - Re: [PATCH] [34/50] i386: Fix argument signedness warnings

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 22 Sep 2007 10:42:45 -0700
From:	Randy Dunlap <randy.dunlap@...cle.com>
To:	Jan Engelhardt <jengelh@...putergmbh.de>
Cc:	Satyam Sharma <satyam@...radead.org>, Andi Kleen <ak@...e.de>,
	patches@...-64.org,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] [34/50] i386: Fix argument signedness warnings

On Sat, 22 Sep 2007 12:01:16 +0200 (CEST) Jan Engelhardt wrote:

> 
> On Sep 22 2007 10:36, Satyam Sharma wrote:
> >> from arch/i386/boot/compressed/misc.c:14:
> >> include/asm/processor.h: In function .$B!F.(Jcpuid_count.$B!G.(J:
> >                                       ^^^^^^^^^^           ^^^^^^^^^^
> >> include/asm/processor.h:615: warning: pointer targets in passing
> >> argument 1 of .$B!F.(Jnative_cpuid.$B!G.(J differ in signedness
> >
> >> include/asm/processor.h:615: warning: pointer targets in passing
> >> argument 2 of .$B!F.(Jnative_cpuid.$B!G.(J differ in signedness
> >
> >> include/asm/processor.h:615: warning: pointer targets in passing
> >> argument 3 of .$B!F.(Jnative_cpuid.$B!G.(J differ in signedness
> >
> >> include/asm/processor.h:615: warning: pointer targets in passing
> >> argument 4 of .$B!F.(Jnative_cpuid.$B!G.(J differ in signedness
> >                ^^^^^^^^^^            ^^^^^^^^^^
> >
> >Yikes. My bad, I had faulty (default) alpine settings (and a sad
> >combination of LANG=en_US.UTF-8) when I made and sent out that patch.
> >Please ensure that this finally gets committed in a somewhat saner and
> >more readable state to the tree.
> 
> I am not too thrilled about gcc using non-ascii for interpunctuation
> (for Western languages)..

Ack.  I usually build with "LC_ALL=C" to make those readable.

---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/