> >> > >> Hi Jan, > >> > >> https://gcc.gnu.org/ml/gcc-patches/2018-01/msg02233.html > >> > >> Is OK for trunk? > > > > I see that using register makes the problem go away and pushing address to > > stack > > seemed bit odd anyway. However how does this work on other types of thunk? > > Kernel only uses -mindirect-branch=thunk-extern. I am working on a proposal > to use -mindirect-branch=thunk-extern in user space to support CET in a single > binary. So at the end of the day, only > -mindirect-branch=thunk-extern will be used.
OK, so it is about the fact that we do not really want to support all -mindirect-branch options in the future? If we don't want to support the correctly, I wonder why we are including them at all. Shall we at least output warning/sorry when user tries other thunk type with stack unwinding enabled? (does Kernel use it?) Honza > > > -- > H.J.
