[LLVMdev] Segmented Stacks: Pre-midterm work

[Evan Shaw]

2011/8/17 Sanjoy Das <sanjoy at playingwithpointers.com>:
> As far as I can see (after hand-tweaking the assembly generated for a
> simple example), there is no problem with the calling
> convention. Also, go_write_export_data only seems to generate to some
> sort of debug information (which does not look like DWARF).

It's not exactly debug info. It's export info. Go doesn't have header
files, but the compiler needs some way of discovering what functions,
types, variables, and constants a package defines when it is imported.
It does this by parsing the package's export information.

- Evan