From: "Joel C. Salomon" <joelcsalomon@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] LLVM & Exceptions (Was re. request for more GSoC project suggestions)
Date: Thu, 26 Mar 2009 12:23:05 -0400 [thread overview]
Message-ID: <49CBABE9.6080107@gmail.com> (raw)
In-Reply-To: <9ab217670903251620n5511aa2ej14b22e725adf6eec@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1566 bytes --]
Devon H. O'Dell wrote:
> Another student I spoke to on IRC spoke of the possibility of
> bootstrapping LLVM for Plan 9 on Linux and getting it to run natively.
> That would give us a whole bunch of different compilers.
Something to watch out for with such a project:
The LLVM back-end for Windows does not support C++ (nicely) because of
issues with exception handling; Windows provides a mechanism for stack
unwinding—especially across DLL boundaries—that neither GCC nor LLVM
handle well. Porting LLVM to Plan 9 may well have some of the same
troubles.
Those who have dealt with the GCC port can answer this: What does g++
do on Plan 9? Does it add DWARF debugging tables to the executable so
that the stack can be unwound? Does it play games with setjmp/longjmp?
Does it even work at all? Otherwise, a large part of an LLVM project
would be a port of some exception mechanism.
Does plan9port’s mach-stack(3) have any precedent in Plan 9? and is that
the correct basis for exception-like stack unwinding? (I.e., a program
unwinding its own stack, rather than a debugger tracing the stack back.)
—Joel Salomon
P.s.: I am not raising the question of whether exception handling via
stack unwinding is a good idea—which has been done to death on this
list; see the “Same Functions Everywhere” thread from 2003 at
<http://preview.tinyurl.com/cou63b> and message 56 & responses at
<http://preview.tinyurl.com/cun6vg>—just asking how to implement it
under Plan 9 using the existing tools as far as possible.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 202 bytes --]
next prev parent reply other threads:[~2009-03-26 16:23 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-25 15:16 [9fans] request for more GSoC project suggestions Charles Forsyth
2009-03-25 15:06 ` Devon H. O'Dell
2009-03-26 5:19 ` lucio
2009-03-26 13:18 ` Devon H. O'Dell
2009-03-26 15:03 ` lucio
2009-03-26 15:17 ` lucio
2009-03-25 19:57 ` Paul Lalonde
2009-03-25 20:12 ` Devon H. O'Dell
2009-03-25 20:19 ` erik quanstrom
2009-03-25 20:28 ` Devon H. O'Dell
2009-03-25 20:38 ` Chris Brannon
2009-03-26 0:47 ` erik quanstrom
2009-03-26 1:10 ` Chris Brannon
2009-03-26 2:02 ` Roman Shaposhnik
2009-03-25 20:39 ` Paul Lalonde
2009-03-25 21:12 ` Charles Forsyth
2009-03-26 1:11 ` Roman V. Shaposhnik
2009-03-26 1:51 ` Paul Lalonde
2009-03-26 2:01 ` Roman Shaposhnik
2009-03-26 2:01 ` Devon H. O'Dell
2009-03-25 20:40 ` James Tomaschke
2009-03-25 22:48 ` Paul Lalonde
2009-03-25 23:20 ` Devon H. O'Dell
2009-03-25 23:26 ` erik quanstrom
2009-03-26 2:03 ` Devon H. O'Dell
2009-03-26 4:43 ` erik quanstrom
2009-03-26 2:05 ` Roman Shaposhnik
2009-03-26 14:21 ` Joel C. Salomon
2009-03-26 15:09 ` Juan M. Mendez
2009-03-26 15:18 ` Devon H. O'Dell
2009-03-26 16:23 ` Joel C. Salomon [this message]
2009-03-26 0:09 ` Federico G. Benavento
2009-03-26 1:54 ` Devon H. O'Dell
2009-03-26 10:41 ` Charles Forsyth
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=49CBABE9.6080107@gmail.com \
--to=joelcsalomon@gmail.com \
--cc=9fans@9fans.net \
/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;
as well as URLs for NNTP newsgroup(s).