From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Strange asm warning from bsetupt.s in 2.5.3-pre5
Date: 24 Jan 2002 14:49:11 -0800 [thread overview]
Message-ID: <a2q317$ln$1@cesium.transmeta.com> (raw)
In-Reply-To: <3C5082E3.C3A61B27@easynet.be>
Followup to: <3C5082E3.C3A61B27@easynet.be>
By author: Luc Van Oostenryck <luc.vanoostenryck@easynet.be>
In newsgroup: linux.dev.kernel
>
> I've just finished to compile 2.5.3-pre5 and I noticed
> the following strange warning from as(1):
> as -o bsetup.o bsetup.s
> bsetup.s: Assembler messages:
> bsetup.s:1180: Warning: Value 0x37ffffff truncated to 0x37ffffff.
> ~~~~~~ ~~~~~~
>
> It's comming from the small change introduced in setup.S:
> ramdisk_max: .long __MAXMEM-1 # (Header version 0x0203 or later)
>
>
> FYI as(1) version is:
> as --version
> GNU assembler 2.11.90.0.19
>
Suggest reporting a bug to binutils-bug@gnu.org?
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt <amsp@zytor.com>
prev parent reply other threads:[~2002-01-24 22:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-24 21:55 Strange asm warning from bsetupt.s in 2.5.3-pre5 Luc Van Oostenryck
2002-01-24 22:49 ` H. Peter Anvin [this message]
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='a2q317$ln$1@cesium.transmeta.com' \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.