public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "matz at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/110899] RFE: Attributes preserve_most and preserve_all Date: Mon, 07 Aug 2023 12:55:04 +0000 [thread overview] Message-ID: <bug-110899-4-1msugaiDAZ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110899-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110899 --- Comment #3 from Michael Matz <matz at gcc dot gnu.org> --- Huh, since when does clang implement this? See also https://gcc.gnu.org/pipermail/gcc-patches/2023-July/624004.html where I asked for comments about a similar, but not same, mechanism. I came from the angle of preserving a couple of SSE registers on x86-64. For ABIs you generally want a good mix between caller- and callee-saved registers. The x86-64 psABI didn't do that on the SSE regs for conscious, but meanwhile irrelevant, reasons, so my approach above tried to rectify this. The clang attributes seem to go against that general idea, they move all regs (or all general regs) into being callee-saved (except, strangely for aarch64?). It also makes argument registers be callee-saved, which is very unconventional. Does the clang implementation take into account the various problematic cases that arise when calling a normal function from a (say) preserve_all function (hint: such call can't usually be done)? Does exception handling, setjmp/longjmp and make/swapcontext interact with the clang attributes? That said: the implementation itself (after a more detailed spec) can be implemented in the same framework like the above patch. (It's possible that something more needs doing for the unusual situation that argument regs are then callee-saved).
next prev parent reply other threads:[~2023-08-07 12:55 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-08-04 13:57 [Bug target/110899] New: " elver at google dot com 2023-08-04 14:19 ` [Bug target/110899] " pinskia at gcc dot gnu.org 2023-08-07 8:38 ` rguenth at gcc dot gnu.org 2023-08-07 12:28 ` fw at gcc dot gnu.org 2023-08-07 12:55 ` matz at gcc dot gnu.org [this message] 2023-08-07 12:59 ` matz at gcc dot gnu.org 2023-08-07 13:42 ` fw at gcc dot gnu.org 2023-08-07 13:55 ` hubicka at gcc dot gnu.org 2023-08-07 15:34 ` matz at gcc dot gnu.org 2023-08-07 16:19 ` fw at gcc dot gnu.org 2023-08-07 16:24 ` matz at gcc dot gnu.org 2023-08-08 8:59 ` fw at gcc dot gnu.org 2023-08-08 12:47 ` matz at gcc dot gnu.org 2023-12-25 11:04 ` sjames at gcc dot gnu.org 2023-12-28 21:26 ` 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-110899-4-1msugaiDAZ@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).