public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "acoplan at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/113539] New: [14 Regression] perlbench miscompiled on aarch64 since r14-8223-g1c1853a70f
Date: Mon, 22 Jan 2024 10:37:16 +0000	[thread overview]
Message-ID: <bug-113539-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 113539
           Summary: [14 Regression] perlbench miscompiled on aarch64 since
                    r14-8223-g1c1853a70f
           Product: gcc
           Version: 14.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: tree-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: acoplan at gcc dot gnu.org
  Target Milestone: ---

I'm seeing miscompares of perlbench (both from SPEC CPU 2006 and SPEC CPU 2017)
on aarch64 with recent trunk changes, a bisect pointed to
r14-8223-g1c1853a70f9422169190e65e568dcccbce02d95c :

commit 1c1853a70f9422169190e65e568dcccbce02d95c
Author: Richard Biener <rguenther@suse.de>
Date:   Thu Jan 18 10:22:34 2024

    Fix memory leak in vect_analyze_loop_form

The miscompares are with the checkspam.pl workload, I see:

*** Miscompare of checkspam.2500.5.25.11.150.1.1.1.1.out

I've seen this with:

-flto=auto -fomit-frame-pointer -O3 -fno-strict-aliasing

and various -mcpu options (at least -mcpu=cortex-a72 and -mcpu=neoverse-v1).

             reply	other threads:[~2024-01-22 10:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-22 10:37 acoplan at gcc dot gnu.org [this message]
2024-01-22 10:49 ` [Bug tree-optimization/113539] " tnfchris at gcc dot gnu.org
2024-01-22 10:54 ` rguenth at gcc dot gnu.org
2024-01-22 10:56 ` tnfchris at gcc dot gnu.org
2024-01-22 11:03 ` acoplan at gcc dot gnu.org
2024-01-24  5:04 ` liuhongt at gcc dot gnu.org
2024-01-24 14:08 ` fkastl at suse dot cz
2024-01-24 14:10 ` fkastl at suse dot cz
2024-01-26 13:29 ` rguenth at gcc dot gnu.org
2024-01-26 14:09 ` fkastl at suse dot cz
2024-02-05 20:56 ` jakub at gcc dot gnu.org
2024-02-05 21:12 ` tnfchris 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-113539-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).