From: Jonathan Lennox <lennox@cs.columbia.edu>
To: matthias.gehre@amd.com (Matthias Gehre)
Subject: Re: AW: [RFC] Adding division/modulo on arbitrary precision integers to libgcc
Date: Fri, 6 May 2022 12:39:02 -0400 [thread overview]
Message-ID: <25205.20262.994817.37250@compute02.cs.columbia.edu> (raw)
In-Reply-To: <SA1PR02MB857333A597CFDCEBDAADE583A7C59@SA1PR02MB8573.namprd02.prod.outlook.com>
On Friday, May 6 2022, "Matthias Gehre" wrote to "lennox" saying:
> Jakub Jelinek wrote:
> > Rather than uint32_t, wouldn't using the word size (64-bit for lp64, 32-bit
> for ilp32) be better?
> Is there a portable way to specify this in C? (size_t, uintptr_t?) And is the word size
> clearly defined for each target? (I'm not a backend expert).
Wouldn't this just be 'unsigned long' by definition?
--
Jonathan Lennox
lennox@cs.columbia.edu
next prev parent reply other threads:[~2022-05-06 16:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-06 14:09 Matthias Gehre
2022-05-06 14:36 ` Joseph Myers
2022-05-06 15:57 ` AW: " Matthias Gehre
2022-05-06 16:02 ` Joseph Myers
2022-05-06 14:47 ` Jakub Jelinek
2022-05-06 15:23 ` Joseph Myers
2022-05-06 15:42 ` AW: " Matthias Gehre
2022-05-06 16:39 ` Jonathan Lennox [this message]
2022-05-06 18:05 ` Segher Boessenkool
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=25205.20262.994817.37250@compute02.cs.columbia.edu \
--to=lennox@cs.columbia.edu \
--cc=matthias.gehre@amd.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).