public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Matt Mackall <mpm@selenic.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	discuss@x86-64.org, Tom Rini <trini@kernel.crashing.org>
Subject: Re: [CFT] inflate.c rework arch testing needed
Date: Fri, 19 Mar 2004 10:31:26 +0000	[thread overview]
Message-ID: <20040319103126.A12519@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20040318231006.GK11010@waste.org>; from mpm@selenic.com on Thu, Mar 18, 2004 at 05:10:06PM -0600

On Thu, Mar 18, 2004 at 05:10:06PM -0600, Matt Mackall wrote:
> I've reworked the mess that is lib/inflate.c, including:

Please don't - this will probably break the PIC decompressor on ARM.

There are un-merged patches in the pipeline which make this all work
correctly with todays toolchains - which mostly means getting rid of
all static data to make the compiler produce the right relocations.

Yes its stupid, but there seems to be no other way to do this with
the ELF toolchains we have available to us now.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 PCMCIA      - http://pcmcia.arm.linux.org.uk/
                 2.6 Serial core

  parent reply	other threads:[~2004-03-19 10:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-18 23:10 [CFT] inflate.c rework arch testing needed Matt Mackall
2004-03-19  0:32 ` Jörn Engel
2004-03-19  3:09   ` Matt Mackall
2004-03-19  9:29     ` Jörn Engel
2004-03-28  7:00     ` [discuss] " Pavel Machek
2004-04-01 12:14       ` Jörn Engel
2004-03-19 10:31 ` Russell King [this message]
2004-03-19 17:16   ` Matt Mackall
2004-03-19 21:39     ` Russell King
2004-03-19 22:25       ` Matt Mackall

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=20040319103126.A12519@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --cc=discuss@x86-64.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpm@selenic.com \
    --cc=trini@kernel.crashing.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