All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tim Cambrant <tim@cambrant.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: 2.6.0 setup.S assembler messages
Date: Thu, 18 Dec 2003 21:28:36 +0100	[thread overview]
Message-ID: <20031218202836.GA13575@cambrant.com> (raw)

I posted this a while ago but got no replies. When I compiled 2.6.0 today,
the warning was still there, so I felt that a repost might be useful for
someone.

I thought it would be best to report this warning I get at the 
very end of the compiling-process. I'm no programmer or kernel- 
developer, so there is no way for me to tell of what significance 
this is. 

Anyway, I get this message even after a 'make mrproper', so I'm 
quite sure it's not a problem with old junk-files or something. 
When I look in setup.S at line 165, I find nothing but a reference 
to MAXMEM-1 or something like that, and it does seem odd that the 
value gets truncated into an identical value (unless the value was 
truncated before the message got printed, that is). 

--------------------------------------- 
AS arch/i386/boot/setup.o 
	arch/i386/boot/setup.S: Assembler messages: 
	arch/i386/boot/setup.S:165: Warning: value 0x37ffffff truncated to 0x37ffffff
LD arch/i386/boot/setup 
--------------------------------------- 

I'm running i386-systems with the 2.6.0-kernel. I got the same 
message on two different computers, one AMD Athlon TBird, and one 
Intel Celeron. 

Is this a known problem, and is there a fix to this somehow?

-- 
Tim Cambrant <tim@cambrant.com> 
GPG KeyID 0x59518702
Fingerprint: 14FE 03AE C2D1 072A 87D0  BC4D FA9E 02D8 5951 8702

             reply	other threads:[~2003-12-18 20:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-18 20:28 Tim Cambrant [this message]
2003-12-18 20:46 ` 2.6.0 setup.S assembler messages Tim Cambrant

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=20031218202836.GA13575@cambrant.com \
    --to=tim@cambrant.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.