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] New: _ARCH_PWR8 is not defined when using -mcpu=power8
Date: Wed, 11 Aug 2021 19:41:03 +0000 [thread overview]
Message-ID: <bug-101865-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101865
Bug ID: 101865
Summary: _ARCH_PWR8 is not defined when using -mcpu=power8
Product: gcc
Version: 11.1.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: tuliom at ascii dot art.br
Target Milestone: ---
When using -mcpu=power8, I expected that _ARCH_PWR8 would be defined, however
it isn't defined when used together with -mno-altivec -mno-vsx, e.g.
$ gcc-11 -mcpu=power8 -mno-altivec -mno-vsx -dM -E - < /dev/null | grep PWR
#define _ARCH_PWR5 1
#define _ARCH_PWR6 1
#define _ARCH_PWR7 1
#define _ARCH_PWR5X 1
#define _ARCH_PWR4 1
next reply other threads:[~2021-08-11 19:41 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-11 19:41 tuliom at ascii dot art.br [this message]
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
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@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: link
Be 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).