public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/96015] [10/11 Regression] gcc-10.1.0 miscompiles Python on hppa Date: Tue, 09 Feb 2021 18:56:25 +0000 [thread overview] Message-ID: <bug-96015-4-sLxqDl9R3Q@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-96015-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96015 --- Comment #41 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Eric Botcazou <ebotcazou@gcc.gnu.org>: https://gcc.gnu.org/g:20f28986a8d3cad3c848d1e7da48f4bea7637298 commit r11-7154-g20f28986a8d3cad3c848d1e7da48f4bea7637298 Author: Eric Botcazou <ebotcazou@adacore.com> Date: Tue Feb 9 19:49:18 2021 +0100 Fix miscompilation of Python on HP-PA/Linux This is the miscompilation of Python at -O2 on HP-PA/Linux present on the mainline and 10 branch, caused by the presence of a call to __builtin_unreachable () in the middle of a heavily branchy code, which confuses the reorg pass. gcc/ PR rtl-optimization/96015 * reorg.c (skip_consecutive_labels): Minor comment tweaks. (relax_delay_slots): When deleting a jump to the next active instruction over a barrier, first delete the barrier if the jump is the only way to reach the target label.
next prev parent reply other threads:[~2021-02-09 18:56 UTC|newest] Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-01 7:29 [Bug target/96015] New: [regression] " slyfox at inbox dot ru 2020-07-01 7:30 ` [Bug target/96015] " slyfox at inbox dot ru 2020-07-01 7:32 ` slyfox at inbox dot ru 2020-07-01 7:38 ` slyfox at inbox dot ru 2020-07-01 8:03 ` [Bug target/96015] [10/11 Regression] " rguenth at gcc dot gnu.org 2020-07-01 8:11 ` marxin at gcc dot gnu.org 2020-07-01 9:14 ` slyfox at inbox dot ru 2020-07-01 9:15 ` slyfox at inbox dot ru 2020-07-01 13:11 ` marxin at gcc dot gnu.org 2020-07-01 13:12 ` marxin at gcc dot gnu.org 2020-07-01 15:39 ` slyfox at inbox dot ru 2020-07-01 15:40 ` slyfox at inbox dot ru 2020-07-01 15:46 ` slyfox at inbox dot ru 2020-07-01 16:35 ` law at redhat dot com 2020-07-01 17:33 ` law at redhat dot com 2020-07-01 17:57 ` slyfox at inbox dot ru 2020-07-01 19:15 ` slyfox at inbox dot ru 2020-07-02 6:58 ` slyfox at inbox dot ru 2020-07-02 7:58 ` marxin at gcc dot gnu.org 2020-07-02 9:34 ` ebotcazou at gcc dot gnu.org 2020-07-02 17:15 ` slyfox at inbox dot ru 2020-07-02 17:15 ` slyfox at inbox dot ru 2020-07-02 17:16 ` slyfox at inbox dot ru 2020-07-02 20:21 ` slyfox at inbox dot ru 2020-07-02 20:50 ` slyfox at inbox dot ru 2020-07-02 21:35 ` slyfox at inbox dot ru 2020-07-02 22:36 ` slyfox at inbox dot ru 2020-07-02 23:16 ` [Bug rtl-optimization/96015] " ebotcazou at gcc dot gnu.org 2020-07-03 7:19 ` slyfox at inbox dot ru 2020-07-03 7:45 ` marxin at gcc dot gnu.org 2020-07-03 8:23 ` ebotcazou at gcc dot gnu.org 2020-07-03 9:23 ` ebotcazou at gcc dot gnu.org 2020-07-03 17:24 ` slyfox at inbox dot ru 2020-07-03 19:29 ` ebotcazou at gcc dot gnu.org 2020-07-06 20:31 ` law at redhat dot com 2020-07-07 8:09 ` ebotcazou at gcc dot gnu.org 2020-07-08 17:01 ` law at redhat dot com 2020-07-23 6:51 ` rguenth at gcc dot gnu.org 2021-01-14 9:04 ` rguenth at gcc dot gnu.org 2021-01-14 16:33 ` law at redhat dot com 2021-01-14 19:14 ` mikpelinux at gmail dot com 2021-01-15 16:54 ` ebotcazou at gcc dot gnu.org 2021-02-09 18:56 ` cvs-commit at gcc dot gnu.org [this message] 2021-02-09 18:59 ` cvs-commit at gcc dot gnu.org 2021-02-09 19:01 ` ebotcazou at gcc dot gnu.org 2021-02-09 20:21 ` dave.anglin at bell dot net
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-96015-4-sLxqDl9R3Q@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).