From: "panda.trooper" <panda.trooper@protonmail.com>
To: "newlib@sourceware.org" <newlib@sourceware.org>
Subject: Why int32_t is long int on 32 Bit Intel?
Date: Thu, 27 Jul 2023 11:55:57 +0000 [thread overview]
Message-ID: <Cqp71y7dEMZ7WbDaFFzEzr4idhvMET4sJ3SsYd7rvBAURIX_tQ93hhswdmp5dr9FTpwV6N_ZQ2D4GWyAJIgGLQFUXlMlyt2jyRoldYuMyDQ=@protonmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 178 bytes --]
Hi, can somebody explain what is the reason behind the architectural decision that on x86 the type of int32_t is long int by default and not int when using newlib?
Thanks,
Zoltan
next reply other threads:[~2023-07-27 11:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-27 11:55 panda.trooper [this message]
2023-07-27 23:13 ` Brian Inglis
2023-07-28 8:06 ` panda.trooper
2023-07-28 13:23 ` Anders Montonen
2023-07-28 14:15 ` Joel Sherrill
2023-07-28 15:49 ` [EXTERNAL]: " Mike Burgess
2023-07-28 16:11 ` Stefan Tauner
2023-07-28 16:26 ` Mike Burgess
2023-07-28 17:06 ` Richard Damon
2023-07-28 18:05 ` Grant Edwards
2023-07-28 18:27 ` panda.trooper
2023-07-28 20:23 ` Jon Beniston
2023-07-28 21:42 ` panda.trooper
2023-07-28 21:53 ` Jon Beniston
2023-07-29 12:47 ` Trampas Stern
2023-07-29 13:19 ` Stefan Tauner
2023-07-29 21:21 ` Grant Edwards
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='Cqp71y7dEMZ7WbDaFFzEzr4idhvMET4sJ3SsYd7rvBAURIX_tQ93hhswdmp5dr9FTpwV6N_ZQ2D4GWyAJIgGLQFUXlMlyt2jyRoldYuMyDQ=@protonmail.com' \
--to=panda.trooper@protonmail.com \
--cc=newlib@sourceware.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: 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).