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 tree-optimization/100457] New: [meta bug] Enabling O2 vectorization in GCC 12
Date: Thu, 06 May 2021 14:49:34 +0000	[thread overview]
Message-ID: <bug-100457-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 100457
           Summary: [meta bug] Enabling O2 vectorization in GCC 12
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: tree-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: crazylht at gmail dot com
                CC: hjl.tools at gmail dot com
  Target Milestone: ---

This metabug is used to track all the O2 vectorization issues.

We're trying to enable vectorization in O2 for GCC12. To do that, we need to
make  there's no regression comparing -O2 -ftree-vectorize
-fvect-cost-model=very-cheap to plain -O2, or those regressions are acceptable.

             reply	other threads:[~2021-05-06 14:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-06 14:49 crazylht at gmail dot com [this message]
2021-07-19  4:22 ` [Bug tree-optimization/100457] " pinskia at gcc dot gnu.org
2021-07-28  2:49 ` crazylht at gmail dot com
2021-08-19  2:32 ` crazylht at gmail dot com
2022-02-22  8:00 ` rguenth at gcc dot gnu.org
2022-03-08 15:06 ` rguenth at gcc dot gnu.org
2022-04-05  6:24 ` rguenth at gcc dot gnu.org
2023-08-08 22:02 ` [Bug tree-optimization/100457] [meta-bug] Bugs relating to the enabling of vectorization at -O2 in GCC 12+ egallager at gcc dot gnu.org
2023-11-02 13:20 ` rguenth 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-100457-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).