https://bugzilla.redhat.com/show_bug.cgi?id=2008090
--- Comment #11 from Andreas Krebbel <krebbel1(a)de.ibm.com> ---
(In reply to Dan Horák from comment #10)
one last thing - won't the -mzvector cause any troubles with the
distro-wide
-march/-mtune settings?
gcc -O3 -mzvector -Wall -std=gnu99 -fstack-protector-all -O2 -flto=auto
-ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall
-Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS
-specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong
-specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -march=zEC12 -mtune=z13
-fasynchronous-unwind-tables -fstack-clash-protection "-Wall" -fPIC -c
zdnn_init.c -o obj/zdnn_init.o
-mzvector does not influence code generation. It only enables language
extensions which are used by the zDNN library. With that option the "vector"
keyword is available which allows to define vector data types more easily. For
code not using these extensions it doesn't make a difference.
--
You are receiving this mail because:
You are always notified about changes to this product and component
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2008090