public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "crazylht at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/107304] internal compiler error: in convert_move, at expr.cc:220 with -march=tigerlake
Date: Tue, 18 Oct 2022 23:37:52 +0000	[thread overview]
Message-ID: <bug-107304-4-OeixRgTQUl@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107304-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107304

--- Comment #6 from Hongtao.liu <crazylht at gmail dot com> ---
(In reply to Hongtao.liu from comment #5)
> (In reply to H.J. Lu from comment #4)
> > Since the default is -march=tigerlake, it enables AVX512 in the middle end.
> > When "arch=alderlake" disables AVX512, we fails to expand AVX512 to
> > non-AVX512
> > ISAs. It means that target_clones can't be more restrictive than the
> > default. We
> > should provide better diagnostics.
> 
> Is there any place checking ISA difference for target_clones?

ix86_valid_target_attribute_inner_p?

  parent reply	other threads:[~2022-10-18 23:37 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-18 16:03 [Bug middle-end/107304] New: " colin.king at intel dot com
2022-10-18 16:06 ` [Bug middle-end/107304] " colin.king at intel dot com
2022-10-18 16:16 ` colin.king at intel dot com
2022-10-18 16:37 ` colin.king at intel dot com
2022-10-18 18:30 ` [Bug target/107304] " hjl.tools at gmail dot com
2022-10-18 23:21 ` crazylht at gmail dot com
2022-10-18 23:37 ` crazylht at gmail dot com [this message]
2022-10-18 23:44 ` hjl.tools at gmail dot com
2022-10-19  1:27 ` crazylht at gmail dot com
2022-10-19  2:41 ` hjl.tools at gmail dot com
2022-10-19  3:00 ` wwwhhhyyy333 at gmail dot com
2022-10-19  3:03 ` crazylht at gmail dot com
2022-10-19  3:11 ` hjl.tools at gmail dot com
2022-10-19  3:20 ` hjl.tools at gmail dot com
2022-10-19  3:25 ` crazylht at gmail dot com
2022-10-19  3:31 ` hjl.tools at gmail dot com
2022-10-19  3:55 ` crazylht at gmail dot com
2022-10-19 18:03 ` hjl.tools at gmail dot com
2022-10-19 18:37 ` hjl.tools at gmail dot com
2022-10-19 19:49 ` hjl.tools at gmail dot com
2022-10-19 20:07 ` hjl.tools at gmail dot com
2022-10-19 20:12 ` hjl.tools at gmail dot com
2022-10-25 17:31 ` cvs-commit at gcc dot gnu.org
2022-10-25 17:34 ` hjl.tools at gmail dot com
2022-11-08 21:22 ` cvs-commit at gcc dot gnu.org
2022-11-08 21:56 ` cvs-commit at gcc dot gnu.org
2022-11-08 22:25 ` cvs-commit at gcc dot gnu.org
2022-11-08 22:56 ` hjl.tools at gmail dot com
2022-11-11 11:27 ` aoliva at gcc dot gnu.org
2022-11-23 13:34 ` ro at gcc dot gnu.org
2022-11-30  8:00 ` cvs-commit at gcc dot gnu.org
2022-12-19 22:52 ` pinskia 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-107304-4-OeixRgTQUl@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).