public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/105558] simple 8-bit integer calculation fails with -O3 / march=core-avx2 on some gfortran 8/9/10 versions
Date: Wed, 11 May 2022 07:51:38 +0000	[thread overview]
Message-ID: <bug-105558-4-wWTBfCPkZA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105558-4@http.gcc.gnu.org/bugzilla/>

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Last reconfirmed|                            |2022-05-11
             Status|UNCONFIRMED                 |NEW
           Keywords|                            |needs-bisection
     Ever confirmed|0                           |1

--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
Can I ask you to see whether -O3 -fno-tree-vectorize avoids the issue and
whether -O3 -fno-vect-cost-model makes the issue appear in more versions?  It
could be that this is a resolved issue that awaits backporting of a fix (or
where backporting is too difficult).

I can confirm the -O3 -march=core-avx2 failure with GCC 10 and success with GCC
11.

  reply	other threads:[~2022-05-11  7:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-11  7:05 [Bug fortran/105558] New: simple 8-byte " federico.perini at gmail dot com
2022-05-11  7:51 ` rguenth at gcc dot gnu.org [this message]
2022-05-11  8:15 ` [Bug fortran/105558] simple 8-bit " federico.perini at gmail dot com
2022-05-11  8:17 ` federico.perini at gmail dot com
2022-07-15 10:45 ` marxin at gcc dot gnu.org
2022-10-27  4:57 ` [Bug tree-optimization/105558] " pinskia at gcc dot gnu.org
2022-10-27  4:58 ` [Bug tree-optimization/105558] [10 Regression] " pinskia at gcc dot gnu.org
2023-07-07 10:00 ` [Bug tree-optimization/105558] " rguenth at gcc dot gnu.org
2023-11-07  6:19 ` tkoenig 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-105558-4-wWTBfCPkZA@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).