From: Michael Matz <matz@suse.de>
To: Borislav Petkov <bp@alien8.de>
Cc: Enrico Mioso <mrkiko.rs@gmail.com>,
linux-kernel@vger.kernel.org, x86-ml <x86@kernel.org>
Subject: Re: X86 GIT GCC 5 compilation warning
Date: Tue, 16 Jun 2015 13:59:20 +0200 (CEST) [thread overview]
Message-ID: <alpine.LSU.2.20.1506161353270.27315@wotan.suse.de> (raw)
In-Reply-To: <20150615171750.GP4255@pd.tnic>
Hello,
On Mon, 15 Jun 2015, Borislav Petkov wrote:
> Hmm, so I did start my oS13.2 i386 guest:
>
> $ as --version
> GNU assembler (GNU Binutils; openSUSE 13.2) 2.24.0.20140403-6.1
That won't show the issue. Our binutils are compiled with support for
multiple targets, among them 64bit ones, and as I said, that makes the
internal value types be 64bit as well, and hence masks the warning.
You could compile binutils yourself in that i386 guest, without enabling
other than the host target to see the problem, but why would you want
that?
> $ gcc --version
Again, gcc doesn't enter the picture here, it's gas itself that warns if
it was compiled with the right (or wrong) options.
> $ cat t.s
> .text
> LOWMEM_PAGES = (((1<<32) - 0xc0000000) >> 12)
>
> mov LOWMEM_PAGES, %eax
>
> $ as t.s
> $
My self-compiled gas warns here.
> Do we have some bleeding edge gcc5 rpms somewhere I could try?
devel:gcc, but gcc is not the cause here.
Ciao,
Michael.
next prev parent reply other threads:[~2015-06-16 11:59 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 [this message]
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=alpine.LSU.2.20.1506161353270.27315@wotan.suse.de \
--to=matz@suse.de \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).