If you're asking opinions I would rather the default is set
-mms-bitfields if compiling on Windows, and -no-mms-bitfields (?) on
Linux. That way there is no breaking change for some Windows users.
Then the only impact would be to non MSVC users on Windows who are
wanting to share
Hello
Is this really a problem for tcc? An old version of VC produces the
same sizes as tcc. The spec seems to say (not sure I'm reading this
right, first time I've read the spec)
"An implementation may allocate any addressable storage unit large
enough to hold a bitfield.snip.
Hi Philip
The process I use is as follows (simplified from actual, error checking
removed etc)
// set we want code in memory
tcc_set_output_type(state, TCC_OUTPUT_MEMORY);
// compile the program
tcc_compile_string(state, Program);
// Add symbols for functions in current program, if any
Hello
If I use the function tcc_set_error_func() the function that gets
called has a text string describing the error. Is there any
standardisation of this message line - sometimes it seems to be
:19: xyz Othertimes it has more prefixes to the message.
What I am really after is the
