public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Enrico Mioso <mrkiko.rs@gmail.com>
Cc: Michael Matz <matz@suse.de>,
	linux-kernel@vger.kernel.org, x86-ml <x86@kernel.org>
Subject: Re: X86 GIT GCC 5 compilation warning
Date: Tue, 16 Jun 2015 15:58:01 +0200	[thread overview]
Message-ID: <20150616135801.GH17786@pd.tnic> (raw)
In-Reply-To: <alpine.LSU.2.20.1506161446081.27315@wotan.suse.de>

On Tue, Jun 16, 2015 at 02:47:02PM +0200, Michael Matz wrote:
> Yeah, building like so on i686 will produce an assembler that warns on 
> "1<<32".

Enrico, try this.

---
From: Borislav Petkov <bp@suse.de>
Date: Tue, 16 Jun 2015 15:43:27 +0200
Subject: [PATCH] x86/head_32: Fix overflow warning with 32-bit binutils

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-by: Enrico Mioso <mrkiko.rs@gmail.com>
Suggested-by: Michael Matz <matz@suse.de>
Signed-off-by: Borislav Petkov <bp@suse.de>
---
 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)
+
 /* Enough space to fit pagetables for the low memory linear map */
 MAPPING_BEYOND_END = PAGE_TABLE_SIZE(LOWMEM_PAGES) << PAGE_SHIFT
 
-- 
2.3.5

-- 
Regards/Gruss,
    Boris.

ECO tip #101: Trim your mails when you reply.
--

  reply	other threads:[~2015-06-16 13:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-14 15:14 X86 GIT GCC 5 compilation warning Enrico Mioso
2015-06-14 18:07 ` Borislav Petkov
2015-06-15 11:30   ` Michael Matz
2015-06-15 17:17     ` Borislav Petkov
2015-06-16 11:59       ` Michael Matz
2015-06-16 12:39         ` Enrico Mioso
2015-06-16 12:47           ` Michael Matz
2015-06-16 13:58             ` Borislav Petkov [this message]
2015-06-16 14:09               ` Enrico Mioso
2015-06-16 14:42               ` Enrico Mioso
2015-06-16 15:32                 ` Borislav Petkov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150616135801.GH17786@pd.tnic \
    --to=bp@alien8.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matz@suse.de \
    --cc=mrkiko.rs@gmail.com \
    --cc=x86@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox