public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "egallager at gcc dot gnu.org" <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: Wed, 04 Sep 2024 15:07:23 +0000 [thread overview] Message-ID: <bug-83324-4-GY56Bf5Otb@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 #34 from Eric Gallager <egallager at gcc dot gnu.org> --- Yeah I think GCC should support the __attribute__ style syntax for this attribute, too
prev parent reply other threads:[~2024-09-04 15:07 UTC|newest] Thread overview: 34+ 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 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 2024-07-12 23:16 ` mpolacek at gcc dot gnu.org 2024-07-18 4:27 ` cvs-commit at gcc dot gnu.org 2024-07-18 4:27 ` cvs-commit at gcc dot gnu.org 2024-07-18 4:27 ` cvs-commit at gcc dot gnu.org 2024-07-18 4:27 ` cvs-commit at gcc dot gnu.org 2024-07-18 15:34 ` andi-gcc at firstfloor dot org 2024-07-20 6:34 ` cvs-commit at gcc dot gnu.org 2024-07-20 6:34 ` cvs-commit at gcc dot gnu.org 2024-07-20 6:34 ` cvs-commit at gcc dot gnu.org 2024-07-20 6:34 ` cvs-commit at gcc dot gnu.org 2024-07-23 20:28 ` cvs-commit at gcc dot gnu.org 2024-07-23 20:28 ` cvs-commit at gcc dot gnu.org 2024-07-23 20:28 ` cvs-commit at gcc dot gnu.org 2024-07-23 21:10 ` ak at gcc dot gnu.org 2024-08-21 21:31 ` lucier at math dot purdue.edu 2024-08-22 16:32 ` andi at firstfloor dot org 2024-08-23 17:45 ` lucier at math dot purdue.edu 2024-08-25 1:39 ` lucier at math dot purdue.edu 2024-08-25 22:08 ` andi at firstfloor dot org 2024-08-26 0:25 ` lucier at math dot purdue.edu 2024-09-04 15:07 ` egallager at gcc dot gnu.org [this message]
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-GY56Bf5Otb@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).