search for: gokta

-krasin@ On Fri, Jun 16, 2017 at 11:05 AM, Kostya Serebryany <kcc at google.com> wrote: > > > On Thu, Jun 15, 2017 at 10:39 PM, Enes Göktaş <enes.goktas at gmail.com> > wrote: > >> Hi Kostya, >> >> Please find attached the minimized motivation test. >> I hope it is minimized enough. If not please let me know so I can try to >> make it more minimal. >> Were you expecting something like this? >> &gt...

...issues likes this > w/o having a minimized motivation test. > Could you please provide such a test with one of the patches? > (And in general, please try to provide tests with any patch) > > Thanks! > > --kcc > > > On Thu, Jun 15, 2017 at 5:08 AM, Enes Göktaş <enes.goktas at gmail.com> > wrote: > >> Hi, >> >> I would like to propose extending the Control-Flow Integrity (CFI) >> mechanism in LLVM/Clang with a feature that allows users to explicitly link >> classes that have no inheritance link. Usually, if one class is used at...

...at 11:06 AM, Kostya Serebryany <kcc at google.com> wrote: > > -krasin@ > > > > On Fri, Jun 16, 2017 at 11:05 AM, Kostya Serebryany <kcc at google.com> wrote: > >> > >> > >> > >> On Thu, Jun 15, 2017 at 10:39 PM, Enes Göktaş <enes.goktas at gmail.com> > >> wrote: > >>> > >>> Hi Kostya, > >>> > >>> Please find attached the minimized motivation test. > >>> I hope it is minimized enough. If not please let me know so I can try to > >>> make it more min...

Hi, I would like to propose extending the Control-Flow Integrity (CFI) mechanism in LLVM/Clang with a feature that allows users to explicitly link classes that have no inheritance link. Usually, if one class is used at locations in code where this class is not expected, this will create a CFI error at runtime, assuming the application is built with CFI enabled. However, in cases where the user