mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Enrico Mioso <mrkiko.rs@gmail.com>, Michael Matz <matz@suse.de>
Cc: linux-kernel@vger.kernel.org, x86-ml <x86@kernel.org>
Subject: Re: X86 GIT GCC 5 compilation warning
Date: Sun, 14 Jun 2015 20:07:24 +0200	[thread overview]
Message-ID: <20150614180724.GB14892@pd.tnic> (raw)
In-Reply-To: <alpine.LNX.2.20.1506141711200.9260@localhost.localdomain>

On Sun, Jun 14, 2015 at 05:14:18PM +0200, Enrico Mioso wrote:
> Hi guys.
> Compiling my kernel with gcc (GCC) 5.1.0
> the GIT snapshot as of commit c8d17b451aa18b07b60e771addf17a5fdd4138c7
> I get the following warning you might be interested in:
> arch/x86/kernel/head_32.S:66: Warning: shift count out of range (32 is not between 0 and 31)

That's

LOWMEM_PAGES = (((1<<32) - __PAGE_OFFSET) >> PAGE_SHIFT)

and a 32-bit build. So gas hasn't been complaning so far about this.

Micha, did something change wrt constants type and width in gas in gcc5?

Judging by the warning, it seems gas considers the "1" a 4-byte type now
and complains about the shift overflow. But it didn't before and the asm
from gcc4.9 looks correct here.

What's up?

-- 
Regards/Gruss,
    Boris.

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

  reply	other threads:[~2015-06-14 18:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-14 15:14 Enrico Mioso
2015-06-14 18:07 ` Borislav Petkov [this message]
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
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=20150614180724.GB14892@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

all inboxes | Powered by JetHome®