|
From: | Bart Samwel |
Subject: | Re: [PATCH] gas value truncation warning reports truncated values, doesn't look at signedness. |
Date: | Mon, 12 Jan 2004 08:46:18 +0100 |
User-agent: | Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6b) Gecko/20031221 Thunderbird/0.4 |
Alan Modra wrote:
-- i386, to be precise. So I don't know why Debian compiles with a 64-bit bfd for a 32-bit arch. Would there be any reason for them to doProbably so that readelf, objdump etc. work on 64 bit binaries, such as those for x86_64.
Ah, that explains. But is there a reason then that bfd's bit-width determines the bit-width of gas as well, all in one swoop? I could imagine multiple gases on an x86_64 system, one for 64-bit, one for 32-bit. Or is that handled all in one version of gas? Because then you get these nasty warnings that we've been talking about on the LKML, any time you use ~. :( (Can't think of any other nasty side-effects of using a single binary however -- it really shouldn't make any difference if you use modulo (1 << 64) arithmetic and cut off to (1 << 32) later, or use modulo (1 << 32) arithmetic natively.)
-- Bart
[Prev in Thread] | Current Thread | [Next in Thread] |