* Borislav Petkov <[email protected]> wrote:
> From: Borislav Petkov <[email protected]>
>
> When building the kernel with 32-bit binutils built with support only
> for the i386 target, we get the following warning:
>
> arch/x86/kernel/head_32.S:66: Warning: shift count out of range (32 is not
> between 0 and 31)
>
> The problem is that in that case, binutils' internal type representation
> is 32-bit wide and the shift range overflows.
>
> In order to fix this, manipulate the shift expression which creates the
> 4GiB constant to not overflow the shift count.
>
> Reported-and-tested-by: Enrico Mioso <[email protected]>
> Suggested-by: Michael Matz <[email protected]>
> Signed-off-by: Borislav Petkov <[email protected]>
> ---
> arch/x86/kernel/head_32.S | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/x86/kernel/head_32.S b/arch/x86/kernel/head_32.S
> index 53eeb226657c..c601d1de5ae5 100644
> --- a/arch/x86/kernel/head_32.S
> +++ b/arch/x86/kernel/head_32.S
> @@ -63,8 +63,8 @@
> #endif
>
> /* Number of possible pages in the lowmem region */
> -LOWMEM_PAGES = (((1<<32) - __PAGE_OFFSET) >> PAGE_SHIFT)
> -
> +LOWMEM_PAGES = (((2<<31) - __PAGE_OFFSET) >> PAGE_SHIFT)
> +
Hm, so if internally GAS uses 64-bit types, couldn't we 'make sure' it's a
64-bit
type, by using something like 31LL? Assuming GAS understands that?
Or if the internal representation is 32 bits, then 2<<31 is just a fancy way of
saying '0', right?
So this could be written as:
LOWMEM_PAGES = (-__PAGE_OFFSET >> PAGE_SHIFT)
or:
LOWMEM_PAGES = ((0 - __PAGE_OFFSET) >> PAGE_SHIFT)
right?
Or did it get it all wrong?
Thanks,
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
