Displaying 3 results from an estimated 3 matches for "typeruntim".
Did you mean:
typeruntime
2011 Aug 21
0
[LLVMdev] Clang + SAFECode Release Announcement
John,
The release source code (sc-main.tar) won't compile cleanly under
Debian6-i386 (gcc/g++: 4.4.5).
The compiler back trace is attached.
Please fix it/them and repost.
Or, 64b system is a requirement?
Thank you
Chuck
llvm[4]: Compiling TypeRuntime.cpp for Release+Asserts build (PIC)
cc1plus: warnings being treated as errors
/home/czhao/ResearchTools/LLVM/SubProjects/Safecode/llvm/projects/poolalloc/runtime/DynamicTypeChecks/TypeRuntime.cpp:52:
error: integer constant is too large for ‘long’ type
/home/czhao/ResearchTools/LLVM/SubProjec...
2011 Aug 21
1
[LLVMdev] Clang + SAFECode Release Announcement
...t;
> The release source code (sc-main.tar) won't compile cleanly under
> Debian6-i386 (gcc/g++: 4.4.5).
> The compiler back trace is attached.
> Please fix it/them and repost.
>
> Or, 64b system is a requirement?
>
> Thank you
>
> Chuck
>
> llvm[4]: Compiling TypeRuntime.cpp for Release+Asserts build (PIC)
> cc1plus: warnings being treated as errors
> /home/czhao/ResearchTools/LLVM/SubProjects/Safecode/llvm/projects/poolalloc/runtime/DynamicTypeChecks/TypeRuntime.cpp:52:
> error: integer constant is too large for ‘long’ type
> /home/czhao/ResearchT...
2011 Aug 18
5
[LLVMdev] Clang + SAFECode Release Announcement
Dear All,
We have a new release of Clang with SAFECode technology for detecting
memory safety errors. Memory safety checking (SAFECode for short) can be
turned on with a single command line switch to clang/clang++. The
SAFECode techniques do not change the behavior of the clang/clang++
compilers in any way when the switch is turned off, so this can be used
as a drop-in replacement for