From: Pete Zaitcev <zaitcev@redhat.com>
To: Edgar Toernig <froese@gmx.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] [PATCH] C exceptions in kernel
Date: Sat, 23 Feb 2002 05:11:36 -0500 [thread overview]
Message-ID: <200202231011.g1NABaU10984@devserv.devel.redhat.com> (raw)
In-Reply-To: <mailman.1014437101.26721.linux-kernel2news@redhat.com>
In-Reply-To: <1014412325.1074.36.camel@callisto.yi.org> <mailman.1014437101.26721.linux-kernel2news@redhat.com>
>> The attached patch implements C exceptions in the kernel,
>
> Bad idea ...
Why is it bad? I can see a couple of reasons, but this does
not help me undestand your, unspecified, reasons.
>> which *don't* depend on special support from the compiler.
>
> ... which can be implemented in simple ANSI-C. See below.
Right, but the question is, do we support setjump/longjump
in kernel? The patch as I saw it does reimplement a similar thing
(check out its assembler fragments).
-- Pete
next prev parent reply other threads:[~2002-02-23 10:12 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-22 21:12 [RFC] [PATCH] C exceptions in kernel Dan Aloni
2002-02-22 21:28 ` Davide Libenzi
2002-02-22 22:10 ` Richard B. Johnson
2002-02-22 22:34 ` David B. Stevens
2002-02-22 22:48 ` Davide Libenzi
2002-02-23 3:37 ` Edgar Toernig
[not found] ` <mailman.1014437101.26721.linux-kernel2news@redhat.com>
2002-02-23 10:11 ` Pete Zaitcev [this message]
2002-02-23 12:26 ` Keith Owens
2002-02-23 12:50 ` Pete Zaitcev
2002-02-23 23:07 ` Jes Sorensen
2002-02-23 23:40 ` Keith Owens
2002-02-24 1:02 ` Jes Sorensen
2002-02-24 23:45 ` Richard Gooch
2002-02-23 23:50 ` Bill Huey
2002-02-24 1:31 ` Davide Libenzi
2002-02-24 2:55 ` Bill Huey
2002-02-23 15:13 ` Felix von Leitner
2002-02-23 15:21 ` bert hubert
2002-02-23 16:05 ` Dan Aloni
2002-02-23 16:22 ` Larry McVoy
2002-02-23 17:00 ` Dan Aloni
2002-02-23 17:52 ` Francois Romieu
2002-02-23 17:07 ` bert hubert
2002-02-23 17:47 ` Alexander Viro
2002-02-23 18:21 ` bert hubert
2002-02-23 18:31 ` Larry McVoy
2002-02-23 18:38 ` bert hubert
2002-02-23 19:12 ` Kurt Ferreira
2002-02-23 23:05 ` Jes Sorensen
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=200202231011.g1NABaU10984@devserv.devel.redhat.com \
--to=zaitcev@redhat.com \
--cc=froese@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