public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.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: Fri, 03 Sep 2021 05:06:04 +0000 [thread overview] Message-ID: <bug-102166-4-5bI9bGiBLr@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 #12 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-11 branch has been updated by hongtao Liu <liuhongt@gcc.gnu.org>: https://gcc.gnu.org/g:259945a0a4880b66f93f71eebe70f78c91e02d5e commit r11-8953-g259945a0a4880b66f93f71eebe70f78c91e02d5e Author: liuhongt <hongtao.liu@intel.com> Date: Thu Sep 2 12:49:46 2021 +0800 Remove macro check for __AMX_BF16/INT8/TILE__ in header file. gcc/ChangeLog: PR target/102166 * config/i386/amxbf16intrin.h : Remove macro check for __AMX_BF16__. * config/i386/amxint8intrin.h : Remove macro check for __AMX_INT8__. * config/i386/amxtileintrin.h : Remove macro check for __AMX_TILE__. gcc/testsuite/ChangeLog: PR target/102166 * g++.target/i386/pr102166.C: New test.
prev parent reply other threads:[~2021-09-03 5:06 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 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 [this message]
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-5bI9bGiBLr@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).