public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "guojiufu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/106928] New: 500.perlbench_r fail(VE) since r13-1933 Date: Tue, 13 Sep 2022 13:56:22 +0000 [thread overview] Message-ID: <bug-106928-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106928 Bug ID: 106928 Summary: 500.perlbench_r fail(VE) since r13-1933 Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: middle-end Assignee: unassigned at gcc dot gnu.org Reporter: guojiufu at gcc dot gnu.org Target Milestone: --- With the latest trunk, the 500.perlbench_r (-Ofast) from spec2017 encounter VE on power9 and power10 on no matter with or without -fno-unsafe-math-optimizations. With bisect, the commit may be r13-1933 (Implement basic range operators to enable floating point VRP). One compiling command: gcc -std=c99 -m64 -c -o reentr.o -DSPEC -DNDEBUG -DPERL_CORE -I. -Idist/IO -Icpan/Time-HiRes -Icpan/HTML-Parser -Iext/re -Ispecrand -DDOUBLE_SLASHES_SPECIAL=0 -DSPEC_AUTO_SUPPRESS_OPENMP -D_LARGE_FILES -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -Ofast -fno-unsafe-math-optimizations -DSPEC_LINUX_PPC_LE -fno-strict-aliasing -fgnu89-inline -DSPEC_LP64 reentr.c In configure, I use: default=base: # flags for all base OPTIMIZE = -Ofast -fno-unsafe-math-optimizations FOPTIMIZE = -std=legacy intrate,intspeed=base: # flags for integer base EXTRA_COPTIMIZE = -fno-strict-aliasing -fgnu89-inline Log message: *** Miscompare of diffmail.4.800.10.17.19.300.out; for details see benchspec/CPU/500.perlbench_r/run/run_base_refrate_base_64.0000/diffmail.4.800.10.17.19.300.out.mis Error: 1x500.perlbench_r
next reply other threads:[~2022-09-13 13:56 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-13 13:56 guojiufu at gcc dot gnu.org [this message] 2022-09-13 14:08 ` [Bug middle-end/106928] " guojiufu at gcc dot gnu.org 2022-09-13 14:19 ` marxin at gcc dot gnu.org 2022-09-14 2:10 ` guojiufu at gcc dot gnu.org 2024-05-02 21:31 ` pinskia 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-106928-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).