mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Valery Ushakov <uwe@stderr.spb.ru>
To: musl@lists.openwall.com
Subject: [musl] Re: Re: Not sure how to debug this one.
Date: Sun, 18 Feb 2024 15:15:52 +0300	[thread overview]
Message-ID: <ZdH0-P9zw0t20LXc@snips.stderr.spb.ru> (raw)
In-Reply-To: <Pine.BSM.4.64L.2402172305090.9009@herc.mirbsd.org>

On Sat, Feb 17, 2024 at 23:09:24 +0000, Thorsten Glaser wrote:

> Valery Ushakov dixit:
> 
> >comments (*ugh*), but I *think* sigsetjmp clobbers caller's r8.
> >
> >r8 is callee saved.
> 
> Say, is there a handy list of which registers are preserved
> or clobbered across function calls like the one for syscalls
> from Linux man-pages’ syscall(2) for all arches?
> 
> I have indeed chased this same problem on unfamiliar arches
> often enough as well…

Calling conventions etc are defined in architecture's ELF psABI (ps =
processor specific, as opposed to generic (gABI)).  Though it seems
this terminology is now a bit dated.  E.g. Renesas ABI document still
has a running title of "SH-4 Generic and Specific ABI", where you can
see the echo of "generic" and "specific", but the word "processor"
never even occurs in it once.

The ELF ABI spec used to be hosted by (the old) SCO, iirc.  I'm not
sure what is the official source of truth nowadays of if even there is
one.

I would just google for "$arch psABI" and/or "$arch calling convention" :)

-uwe

  reply	other threads:[~2024-02-18 12:37 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-17  1:48 [musl] " Rob Landley
2024-02-17  3:23 ` [musl] Re: [Toybox] " Mouse
2024-02-17 13:32   ` Rob Landley
2024-02-17 15:01     ` [musl] " Thorsten Glaser
2024-02-17 15:21     ` [musl] " Mouse
2024-02-17 17:02 ` [musl] " Rich Felker
2024-02-17 21:45 ` [musl] " Valery Ushakov
2024-02-17 23:09   ` Thorsten Glaser
2024-02-18 12:15     ` Valery Ushakov [this message]
2024-02-18 22:51       ` Thorsten Glaser
2024-02-18  1:34   ` Rich Felker
2024-02-18  1:40     ` Rich Felker
2024-02-18 12:55       ` Valery Ushakov
2024-02-18 14:33         ` Rich Felker
2024-02-18 15:06           ` Valery Ushakov
2024-02-18 20:33             ` Rich Felker
2024-02-19 11:00               ` Valery Ushakov
2024-02-19 17:54       ` Rob Landley
2024-02-19 23:05         ` Rich Felker
2024-02-18 12:47     ` Valery Ushakov
2024-02-19 13:12     ` Rob Landley

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=ZdH0-P9zw0t20LXc@snips.stderr.spb.ru \
    --to=uwe@stderr.spb.ru \
    --cc=musl@lists.openwall.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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 NNTP newsgroup(s).