darcs patch: Get External Core (-fext-core) working with readline

[Simon Marlow]

Samuel Bronson wrote:
> On 11/1/06, Aaron Tomb <atomb at soe.ucsc.edu> wrote:
> 
>> Good to know about. I did part of this, as well --- printing External
>> Core in 6.7 resulted in a panic, since coercions weren't translated,
>> and I fixed that. The patch mentioned below goes beyond mine, though,
>> by adding support for foreign labels. Fortunately, what I did was
>> only a few lines, and not much work. I was waiting to finish work on
>> the parser before I sent in a patch.
> 
> 
> I didn't write more than a few lines myself. Note that *all* I did was
> the dynamic calls and labels, add a calling convention field to the
> static calls, plus fixing up those two string constants that were used
> for printing arrows.
> 
>> Also, Sam, if you're also interested in getting the parser working,
>> we should coordinate so that we don't duplicate work.
> 
> 
> I wasn't planning on it; I only did the above because I wanted to be
> able to compare optimization results for standard library modules
> between slightly different compilers.
> 
> Unfortunately I have no idea where to look for the *time*... I wish
> non-exported ("static") names were qualified with the module name in
> the object files, just like exported names are... (would make it
> easier to compare output between cachegrind runs, IMO)

I worry slightly about bloating the symbol table and increasing link times, but 
perhaps I shouldn't.  You can make this change pretty easily - see the 
Outputable instance for Name in the Name module.

Cheers,
	Simon