From: Matthias Andree <matthias.andree@gmx.de>
To: Linux-Kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: post 2.6.7 BK change breaks Java?
Date: Mon, 12 Jul 2004 16:05:51 +0200 [thread overview]
Message-ID: <20040712140551.GA7264@merlin.emma.line.org> (raw)
In-Reply-To: <40F28628.2030303@quark.didntduck.org>
On Mon, 12 Jul 2004, Brian Gerst wrote:
[a hell of a quote that got snipped]
> >gcc 3.4.0
> >
> >I got a patch from Linus yesterday that seems to fix it nicely on top of
> >2.6.8-rc1. I guess he has his reasons for not CC'ing it to the list, but
> >I've given him feedback on my testing of it, so I hope it'll surface as
> >soon as he's happy with it.
>
> I see Linus commited a changeset that avoids a tailcall from this
> function, which messes up the stack if CONFIG_REGPARM=n. Specifically,
> it clobbers %edx in the pt_regs image:
>
> sys_sigaltstack:
> movl 56(%esp), %eax
> movl %eax, 12(%esp)
> jmp do_sigaltstack
After a BK pull and a rebuild, Java is well again.
--
Matthias Andree
Encrypted mail welcome: my GnuPG key ID is 0x052E7D95 (PGP/MIME preferred)
next prev parent reply other threads:[~2004-07-12 14:05 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-05 23:11 Matthias Andree
2004-07-06 15:55 ` John Richard Moser
2004-07-06 16:14 ` Matthias Andree
2004-07-06 17:49 ` John Richard Moser
2004-07-06 22:45 ` Andy Isaacson
2004-07-09 13:51 ` Jesper Juhl
2004-07-09 14:54 ` Con Kolivas
2004-07-09 16:37 ` José de Paula
2004-07-09 17:55 ` Jesper Juhl
2004-07-10 11:41 ` Go Taniguchi
2004-07-11 15:16 ` Jesper Juhl
2004-07-11 15:19 ` Con Kolivas
2004-07-11 15:35 ` Jesper Juhl
2004-07-11 15:35 ` Grzegorz Kulewski
2004-07-11 15:38 ` Jesper Juhl
2004-07-12 0:56 ` Jesper Juhl
2004-07-12 3:20 ` Brian Gerst
2004-07-12 3:57 ` Brian Gerst
2004-07-12 11:01 ` Jesper Juhl
2004-07-12 12:38 ` Brian Gerst
2004-07-12 14:05 ` Matthias Andree [this message]
2004-07-12 15:59 ` Linus Torvalds
2004-07-12 21:50 ` Bill Davidsen
2004-07-06 18:38 Ray Lee
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=20040712140551.GA7264@merlin.emma.line.org \
--to=matthias.andree@gmx.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 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®