public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hp at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/110628] [14 regression] gcc.dg/tree-ssa/update-threading.c fails after r14-2383-g768f00e3e84123 Date: Tue, 15 Aug 2023 16:23:42 +0000 [thread overview] Message-ID: <bug-110628-4-pJ1FKklxuo@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110628-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110628 Hans-Peter Nilsson <hp at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hp at gcc dot gnu.org --- Comment #5 from Hans-Peter Nilsson <hp at gcc dot gnu.org> --- A quick survey of recent test-results show this regression happens for many targets. Besides the reported: powerpc64le-unknown-linux-gnu https://gcc.gnu.org/pipermail/gcc-testresults/2023-August/793193.html Also fails for: pru-unknown-elf https://gcc.gnu.org/pipermail/gcc-testresults/2023-August/792102.html s390x-ibm-linux-gnu https://gcc.gnu.org/pipermail/gcc-testresults/2023-August/792106.html m68k-unknown-linux-gnu https://gcc.gnu.org/pipermail/gcc-testresults/2023-August/793249.html cris-axis-elf https://gcc.gnu.org/pipermail/gcc-testresults/2023-August/793462.html But, curiously not for: x86_64-pc-linux-gnu https://gcc.gnu.org/pipermail/gcc-testresults/2023-August/792111.html i686-pc-linux-gnu https://gcc.gnu.org/pipermail/gcc-testresults/2023-August/792104.html aarch64-unknown-linux-gnu https://gcc.gnu.org/pipermail/gcc-testresults/2023-August/793190.html arm-unknown-linux-gnueabihf https://gcc.gnu.org/pipermail/gcc-testresults/2023-August/793191.html Not seeing any action for this regression for three weeks, for tracking purposes I'm considering xfailing this test-case for cris-* after another week.
next prev parent reply other threads:[~2023-08-15 16:23 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-07-11 12:50 [Bug other/110628] New: " seurer at gcc dot gnu.org 2023-07-11 13:06 ` [Bug tree-optimization/110628] " rguenth at gcc dot gnu.org 2023-07-11 14:42 ` hubicka at gcc dot gnu.org 2023-07-11 14:51 ` seurer at gcc dot gnu.org 2023-07-13 13:13 ` hubicka at ucw dot cz 2023-07-17 23:02 ` seurer at gcc dot gnu.org 2023-08-15 16:23 ` hp at gcc dot gnu.org [this message] 2023-08-17 14:52 ` hubicka at ucw dot cz 2023-08-24 1:14 ` hp at gcc dot gnu.org 2023-08-24 12:03 ` hubicka at ucw dot cz 2023-08-24 14:54 ` hp at gcc dot gnu.org 2023-08-25 1:22 ` hp at gcc dot gnu.org 2024-03-07 23:29 ` law at gcc dot gnu.org 2024-05-07 7:41 ` [Bug tree-optimization/110628] [14/15 " rguenth 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-110628-4-pJ1FKklxuo@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).