public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bugdal at aerifal dot cx" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/99491] New: [mips64] over-strict refusal to emit tail calls Date: Tue, 09 Mar 2021 18:03:47 +0000 [thread overview] Message-ID: <bug-99491-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99491 Bug ID: 99491 Summary: [mips64] over-strict refusal to emit tail calls Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: bugdal at aerifal dot cx Target Milestone: --- mips_function_ok_for_sibcall refuses to generate sibcalls (except locally) on mips64 due to %gp being call-saved and the possibility that the callee is a lazy resolver stub. This is presumably correct-ish on dynamic-linked platforms with lazy resolver, due to the resolver using the caller's value of %gp, but completely gratuitous on platforms that are static linked or don't use lazy resolver, such as musl libc. Moreover, the problem could be fixed even for lazy-resolver targets by generating an indirect function call reference that forcibly loads the address and can't go through a lazy resolver, rather than a PLT-like reference that might.
next reply other threads:[~2021-03-09 18:03 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-09 18:03 bugdal at aerifal dot cx [this message] 2021-03-09 19:14 ` [Bug target/99491] " 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-99491-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).