public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86 Boot enhancements, pic 16 4/9
Date: 03 Apr 2002 19:54:28 -0700	[thread overview]
Message-ID: <m17knorx5n.fsf@frodo.biederman.org> (raw)
In-Reply-To: <m11ydwu5at.fsf@frodo.biederman.org> <a8fls5$mur$1@cesium.transmeta.com>

"H. Peter Anvin" <hpa@zytor.com> writes:

> Followup to:  <m11ydwu5at.fsf@frodo.biederman.org>
> By author:    ebiederm@xmission.com (Eric W. Biederman)
> In newsgroup: linux.dev.kernel
> >
> > Linus please apply,
> > 
> > This patch makes not changes to the generated object code.
> > 
> > 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. 
> > 
> 
> Flexible in what way?

In that the object files generated can be treated as ordinary object
files, instead of needing special treatment.  

Since gas does not have an ASSUME segment directive to tell the
assembler where base addresses point the current code is arguable
broken.  And this patch is a bug fix.

I don't really need this patch but it sure makes life easier.

Eric

  reply	other threads:[~2002-04-04  3:01 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 [this message]
2002-04-05  8:01 ` Martin Mares
2002-04-05  8:29   ` Eric W. Biederman
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=m17knorx5n.fsf@frodo.biederman.org \
    --to=ebiederm@xmission.com \
    --cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox