Re: Exposing gthreads, and making exceptions safe under cthreads

[Alexandre Oliva <oliva at dcc dot unicamp dot br>]

Melissa O'Neill <oneill@cs.sfu.ca> writes:

> It's also possible to provide a replacement cthreads header that
> redirects cthreads names to gthreads names so that cthreads programs
> can transparently use the gthreads library instead, with zero work on
> the part of the user.

It might be possible to install this header as a replacement of the
standard cthreads header (if there is one; I'm just guessing) in the
gcc include PATH, so that it wraps the standard cthreads header
redirecting the calls as appropriate.

Another alternative is to modify gcc so that it internally handles the
gthreads calls as built-ins or aliases to gthreads functions.

-- 
Alexandre Oliva
mailto:oliva@dcc.unicamp.br mailto:aoliva@acm.org
http://www.dcc.unicamp.br/~oliva
Universidade Estadual de Campinas, SP, Brasil