search for: 1003233

...rams as well as percentage changes in those sizes: .text section size in bytes: +--------------+---------+---------+---------+-------+ |Benchmark|Unpatched|Unpatched|Patched|MPX| ||Base|SafeStack|SafeStack|| +--------------+---------+---------+---------+-------+ |400.perlbench |884769|1003041|1003233|1131769| +--------------+---------+---------+---------+-------+ |401.bzip2|79393|175297|175489|235577 | +--------------+---------+---------+---------+-------+ |403.gcc|2420209|2545041|2545233|2727913| +--------------+---------+---------+---------+-------+ |429.mcf|10977|105345|105537|155705 |...

Rodrigo, On Mar 20, 2009, at 8:41 AM, Rodrigo Dominguez wrote: > Congratulations to LLVM for getting accepted to GSoC 2009! > > I am a PhD candidate interested in participating this year. I have > been > working on dynamic compilation (binary translation or BT) for > multicore > architectures for a couple of years. I am familiar with the > internals of > several

Hi, I previously posted about using 32-bit X86 segmentation to harden SafeStack: http://lists.llvm.org/pipermail/llvm-dev/2016-May/100346.html That involves lowering the limits of the DS and ES segments that are used for ordinary data accesses while leaving the limit for SS, the stack segment, set to its maximum value. The safe stacks were clustered above the limits of DS and ES. Thus, by