search for: checker2

...he two ODR tables (no reuse for non-symbol ODR names to start with, as >> compression may be enough on its own). >> > > I developed a second prototype which uses hash/compression with no attempt > to reuse. It is available here: > https://github.com/pcc/llvm-project/tree/odr-checker2 > > For Chromium the object file size overhead was 536566007 bytes, or in > relative terms about 25%, or about 4% with debug info. I measured perf > overhead for unit_tests at about 6%, but after I moved the checker onto > another thread, the overhead disappeared into the noise. >...

...ames to >>>> start with, as compression may be enough on its own). >>>> >>> >>> I developed a second prototype which uses hash/compression with no >>> attempt to reuse. It is available here: >>> https://github.com/pcc/llvm-project/tree/odr-checker2 >>> >>> For Chromium the object file size overhead was 536566007 bytes, or in >>> relative terms about 25%, or about 4% with debug info. I measured perf >>> overhead for unit_tests at about 6%, but after I moved the checker onto >>> another thread, the o...

...compression may be enough on its own). >>>>>> >>>>> >>>>> I developed a second prototype which uses hash/compression with no >>>>> attempt to reuse. It is available here: >>>>> https://github.com/pcc/llvm-project/tree/odr-checker2 >>>>> >>>>> For Chromium the object file size overhead was 536566007 bytes, or in >>>>> relative terms about 25%, or about 4% with debug info. I measured perf >>>>> overhead for unit_tests at about 6%, but after I moved the checker onto &g...

On Wed, Jun 7, 2017 at 8:06 PM, Sean Silva <chisophugis at gmail.com> wrote: > > > On Wed, Jun 7, 2017 at 4:31 PM, Peter Collingbourne <peter at pcc.me.uk> > wrote: > >> On Wed, Jun 7, 2017 at 12:17 AM, Sean Silva <chisophugis at gmail.com> >> wrote: >> >>> Very nice and simple implementation! >>> >>> Do you have any

...gt;>>>>>>> >>>>>>> >>>>>>> I developed a second prototype which uses hash/compression with no >>>>>>> attempt to reuse. It is available here: >>>>>>> https://github.com/pcc/llvm-project/tree/odr-checker2 >>>>>>> >>>>>>> For Chromium the object file size overhead was 536566007 bytes, or >>>>>>> in relative terms about 25%, or about 4% with debug info. I measured perf >>>>>>> overhead for unit_tests at about 6%, but a...

...gt;>>>>>>>> >>>>>>>>> I developed a second prototype which uses hash/compression with no >>>>>>>>> attempt to reuse. It is available here: https://github.com/pcc/l >>>>>>>>> lvm-project/tree/odr-checker2 >>>>>>>>> >>>>>>>>> For Chromium the object file size overhead was 536566007 bytes, or >>>>>>>>> in relative terms about 25%, or about 4% with debug info. I measured perf >>>>>>>>> overhead f...

...>>>>>>>>> >>>>>>>>> I developed a second prototype which uses hash/compression with no >>>>>>>>> attempt to reuse. It is available here: >>>>>>>>> https://github.com/pcc/llvm-project/tree/odr-checker2 >>>>>>>>> >>>>>>>>> For Chromium the object file size overhead was 536566007 bytes, or >>>>>>>>> in relative terms about 25%, or about 4% with debug info. I measured perf >>>>>>>>> overhead f...

...>>> >>>>>>>>>>> I developed a second prototype which uses hash/compression with >>>>>>>>>>> no attempt to reuse. It is available here: >>>>>>>>>>> https://github.com/pcc/llvm-project/tree/odr-checker2 >>>>>>>>>>> >>>>>>>>>>> For Chromium the object file size overhead was 536566007 bytes, >>>>>>>>>>> or in relative terms about 25%, or about 4% with debug info. I measured >>>>>>>...

...;>>>>>>>>>> I developed a second prototype which uses hash/compression >>>>>>>>>>>>> with no attempt to reuse. It is available here: >>>>>>>>>>>>> https://github.com/pcc/llvm-project/tree/odr-checker2 >>>>>>>>>>>>> >>>>>>>>>>>>> For Chromium the object file size overhead was 536566007 >>>>>>>>>>>>> bytes, or in relative terms about 25%, or about 4% with debug info. I >>>&...