I don't have any recent experience mixing and matching files from different
compilers on Windows.
However I do know that the Microsoft compilers, and by the looks of it the
Borland compiler, treat memcpy, memcmp, etc. as intrinisic unless you turn
those optimizations off. They also have #pragma intrinsic to force this
behaviour.
Cheers,
Martin Kenny.
Ramon van Handel wrote:
>Ulrich Weigand wrote:
>> [ B.t.w. for memset and memcpy specifically, we might rely on the
>> fact that those are gcc intrinsic routines, i.e. gcc creates
>> inline code instead of function calls for those anyway, unless
>> optimization is disabled. This would tie us to gcc, of course.
>
>That doesn't sound like a bad idea. Inline assembly &stuff is
>compiler-specific anyway. However, the big question is can we
>create drivers for other OSes in GCC ? I guess it should be
>possible to compile some files in one compiler and others in
>another one and then link them, but somebody with experience with
>an OS such as Windows will need to correct me here, if I'm wrong.
>
>-- Ramon