Re: devel/boost syscall(2) removal

[Theo de Raadt]

On amd64, this makes no sense because we don't use stack protector.
It is retguard.   So something smells, it is like their handwritten
context switcher wasn't handling the full context before.  But that
might only matter if it unrolls via two seperate methods, or if a
new function above has become protected which was not protected before.
The description in the upstream work is pretty lacking.