On 01/16/2016 04:50 PM, Phil Thompson wrote:
On 16 Jan 2016, at 7:36 pm, ken <[email protected]> wrote:
Looking at the Makefile (resulting from "qmake-qt4 qscintilla.pro"), I found:
CFLAGS = -pipe -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2
-fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64
-mtune=generic -O2 -D_REENTRANT -w -fPIC $(DEFINES)
CXXFLAGS = -pipe -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2
-fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64
-mtune=generic -O2 -D_REENTRANT -w -fPIC $(DEFINES)
(That's just two lines, screw-wrapped by my emailer.) Since I've got a better than a generic cpu, an
i7-6700HQ, and I'd like to take advantage of the extra niceties of the more powerful cpu. I'm not compiling
this for distribution, so is there any reason not to change "-mtune=generic" in the two lines above
to "-mtune=native"? (The latter is what "man gcc" actually recommends.)
Anyone have insight into this first issue? I don't see how changing the
target cpu for compiling could possibly muck up the outcome. But I'm
not at all familiar with QScintilla.
_______________________________________________
QScintilla mailing list
[email protected]
https://www.riverbankcomputing.com/mailman/listinfo/qscintilla
