search for: 1003041

...the programs 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|...

Currently, the MachO and ELF Writers and MachineCodeEmitters are hard-coded into LLVMTargetMachine and llc. In other words, the 'object file generation' capabilities of the Common Code Generator are not generic. LLVMTargetMachine::addPassesToEmitFile explicitly checks whether the derived backend TargetMachine implements one of getMachOWriterInfo or getELFWriterInfo, and returns a

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