All of lore.kernel.org
 help / color / mirror / Atom feed
From: Manfred Spraul <manfred@colorfullife.com>
To: Arnd Bergmann <arnd@bergmann-dalldorf.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] reduce large stack usage
Date: Sun, 02 Mar 2003 16:26:31 +0100	[thread overview]
Message-ID: <3E6222A7.9030705@colorfullife.com> (raw)

Arnd wrote:

> The twofish one is obviously
>broken, and I suspect huft_build/inflate_dynamic are the cause of the
>crashes I'm seeing during unpacking of initramfs.
>
What do you mean with broken? On i386, the function needs 32 byte stack 
+ the space for register saving.
It must be either a gcc bug, or a bug in your detection script - I don't 
see anything special in twofish_setkey.

--
    Manfred


             reply	other threads:[~2003-03-02 15:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-02 15:26 Manfred Spraul [this message]
2003-03-02 17:07 ` [PATCH] reduce large stack usage Arnd Bergmann
     [not found] <20030301071007$18ea@gated-at.bofh.it>
2003-03-02 14:11 ` Arnd Bergmann
2003-03-02 15:38   ` Anders Gustafsson
2003-03-02 17:14     ` Arnd Bergmann
  -- strict thread matches above, loose matches on Subject: below --
2003-03-01  7:06 Randy.Dunlap

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=3E6222A7.9030705@colorfullife.com \
    --to=manfred@colorfullife.com \
    --cc=arnd@bergmann-dalldorf.de \
    --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.