public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Hongyu Wang <hongyuw@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r12-5885] x86: Update -mtune=tremont
Date: Fri, 10 Dec 2021 01:40:47 +0000 (GMT)	[thread overview]
Message-ID: <20211210014047.2B7063858022@sourceware.org> (raw)

https://gcc.gnu.org/g:35a4fe8091896529a19a7c2c2a32e69f3b5efddb

commit r12-5885-g35a4fe8091896529a19a7c2c2a32e69f3b5efddb
Author: Cui,Lili <lili.cui@intel.com>
Date:   Fri Nov 26 11:16:43 2021 +0800

    x86: Update -mtune=tremont
    
    Silvermont has a special handle in add_stmt_cost function, because it has in
    order SIMD pipeline. But for Tremont, its SIMD pipeline is out of order,
    remove Tremont from this special handle.
    
    gcc/ChangeLog
    
            * config/i386/i386.c (ix86_vector_costs::add_stmt_cost): Remove Tremont.

Diff:
---
 gcc/config/i386/i386.c | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/gcc/config/i386/i386.c b/gcc/config/i386/i386.c
index f1e41fd55f9..9f4ed34ffd5 100644
--- a/gcc/config/i386/i386.c
+++ b/gcc/config/i386/i386.c
@@ -23144,8 +23144,7 @@ ix86_vector_costs::add_stmt_cost (int count, vect_cost_for_stmt kind,
      for Silvermont as it has out of order integer pipeline and can execute
      2 scalar instruction per tick, but has in order SIMD pipeline.  */
   if ((TARGET_CPU_P (SILVERMONT) || TARGET_CPU_P (GOLDMONT)
-       || TARGET_CPU_P (GOLDMONT_PLUS) || TARGET_CPU_P (TREMONT)
-       || TARGET_CPU_P (INTEL))
+       || TARGET_CPU_P (GOLDMONT_PLUS) || TARGET_CPU_P (INTEL))
       && stmt_info && stmt_info->stmt)
     {
       tree lhs_op = gimple_get_lhs (stmt_info->stmt);


                 reply	other threads:[~2021-12-10  1:40 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20211210014047.2B7063858022@sourceware.org \
    --to=hongyuw@gcc.gnu.org \
    --cc=gcc-cvs@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).