From: Keith Owens <kaos@sgi.com>
To: kdb@oss.sgi.com
Cc: linux-kernel@vger.kernel.org
Subject: Announce: kdb v2.3 i386 updates for kernels 2.4.18 and 2.4.19
Date: Fri, 09 Aug 2002 16:52:18 +1000 [thread overview]
Message-ID: <1076.1028875938@kao2.melbourne.sgi.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Content-Type: text/plain; charset=us-ascii
Updated files in ftp://oss.sgi.com/projects/kdb/download/v2.3/
kdb-v2.3-2.4.18-i386-2.bz2
kdb-v2.3-2.4.19-i386-2.bz2
I also have kdb-v2.3-2.4.18-ia64-020722-2 in progress, to add support
for zx1 serial i/o. Not tested yet, it should be out tomorrow.
Changelog extracts between 2.4.1[89]-i386-1 and -2.
2.4.19-i386-2
2002-08-09 Keith Owens <kaos@sgi.com>
* Use -fno-optimize-sibling-calls for kdb if gcc supports it.
* .text.lock does not consume an activation frame.
* kdb v2.3-2.4.19-i386-2.
2.4.18-i386-2
2002-08-09 Keith Owens <kaos@sgi.com>
* Use -fno-optimize-sibling-calls for kdb if gcc supports it.
* 2.4.18 uses _text_lock_ not .text.lock.
* _text_lock does not consume an activation frame.
* kdb v2.3-2.4.18-i386-2.
When gcc optimizes sibling calls (tail recursion), kdb <= v2.3 cannot
decode the backtrace. Nor can the stack trace show what is really
going on with optimized sibling calls, the return addresses are
ambiguous. Until I can come up with an algorithm to trace through tail
recursion, activating kdb will set -fno-optimize-sibling-calls.
kdb v2.4 is planned as a big gcc catch up, to cope with the code
generated by more recent versions of gcc.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Exmh version 2.1.1 10/15/1999
iD8DBQE9U2agi4UHNye0ZOoRArfUAJ9BXPmRQCJPenkTyBFHiV9zRB6dkACgxkPT
qeyKkLrO/ZTyQ0j3VUa92J8=
=7U08
-----END PGP SIGNATURE-----
next reply other threads:[~2002-08-09 6:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-09 6:52 Keith Owens [this message]
2002-08-10 9:14 ` Announce: kdb v2.3 i386 updates for kernels 2.4.18 and 2.4.19 Keith Owens
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=1076.1028875938@kao2.melbourne.sgi.com \
--to=kaos@sgi.com \
--cc=kdb@oss.sgi.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