This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author meador.inge
Recipients ezberch, meador.inge, ned.deily, ronaldoussoren, vstinner
Date 2012-02-09.03:24:16
SpamBayes Score 3.30473e-11
Marked as misclassified No
Message-id <>
> So perhaps as a temporary workaround, we could tweak to set
> -O0 for building ctypes with clang?

That would make the tests pass, but it still won't fix the fundamental 
issue.  clang and GCC have a difference in opinion as to when function
parameters and return values should be sign extended.  libffi follows
the GCC model.

I am talking to the LLVM folks right now to see why things are 
implemented this way.  Whether LLVM or libffi should be fixed depends
on the outcome of that discussion.

Due to this ABI difference compiling _ctypes with -O0 for clang will not
fix the problem because any ctypes code that interacts with C code that
was compiled by clang with optimizations has the potential to break just
like our test cases.
Date User Action Args
2012-02-09 03:24:19meador.ingesetrecipients: + meador.inge, ronaldoussoren, vstinner, ned.deily, ezberch
2012-02-09 03:24:19meador.ingesetmessageid: <>
2012-02-09 03:24:18meador.ingelinkissue13370 messages
2012-02-09 03:24:16meador.ingecreate