From: ebiederm@xmission.com (Eric W. Biederman)
To: Martin Mares <mj@ucw.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86 Boot enhancements, pic 16 4/9
Date: 05 Apr 2002 01:29:49 -0700 [thread overview]
Message-ID: <m1k7rmpmyq.fsf@frodo.biederman.org> (raw)
In-Reply-To: <m11ydwu5at.fsf@frodo.biederman.org> <20020405080115.GA409@ucw.cz>
Martin Mares <mj@ucw.cz> writes:
> Hello!
>
> > Instead removes the assumption the code is linked to run at 0. The
> > binary code is already PIC, this makes the build process the same way,
> > making the build requirements more flexible.
>
> What are the reasons to do this change? The assumption that "linked at 0"
> assumptions looks pretty harmless and the "-start"'s everywhere are ugly.
Short answer the current assembly is broken.
Long answer.
Without the "-start"'s the gas generates a relocation record for
every one of those instructions. The correct syntax with gas is ugly.
If you can find the gas equivalent of an assume %ds ... directive I will use
it.
The fact that you can't treat the generated .o as a normal object
is simply a maintenance nightmare.
With this change it is possible to write a linker script that
generates a bzImage. I won't do it as every other build of ld
is broken with respect to interesting linker scripts. But there are
still some subsets of that idea that make sense.
Eric
next prev parent reply other threads:[~2002-04-05 8:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-03 16:15 [PATCH] x86 Boot enhancements, pic 16 4/9 Eric W. Biederman
2002-04-03 19:40 ` H. Peter Anvin
2002-04-04 2:54 ` Eric W. Biederman
2002-04-05 8:01 ` Martin Mares
2002-04-05 8:29 ` Eric W. Biederman [this message]
2002-04-05 8:47 ` Martin Mares
2002-04-05 8:58 ` Eric W. Biederman
2002-04-05 9:08 ` Martin Mares
2002-04-05 9:44 ` Eric W. Biederman
2002-04-05 10:59 ` Martin Mares
2002-04-05 16:24 ` Maciej W. Rozycki
2002-04-05 20:59 ` Eric W. Biederman
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=m1k7rmpmyq.fsf@frodo.biederman.org \
--to=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mj@ucw.cz \
/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