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 tree-optimization/103088] [12 regression] 500.perlbench from spec 2017 fails since r12-4698 Date: Fri, 05 Nov 2021 14:19:28 +0000 [thread overview] Message-ID: <bug-103088-4-ygH6JAUezH@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103088-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103088 --- Comment #2 from seurer at gcc dot gnu.org --- One of the ocmpilations was this: /home/seurer/gcc/git/install/gcc-test/bin/gcc -c -o ext/re/re_comp.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 -m64 -O3 -mcpu=power9 -ffast-math -funroll-loops -fpeel-loops -fvect-cost-model -mpopcntd -mrecip=rsqrt -DSPEC_LP64 -Wno-deprecated-declarations -DSPEC_LINUX_PPC_LE -D_XOPEN_SOURCE=500 -fno-strict-aliasing ext/re/re_comp.c
next prev parent reply other threads:[~2021-11-05 14:19 UTC|newest] Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-04 20:45 [Bug other/103088] New: " seurer at gcc dot gnu.org 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 [this message] 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-ygH6JAUezH@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).