[gambit-list] calling scheme from C
cristi at ot.onrc.ro
Mon Jun 15 03:50:23 EDT 2009
Here are some thoughts:
On Sun, 14 Jun 2009 17:29:36 +0300, Marc Feeley <feeley at iro.umontreal.ca>
> Thanks for the suggestion. The problem is that there are so many
> different ways that the C code generated by gsc can be used (creating
> a .o file, creating an executable, creating a plugin, etc). Depending
> on the case you may want some unusual C compiler options, like
> selecting the calling convention, position independent code,
> profiling, etc.
Regardless of the diversity of use, .o files will be generated.
The diversity consist in the content of the .o files and in their linking.
The content is influenced by flags:
- language dependent options
- machine dependent options
- translation step dependent options
- warning and debugging options
- optimization options
The options can be:
There are two kind of code uses:
The .o files are linked into modules:
The calls can be inter/intra modules.
It seems that the objective is geting the linking and the calling right.
Maybe a matrimonial agency is required :-)
> So it doesn't seem like the right solution to package all of these
> decisions in a single script.
> What is the right abstraction?
Scheme code and/or makefiles ?
________ Information from NOD32 ________
This message was checked by NOD32 Antivirus System for Linux Mail Servers.
part000.txt - is OK
More information about the Gambit-list