[m-dev.] for review: GCC back-end: integrate with mmc

[Fergus Henderson]

On 16-Jan-2001, Tyson Dowd <trd at cs.mu.OZ.AU> wrote:
> Here's the plan:
> 
> foreign.m should run as a pre-pass over the MLDS that leaves only 
> preferred foreign code language (in this case, C).  The intention is
> that each backend need only know how to generate its own code and how to
> interface to its preferred language (as mlds_to_gcc already does).
> 
> foreign.m (or maybe some other code) will also handle generating the
> non-C file, generating dependencies on these extra files and will be
> responsible for arranging for the foreign language compiler to be run.
> 
> So as far as each backend is concerned, foreign_code will only ever be
> the preferred language, which will be handled exactly as you have
> handled it here (and as it is handled in mlds_to_ilasm.m).

That sounds like a good plan.

> Note that this isn't how it works at the moment, so it's fine to leave
> the XXX in the code at the moment -- mlds_to_c will eventually call
> error if non-C code makes it through.

Yes, I'll leave the XXX in.

-- 
Fergus Henderson <fjh at cs.mu.oz.au>  |  "I have always known that the pursuit
                                    |  of excellence is a lethal habit"
WWW: <http://www.cs.mu.oz.au/~fjh>  |     -- the last words of T. S. Garp.
--------------------------------------------------------------------------
mercury-developers mailing list
Post messages to:       mercury-developers at cs.mu.oz.au
Administrative Queries: owner-mercury-developers at cs.mu.oz.au
Subscriptions:          mercury-developers-request at cs.mu.oz.au
--------------------------------------------------------------------------