public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mikpelinux at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/96475] direct threaded interpreter with computed gotos generates suboptimal dispatch loop Date: Thu, 06 Aug 2020 16:44:06 +0000 [thread overview] Message-ID: <bug-96475-4-F9SInxMywm@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-96475-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96475 --- Comment #5 from Mikael Pettersson <mikpelinux at gmail dot com> --- I can't reproduce on {ppc64le, ppc64, aarch64, m68k, x86_64}-linux-gnu, they all inline the dispatcher at the end of each handler, w/ gcc-10.2.0 -O2. However, for sparc64 gcc-10.2.0 -O2 does end each handler with a branch to a shared dispatcher (which is not what we want).
next prev parent reply other threads:[~2020-08-06 16:44 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-08-05 0:14 [Bug rtl-optimization/96475] New: " npiggin at gmail dot com 2020-08-05 10:02 ` [Bug rtl-optimization/96475] " mikpelinux at gmail dot com 2020-08-05 17:54 ` segher at gcc dot gnu.org 2020-08-05 22:33 ` mikpelinux at gmail dot com 2020-08-05 22:55 ` segher at gcc dot gnu.org 2020-08-06 16:44 ` mikpelinux at gmail dot com [this message] 2020-08-06 23:47 ` segher at gcc dot gnu.org 2020-09-09 16:56 ` cvs-commit at gcc dot gnu.org 2020-09-09 17:06 ` segher at gcc dot gnu.org 2020-09-09 19:27 ` clyon at gcc dot gnu.org 2020-09-09 19:37 ` segher at gcc dot gnu.org 2020-09-09 19:53 ` clyon at gcc dot gnu.org 2020-09-09 20:05 ` segher at gcc dot gnu.org 2020-09-10 8:58 ` clyon at gcc dot gnu.org 2020-09-10 9:30 ` clyon at gcc dot gnu.org 2020-09-10 10:50 ` acoplan at gcc dot gnu.org 2020-09-13 5:50 ` dinuxbg at gmail dot com 2020-09-14 8:18 ` asolokha at gmx dot com 2020-09-14 13:42 ` segher at gcc dot gnu.org 2020-09-14 14:34 ` segher at gcc dot gnu.org 2020-09-14 14:35 ` segher at gcc dot gnu.org 2020-09-14 15:24 ` asolokha at gmx dot com 2020-09-14 16:02 ` clyon at gcc dot gnu.org 2020-09-14 19:07 ` dinuxbg at gmail dot com 2020-09-15 13:18 ` cvs-commit at gcc dot gnu.org 2021-05-04 12:31 ` 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-96475-4-F9SInxMywm@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).