In mcs/build/platforms/win32.make
Can we change this from:
EXTERNAL_MCS = csc
to the following:
EXTERNAL_MCS = mcs
csc does not work with building Mono on Windows anymore. You get
internal compiler errors. We should just use mcs to build from now on...
I can compile mono/mcs from
From: Jeyasankar Kottalam
How should I implement malloc and free on CLI? I've come up with a couple
of
ideas, but none of them seem particularly good to me:
As far as I know malloc and free are C runtime library functions not
intrinsic functions. I think they should not be implemented at
From: Jeyasankar Kottalam
As far as I know malloc and free are C runtime library functions not
intrinsic functions. I think they should not be implemented at compiler
level. These functions are allocating memory from a heap.
Correct, but I am also writing a partial libc for a couple of
From: Jeyasankar Kottalam
Yes, I agree. However, I still need a mechanism to implement a heap. Even
if
porting an existing libc, that libc will need *some* mechanism to get
memory
from the runtime. What is the recommended way of doing that?
I think to get te better berformance you should
On Sat, 2005-07-16 at 12:36 -0700, Jeyasankar Kottalam wrote:
Hello,
I'm the student writing GCC-CIL for Mono as part of Google's Summer of Code.
How should I implement malloc and free on CLI? I've come up with a couple of
ideas, but none of them seem particularly good to me:
- P/Invoke
Hello,
How should I implement malloc and free on CLI? I've come up with a couple of
ideas, but none of them seem particularly good to me:
- P/Invoke to native malloc and free
Problem: The binary becomes tied to the details of the underlying platform
to
pull in a malloc from the
Hello,
Correct, but I am also writing a partial libc for a couple of reasons:
I'd like to be able to test real world applications, and it is also
part of the acceptance criteria that I demonstrate a real world C
application under Mono.
Well, what I had in mind to demostrate a real C
