public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/109087] [13 Regression] csmith: end of year runtime bug since r13-4839-geef81eefcdc2a581
Date: Fri, 10 Mar 2023 17:20:09 +0000	[thread overview]
Message-ID: <bug-109087-4-ubxjUMlIh2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109087-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #10 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to David Binderman from comment #9)
> (In reply to Richard Biener from comment #6)
> > Try -fno-tree-vectorize?
> 
> I tried that, and it made no difference at all.
> 
> I also tried dropping the -march= setting back to znver1 and
> that also made no difference.

The change added znver1/2/3 to X86_TUNE_AVX256_MOVE_BY_PIECES,
X86_TUNE_AVX256_STORE_BY_PIECES also so must be related to that ...

Most likely a latent bug too ...

you might get a similar failure on alderlake or core_avx2 too.

  parent reply	other threads:[~2023-03-10 17:20 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-10  8:23 [Bug c/109087] New: csmith: end of year runtime bug ? dcb314 at hotmail dot com
2023-03-10  8:47 ` [Bug c/109087] " dcb314 at hotmail dot com
2023-03-10 11:24 ` dcb314 at hotmail dot com
2023-03-10 11:52 ` dcb314 at hotmail dot com
2023-03-10 12:10 ` dcb314 at hotmail dot com
2023-03-10 12:47 ` dcb314 at hotmail dot com
2023-03-10 13:04 ` [Bug c/109087] [13 Regression] " rguenth at gcc dot gnu.org
2023-03-10 13:05 ` [Bug target/109087] " rguenth at gcc dot gnu.org
2023-03-10 15:16 ` marxin at gcc dot gnu.org
2023-03-10 17:02 ` [Bug target/109087] [13 Regression] csmith: end of year runtime bug since r13-4839-geef81eefcdc2a581 pinskia at gcc dot gnu.org
2023-03-10 17:09 ` dcb314 at hotmail dot com
2023-03-10 17:20 ` pinskia at gcc dot gnu.org [this message]
2023-03-13 18:19 ` jakub at gcc dot gnu.org
2023-03-13 18:43 ` jakub at gcc dot gnu.org
2023-03-14  8:04 ` rguenth at gcc dot gnu.org
2023-03-14  8:12 ` jakub at gcc dot gnu.org
2023-03-14  8:27 ` rguenther at suse dot de
2023-03-15  8:42 ` rguenth at gcc dot gnu.org
2023-03-15  8:47 ` jakub at gcc dot gnu.org
2023-03-31 14:59 ` jakub at gcc dot gnu.org
2023-03-31 15:07 ` [Bug target/109087] " jakub at gcc dot gnu.org
2023-04-26  6:58 ` rguenth at gcc dot gnu.org
2023-07-27  9:25 ` rguenth at gcc dot gnu.org
2024-05-16  9:04 ` [Bug target/109087] [13/14/15 Regression] " cvs-commit at gcc dot gnu.org
2024-05-16  9:10 ` 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-109087-4-ubxjUMlIh2@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).