public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "thiago at kde dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/102166] [i386] AMX intrinsics and macros not defined in C++
Date: Thu, 02 Sep 2021 03:31:09 +0000 [thread overview]
Message-ID: <bug-102166-4-14r3UgJdwH@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102166-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102166
--- Comment #5 from Thiago Macieira <thiago at kde dot org> ---
(In reply to Hongtao.liu from comment #4)
> Because _tile_loadd is implemented as embedded assembly plus macros, if
> __AMX_TILE__ is removed, no error will be reported if the user does not use
> the -mamx option, So this macro is added here, but obviously this is not
> convenient for target_attribute. I think we'd better remove __AMX_TILE__,
> (not sure why c doesn't report the error).
I suggest doing as Clang did and make it an intrinsic.
next prev parent reply other threads:[~2021-09-02 3:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-01 22:27 [Bug target/102166] New: " thiago at kde dot org
2021-09-01 22:33 ` [Bug target/102166] " thiago at kde dot org
2021-09-01 22:45 ` thiago at kde dot org
2021-09-01 23:10 ` thiago at kde dot org
2021-09-02 1:35 ` crazylht at gmail dot com
2021-09-02 3:31 ` thiago at kde dot org [this message]
2021-09-02 3:54 ` thiago at kde dot org
2021-09-02 3:55 ` crazylht at gmail dot com
2021-09-02 4:00 ` crazylht at gmail dot com
2021-09-02 4:02 ` thiago at kde dot org
2021-09-02 4:49 ` crazylht at gmail dot com
2021-09-03 5:04 ` cvs-commit at gcc dot gnu.org
2021-09-03 5:06 ` cvs-commit 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-102166-4-14r3UgJdwH@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).