public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "seurer at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/111427] New: [14 regression] gfortran.dg/vect/pr60510.f fails after r14-3999-g3c834d85f2ec42 Date: Fri, 15 Sep 2023 20:17:27 +0000 [thread overview] Message-ID: <bug-111427-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111427 Bug ID: 111427 Summary: [14 regression] gfortran.dg/vect/pr60510.f fails after r14-3999-g3c834d85f2ec42 Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: other Assignee: unassigned at gcc dot gnu.org Reporter: seurer at gcc dot gnu.org Target Milestone: --- g:3c834d85f2ec42c60995c2b678196a06cb744959, r14-3999-g3c834d85f2ec42 make -k check-gcc RUNTESTFLAGS="--target_board=unix'{-m32,-m64}' vect.exp=gfortran.dg/vect/pr60510.f" spawn [open ...] STOP 1 FAIL: gfortran.dg/vect/pr60510.f -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions execution test commit 3c834d85f2ec42c60995c2b678196a06cb744959 Author: Vladimir N. Makarov <vmakarov@redhat.com> Date: Thu Sep 14 10:26:48 2023 -0400 [RA]: Improve cost calculation of pseudos with equivalences Looks like this actually only happens with -m32.
next reply other threads:[~2023-09-15 20:17 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-15 20:17 seurer at gcc dot gnu.org [this message] 2023-09-17 19:30 ` [Bug middle-end/111427] " pinskia at gcc dot gnu.org 2023-09-22 19:15 ` vmakarov at gcc dot gnu.org 2023-09-26 6:13 ` linkw at gcc dot gnu.org 2023-09-29 19:59 ` [Bug testsuite/111427] " vmakarov at gcc dot gnu.org 2023-10-12 5:06 ` cvs-commit at gcc dot gnu.org 2023-10-12 5:12 ` linkw 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-111427-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: linkBe 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).