Skip to Content.
Sympa Menu

svadev - [svadev] Proposal: Change DebugRuntime Compilation Settings for Debug build

svadev AT lists.siebelschool.illinois.edu

Subject: Svadev mailing list

List archive

[svadev] Proposal: Change DebugRuntime Compilation Settings for Debug build


Chronological Thread 
  • From: Santosh Nagarakatte <santoshn AT cis.upenn.edu>
  • To: svadev AT cs.uiuc.edu
  • Subject: [svadev] Proposal: Change DebugRuntime Compilation Settings for Debug build
  • Date: Wed, 14 Dec 2011 03:05:53 -0500
  • List-archive: <http://lists.cs.uiuc.edu/pipermail/svadev>
  • List-id: <svadev.cs.uiuc.edu>

Hi all,

I noticed that SafeCode compiles the runtime in Debug mode when the
SafeCode compiler is compiled in Debug+Asserts mode.
However as the runtime is injected into the binary, this translates to
execution time overheads for any binary compiled in Debug mode.
This implies that to generate optimized code with SafeCode, we need to
compile the compiler in Release mode.

This can be very cumbersome especially when we want to test
performance of the application with optimizations when the compilation
of the application is done with optimizations and compiler is compiled
in debug+asserts mode.

For example SafeCode has 50X overhead for a simple test when the
program is compiled with O3 and the compiler is in compiled in debug
mode.

Santosh



--
Santosh G Nagarakatte,
PhD Student,
Computer and Information Science Department
University of Pennsylvania,
Philadelphia-19104
http://www.cis.upenn.edu/~santoshn




Archive powered by MHonArc 2.6.16.

Top of Page