public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tuliom at ascii dot art.br" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/101865] _ARCH_PWR8 is not defined when using -mcpu=power8 Date: Thu, 26 Aug 2021 13:56:31 +0000 [thread overview] Message-ID: <bug-101865-4-92jhySrj2n@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101865-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101865 --- Comment #12 from Tulio Magno Quites Machado Filho <tuliom at ascii dot art.br> --- There is a chance, that my previous comment is wrong with regards the generation of VSX instructions for Power8. I don't know what the second command means: $ gcc-11 -mcpu=power10 -dM -E - < /dev/null | grep -E 'VECTOR|VSX|ALTIVEC' #define __VSX__ 1 #define __ALTIVEC__ 1 #define __POWER9_VECTOR__ 1 #define __APPLE_ALTIVEC__ 1 #define __POWER8_VECTOR__ 1 $ gcc-11 -mcpu=power10 -mno-power8-vector -dM -E - < /dev/null | grep -E 'VECTOR|VSX|ALTIVEC' #define __VSX__ 1 #define __ALTIVEC__ 1 #define __APPLE_ALTIVEC__ 1
next prev parent reply other threads:[~2021-08-26 13:56 UTC|newest] Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-11 19:41 [Bug target/101865] New: " tuliom at ascii dot art.br 2021-08-11 20:11 ` [Bug target/101865] " segher at gcc dot gnu.org 2021-08-18 14:12 ` wschmidt at gcc dot gnu.org 2021-08-18 15:39 ` segher at gcc dot gnu.org 2021-08-24 7:39 ` guihaoc at gcc dot gnu.org 2021-08-24 16:46 ` segher at gcc dot gnu.org 2021-08-25 2:34 ` guihaoc at gcc dot gnu.org 2021-08-25 14:00 ` tuliom at ascii dot art.br 2021-08-25 14:39 ` segher at gcc dot gnu.org 2021-08-26 0:52 ` guihaoc at gcc dot gnu.org 2021-08-26 13:21 ` tuliom at ascii dot art.br 2021-08-26 13:46 ` wschmidt at gcc dot gnu.org 2021-08-26 13:56 ` tuliom at ascii dot art.br [this message] 2021-08-31 16:09 ` bergner at gcc dot gnu.org 2021-08-31 16:26 ` wschmidt at linux dot ibm.com 2021-08-31 16:37 ` segher at gcc dot gnu.org 2021-08-31 16:42 ` segher at gcc dot gnu.org 2024-04-03 22:22 ` bergner at gcc dot gnu.org 2024-04-10 2:41 ` cvs-commit at gcc dot gnu.org 2024-04-11 22:38 ` bergner at gcc dot gnu.org 2024-04-12 20:27 ` cvs-commit at gcc dot gnu.org 2024-04-12 20:28 ` bergner at gcc dot gnu.org 2024-05-02 3:38 ` cvs-commit at gcc dot gnu.org 2024-05-02 3:38 ` cvs-commit at gcc dot gnu.org 2024-05-02 13:20 ` cvs-commit at gcc dot gnu.org 2024-05-02 13:20 ` cvs-commit at gcc dot gnu.org 2024-05-02 23:09 ` cvs-commit at gcc dot gnu.org 2024-05-02 23:09 ` cvs-commit at gcc dot gnu.org 2024-05-02 23:10 ` bergner at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-101865-4-92jhySrj2n@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).