From: Paul Koning <paulkoning@comcast.net>
To: Matheus Afonso Martins Moreira <matheus.a.m.moreira@gmail.com>
Cc: gcc@gcc.gnu.org
Subject: Re: [RFC] Linux system call builtins
Date: Wed, 10 Apr 2024 09:15:16 -0400 [thread overview]
Message-ID: <BAD977E8-1140-4812-AF5E-7E7E61728763@comcast.net> (raw)
In-Reply-To: <ad3f3e743fba028670681b4c8883d202@gmail.com>
> On Apr 9, 2024, at 9:48 PM, Matheus Afonso Martins Moreira via Gcc <gcc@gcc.gnu.org> wrote:
>
> ...
> MIPS calling conventions work like this:
>
>> mips/n32,64 a0 a1 a2 a3 a4 a5
>> mips/o32 a0 a1 a2 a3 ...
>> mips/o32 args5-8 are passed on the stack
Yes, for regular function calls, but at least in the case of NetBSD, not for syscalls. They have a somewhat odd calling convention that doesn't match any of the normal function call ABIs, though it's similar.
paul
next prev parent reply other threads:[~2024-04-10 13:15 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-08 9:19 Matheus Afonso Martins Moreira
2024-04-08 9:58 ` Jonathan Wakely
2024-04-08 11:59 ` Matheus Afonso Martins Moreira
2024-04-08 14:00 ` Jonathan Wakely
2024-04-08 11:24 ` Florian Weimer
2024-04-08 11:44 ` Alexander Monakov
2024-04-08 11:50 ` Florian Weimer
2024-04-08 13:01 ` Alexander Monakov
2024-04-08 13:37 ` Matheus Afonso Martins Moreira
2024-04-08 18:18 ` Paul Iannetta
2024-04-08 18:26 ` Andrew Pinski
2024-04-08 20:01 ` Paul Iannetta
2024-04-08 20:20 ` Paul Koning
2024-04-10 1:48 ` Matheus Afonso Martins Moreira
2024-04-10 13:15 ` Paul Koning [this message]
2024-04-10 14:10 ` Matheus Afonso Martins Moreira
2024-04-10 1:26 ` Matheus Afonso Martins Moreira
2024-04-08 20:24 ` Paul Floyd
2024-04-10 2:19 ` Matheus Afonso Martins Moreira
2024-04-09 11:45 ` Szabolcs Nagy
2024-04-10 2:59 ` Matheus Afonso Martins Moreira
2024-04-10 11:04 ` Szabolcs Nagy
2024-04-10 14:00 ` Matheus Afonso Martins Moreira
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=BAD977E8-1140-4812-AF5E-7E7E61728763@comcast.net \
--to=paulkoning@comcast.net \
--cc=gcc@gcc.gnu.org \
--cc=matheus.a.m.moreira@gmail.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.
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).