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/103088] New: [12 regression] 500.perlbench from spec 2017 fails since r12-4698 Date: Thu, 04 Nov 2021 20:45:57 +0000 [thread overview] Message-ID: <bug-103088-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103088 Bug ID: 103088 Summary: [12 regression] 500.perlbench from spec 2017 fails since r12-4698 Product: gcc Version: 12.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:f6d012338bf87f427b7420f2f309963c29fe33ba, r12-4698 commit f6d012338bf87f427b7420f2f309963c29fe33ba (HEAD) Author: Aldy Hernandez <aldyh@redhat.com> Date: Wed Oct 20 07:29:25 2021 +0200 Try to resolve paths in threader without looking further back. I am seeing a strange problem starting with this revision. The spec 2017 test case 500.perlbench is producing a few extraneous lines of output which is causing it to fail. seurer@muskie:~/gcc/cpu2017$ diff ./benchspec/CPU/500.perlbench_r/data/refrate/output/diffmail.4.800.10.17.19.300.out ./benchspec/CPU/500.perlbench_r/run/run_peak_refrate_none.0000/diffmail.4.800.10.17.19.300.out 3257a3258 > Minimum abstol: nan 3259a3261 > Minimum reltol: nan 3507a3510 > Minimum abstol: nan 3509a3513 > Minimum reltol: nan 3694a3699 > Minimum abstol: nan 3696a3702 > Minimum reltol: nan 3818a3825 > Minimum abstol: nan 3820a3828 > Minimum reltol: nan These extra lines come from here in the perl code: if ($opts->{'calctol'}) { push @errstats, 'Calculated tolerances:'; foreach my $type (qw(abstol reltol obiwan skiptol)) { if (exists($max->{$type}) && ($max->{$type} >= 0)) { push @errstats, sprintf "Maximum $type: %-10.5e", $max->{$type}; } if (exists($min->{$type}) && ($min->{$type} >= 0)) { push @errstats, sprintf "Minimum $type: %-10.5e", $min->{$type}; } if (exists($errcnt->{$type}) && ($errcnt->{$type} >= 0)) { push @errstats, "# of $type errors: ".$errcnt->{$type}; } if (exists($opts->{"skip$type"}) && ($opts->{"skip$type"} > 0)) { push @errstats, "# of skip$type unused: ".$opts->{"skip$type"}; } } } So it appears that either the results of the perl exists function changed or the values that are being checked did not exist before but do now.
next reply other threads:[~2021-11-04 20:45 UTC|newest] Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-04 20:45 seurer at gcc dot gnu.org [this message] 2021-11-05 7:25 ` [Bug tree-optimization/103088] " rguenth at gcc dot gnu.org 2021-11-05 11:26 ` marxin at gcc dot gnu.org 2021-11-05 13:35 ` rguenth at gcc dot gnu.org 2021-11-05 14:19 ` seurer at gcc dot gnu.org 2021-11-17 15:28 ` tnfchris at gcc dot gnu.org 2021-11-17 17:48 ` aldyh at gcc dot gnu.org 2021-11-17 17:53 ` tnfchris at gcc dot gnu.org 2021-11-17 18:58 ` seurer at gcc dot gnu.org 2021-11-18 16:35 ` aldyh at gcc dot gnu.org 2021-11-18 16:45 ` tnfchris at gcc dot gnu.org 2021-11-18 19:13 ` aldyh at gcc dot gnu.org 2021-11-19 7:06 ` rguenther at suse dot de 2021-11-19 8:10 ` tnfchris at gcc dot gnu.org 2021-11-19 8:14 ` rguenth at gcc dot gnu.org 2021-11-19 10:09 ` aldyh at gcc dot gnu.org 2021-11-19 11:40 ` marxin at gcc dot gnu.org 2021-11-19 11:47 ` aldyh at gcc dot gnu.org 2021-11-19 11:58 ` tnfchris at gcc dot gnu.org 2021-11-19 12:27 ` marxin at gcc dot gnu.org 2021-11-19 12:33 ` tnfchris at gcc dot gnu.org 2021-11-19 16:11 ` aldyh at gcc dot gnu.org 2021-11-19 16:14 ` aldyh at gcc dot gnu.org 2021-11-21 19:37 ` aldyh at gcc dot gnu.org 2021-11-22 7:37 ` rguenther at suse dot de 2021-11-23 7:38 ` tnfchris at gcc dot gnu.org 2021-11-29 16:35 ` segher at gcc dot gnu.org 2024-05-02 21:31 ` pinskia 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-103088-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).