public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "nsz at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/95966] New: soft float operations are not tail called Date: Mon, 29 Jun 2020 15:00:26 +0000 [thread overview] Message-ID: <bug-95966-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95966 Bug ID: 95966 Summary: soft float operations are not tail called Product: gcc Version: 10.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: nsz at gcc dot gnu.org Target Milestone: --- i'd expect this to be a tail call into the soft float add operation on soft float targets: fp_t foo(fp_t a, fp_t b) { return a + b; } e.g. on x86 with 'typedef __float128 fp_t' the generated code is foo: sub rsp, 8 call __addtf3 add rsp, 8 ret on aarch64 with 'typedef long double fp_t' the generated code is foo: stp x29, x30, [sp, -16]! mov x29, sp bl __addtf3 ldp x29, x30, [sp], 16 ret i see similar code on other softfp targets.
next reply other threads:[~2020-06-29 15:00 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-29 15:00 nsz at gcc dot gnu.org [this message] 2021-08-14 9:43 ` [Bug middle-end/95966] " 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-95966-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).