From: Arjan van de Ven <arjanv@redhat.com>
To: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
Cc: Keith Owens <kaos@ocs.com.au>, linux-kernel@vger.kernel.org
Subject: Re: 4k stacks in 2.6
Date: Thu, 27 May 2004 17:34:26 +0200 [thread overview]
Message-ID: <1085672066.7179.3.camel@laptop.fenrus.com> (raw)
In-Reply-To: <20040527152156.GI23194@wohnheim.fh-wedel.de>
[-- Attachment #1: Type: text/plain, Size: 931 bytes --]
On Thu, 2004-05-27 at 17:21, Jörn Engel wrote:
> On Fri, 28 May 2004 01:08:02 +1000, Keith Owens wrote:
> > On Thu, 27 May 2004 16:59:35 +0200,
> > =?iso-8859-1?Q?J=F6rn?= Engel <joern@wohnheim.fh-wedel.de> wrote:
> > >
> > >Plus the script is wrong sometimes. I have had trouble with sizes
> > >around 4G or 2G, and never found the time to really figure out what's
> > >going on. Might be an alloca thing that got misparsed somehow.
> >
> > Some code results in negative adjustments to the stack size on exit,
> > which look like 4G sizes. My script checks for those and ignores them.
> > /^[89a-f].......$/d;
>
> Ok, looks as if only my script is wrong. Do you know what exactly
> causes such a negative adjustment?
you can write "add 100,%esp" as "sub -100, %esp" :)
compilers seem to do that at times, probably some cpu model inside the
compiler decides the later is better code in some cases :)
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-05-27 15:34 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1ZQpn-1Rx-1@gated-at.bofh.it>
[not found] ` <1ZQz8-1Yh-15@gated-at.bofh.it>
[not found] ` <1ZRFf-2Vt-3@gated-at.bofh.it>
[not found] ` <203Zu-4aT-15@gated-at.bofh.it>
2004-05-26 13:57 ` Andi Kleen
2004-05-26 18:17 ` hch
2004-05-26 18:24 ` Andi Kleen
2004-05-26 20:39 ` Zwane Mwaikambo
[not found] ` <206b3-5WN-33@gated-at.bofh.it>
[not found] ` <20baw-1Lz-15@gated-at.bofh.it>
2004-05-26 19:32 ` Andi Kleen
2004-05-27 11:27 ` Jörn Engel
2004-05-27 13:49 ` Andrea Arcangeli
2004-05-27 14:15 ` Jörn Engel
2004-05-27 14:49 ` Andrea Arcangeli
2004-05-27 14:59 ` Jörn Engel
2004-05-27 15:08 ` Keith Owens
2004-05-27 15:21 ` Jörn Engel
2004-05-27 15:34 ` Arjan van de Ven [this message]
2004-05-27 15:46 ` Jörn Engel
2004-06-01 5:25 ` Jörn Engel
2004-05-26 15:17 Albert Cahalan
-- strict thread matches above, loose matches on Subject: below --
2004-05-25 19:50 4g/4g for 2.6.6 Rik van Riel
2004-05-25 20:10 ` Rik van Riel
2004-05-25 21:15 ` Andrea Arcangeli
2004-05-26 10:33 ` 4k stacks in 2.6 Ingo Molnar
2004-05-26 12:50 ` Jörn Engel
2004-05-26 12:53 ` Arjan van de Ven
2004-05-26 13:00 ` Jörn Engel
2004-05-26 13:05 ` Arjan van de Ven
2004-05-26 16:41 ` Jörn Engel
2004-05-27 12:45 ` Ingo Molnar
2004-05-27 13:59 ` Andrea Arcangeli
2004-05-27 14:03 ` Arjan van de Ven
2004-05-27 14:42 ` Andrea Arcangeli
2004-06-02 19:40 ` Bill Davidsen
2004-05-27 14:18 ` Brian Gerst
2004-05-27 14:50 ` Andrea Arcangeli
2004-05-27 14:55 ` Linus Torvalds
2004-05-27 15:39 ` Andrea Arcangeli
2004-05-27 18:31 ` Guy Sotomayor
2004-05-27 19:26 ` Brian Gerst
2004-06-07 18:14 ` Timothy Miller
2004-06-08 6:26 ` Arjan van de Ven
2004-06-08 8:45 ` Jörn Engel
2004-05-26 18:12 ` David S. Miller
2004-05-26 19:02 ` Matt Mackall
2004-05-26 19:25 ` Dave Jones
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=1085672066.7179.3.camel@laptop.fenrus.com \
--to=arjanv@redhat.com \
--cc=joern@wohnheim.fh-wedel.de \
--cc=kaos@ocs.com.au \
--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
all inboxes | Powered by JetHome®