"Joseph S. Myers" writes:
> On Wed, 20 Nov 2013, Gaius Mulley wrote:
>
>> Thanks for all the comments regarding the set of patches. Perhaps the
>> statement "use its own linker" is misleading. When gm2 is asked to link
>> a module hello.mod it does the following:
>
> Thanks for the explanation.
On Wed, 20 Nov 2013, Gaius Mulley wrote:
> Thanks for all the comments regarding the set of patches. Perhaps the
> statement "use its own linker" is misleading. When gm2 is asked to link
> a module hello.mod it does the following:
Thanks for the explanation. I think this is sufficiently compli
"Joseph S. Myers" writes:
> On Wed, 20 Nov 2013, Gaius Mulley wrote:
>
>> As an example of why this is required - the Modula-2 compiler driver
>> uses its own linker. So it needs to both suppress the default linker
>> and also get a list of objects generated from a compiler invocation.
>
> I thi
On Wed, 20 Nov 2013, Gaius Mulley wrote:
> As an example of why this is required - the Modula-2 compiler driver
> uses its own linker. So it needs to both suppress the default linker
> and also get a list of objects generated from a compiler invocation.
I think you'll need to explain that a lot
Here are some proposed patches which allow front end compiler drivers to
add command line arguments, add their own spec functions and also to
disable the default linker.
It does mean that each language front end compiler driver will need an
additional stub function, which at the very least does
