with CXXFLAGS of initially -O2 -march=native, later reduced to
-march=native to keep the default -O3, I started to look at hardening
options to find out where the problems are, and if any cost is
worthwhile. And no,
-march=native is not necessarily a good idea, but in verbose builds it
tells me if my flags are being used.
Now I'm looking at the first of the cheap hardening options (on gcc) :
-D_FORTIFY_SOURCE=2 but b2 has a strong dislike of -D.
After looking around, it appears that this needs to be in a jam file,
possibly in a form like <define>\_FORTIFY\_SOURCE\=2 but I'm making no
progress on this. Also, I could not find any guide to whether the
underscores need to be escaped, I just started with those and found
that the = definitely needed to be escaped. I've created
using gcc : : : <compileflags>-march=native<compileflags>_FORTIFY_SOURCE\=2 ;
project user-config ;
(using gcc through to 2; is all on one line, gmail insists on breaking it up)
On Fri, 31 May 2019 at 11:44, Ken Moffat via Boost-build
<[hidden email]> wrote:
> Now I'm looking at the first of the cheap hardening options (on gcc) :
> -D_FORTIFY_SOURCE=2 but b2 has a strong dislike of -D.
showed the process works (all get added to the existing -O3). I've
spelled that out in the hope google can find it - unfortunately most
of my searching for b2 boost fortify came up with stuff about
vitamins. And I've made a note of where the manual is.
Unsubscribe & other changes: https://lists.boost.org/mailman/listinfo.cgi/boost-build