|
From: | Bart Samwel |
Subject: | Re: [PATCH] gas value truncation warning reports truncated values, doesn't look at signedness. |
Date: | Mon, 12 Jan 2004 11:57:05 +0100 |
User-agent: | Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6b) Gecko/20031205 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?No, you do have separate gas binaries for each target. They could use the same shared libbfd.so though. I suspect that's what you have on your system.
Then it's funny that as uses 64-bit arithmetic, while it's clearly supposed to be a 32-bit assembler (I have an i386 system without any 64-bit parts -- a P3, to be exact). The arithmetic gas uses depends on bfd, which is 64-bit, but I think it might have to depend on the target architecture instead, i.e., N-bit target architecture = N-bit arithmetic. What do you think?
-- Bart
[Prev in Thread] | Current Thread | [Next in Thread] |