[M3devel] link failure on NT386

[Tony Hosking]

Why can't we just have a run-time hook that resolves differently on different targets?
Take a look at m3front/src/misc/Runtyme and m3core/src/runtime/RTHooks.

On Jan 31, 2011, at 7:53 PM, Jay K wrote:

> Oops, I was just wondering to self if I had fixed that.
> I can get to it fairly soon.
> We "just" have to translate m3_alloca to _chkstk..and fiddle with the calling
> convention (which imho is a good reason to
> make it a separate m3cg call...)
> (The input parameter is in eax, and the output is in esp.)
> (Tony, you really don't want a separate m3cg call?)
>  
>  
>  - Jay
>  
> From: rcolebur at SCIRES.COM
> To: m3devel at elegosoft.com
> Date: Mon, 31 Jan 2011 19:48:21 -0500
> Subject: [M3devel] link failure on NT386
> 
> Jay:  I note the HEAD branch is still broken for builds on NT386 due to the linker problem with unresolved symbol we talked about earlier.
> Do you have a plan to fix?
> Anything I can do to help?
> --Randy Coleburn

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20110131/9aec17a1/attachment-0002.html>