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 c/83324] [feature request] Pragma or special syntax for guaranteed tail calls
Date: Thu, 16 Nov 2023 17:27:51 +0000	[thread overview]
Message-ID: <bug-83324-4-eUv8mrozkG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-83324-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83324

--- Comment #5 from Mikael Pettersson <mikpelinux at gmail dot com> ---
To get guaranteed tail-calls to work you need to adjust the calling convention
for the caller as well as the callee. Things are trivial as long as parameters
always fit in registers. With parameters on the stack you need, in general, to
shift the responsibility for their deallocation from caller to callee, and this
results in a non-standard calling convention.

  parent reply	other threads:[~2023-11-16 17:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-83324-4@http.gcc.gnu.org/bugzilla/>
2021-12-04 16:14 ` pietro.gcc at sociotechnical dot xyz
2023-11-16  4:41 ` pinskia at gcc dot gnu.org
2023-11-16  4:49 ` dje at gcc dot gnu.org
2023-11-16 17:27 ` mikpelinux at gmail dot com [this message]
2023-11-16 17:34 ` pinskia at gcc dot gnu.org
2023-11-19 17:19 ` pinskia at gcc dot gnu.org
2023-11-19 17:23 ` sjames at gcc dot gnu.org
2023-11-20  1:07 ` dje at gcc dot gnu.org
2023-11-20  1:21 ` pinskia at gcc dot gnu.org
2023-11-20 14:34 ` dje at gcc dot gnu.org
2023-12-25 11:06 ` sjames at gcc dot gnu.org
2024-01-24 11:13 ` sjames at gcc dot gnu.org
2024-06-20  5:29 ` andi-gcc at firstfloor dot 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-83324-4-eUv8mrozkG@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: link
Be 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).