From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: "Göran Steen" <goran.steen@eis.semcon.com>
Cc: David Brown <david@westcontrol.com>,
"gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: Re: 16-bit int
Date: Fri, 10 Aug 2012 18:01:00 -0000 [thread overview]
Message-ID: <CAH6eHdQ5cK4AC_0bwAficDTF+qFO+KBWFYFgQGED0tKhVE6e6g@mail.gmail.com> (raw)
In-Reply-To: <D046C4666884894FB2C7C3FB30B2A14B0413FC@se-got-mb01.semcon.se>
On 10 August 2012 09:35, Göran Steen wrote:
> Thank you for your response.
>
> Sorry, this will not help. I want to test the snippets, not change them. Besides, I don't know if the compiler that will be used for the 16-bit machine will support any of the types you suggest, so I only want to use standard types.
Those are standard types.
But the bottom line is that on most targets you can't change the size
of int. You still haven't said what target you're using, but chances
are it's not possible. You could look into running a simulator for a
target with 16-bit int instead.
next prev parent reply other threads:[~2012-08-10 9:21 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-10 7:16 Göran Steen
2012-08-10 8:20 ` David Brown
2012-08-10 8:35 ` David Brown
2012-08-10 8:53 ` Göran Steen
2012-08-10 9:05 ` David Brown
2012-08-10 9:19 ` Göran Steen
2012-08-10 9:21 ` David Brown
2012-08-11 15:32 ` Vincent Lefevre
2012-08-11 16:28 ` Ian Lance Taylor
2012-08-11 19:36 ` Tim Prince
2012-08-13 14:42 ` David Brown
2012-08-10 18:01 ` Jonathan Wakely [this message]
2012-08-11 10:47 ` Vincent Lefevre
-- strict thread matches above, loose matches on Subject: below --
2012-08-09 11:26 Göran Steen
2012-08-09 13:45 ` David Brown
2012-08-09 18:52 ` Vincent Lefevre
2012-08-09 19:59 ` David Brown
2012-08-09 22:39 ` Vincent Lefevre
2012-08-09 22:52 ` Ian Lance Taylor
2012-08-10 6:53 ` Jose-Marcio Martins da Cruz
2012-08-11 10:33 ` Vincent Lefevre
2012-08-10 6:48 ` Georg-Johann Lay
2012-08-10 8:16 ` David Brown
2012-08-09 17:14 ` Paulo J. Matos
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=CAH6eHdQ5cK4AC_0bwAficDTF+qFO+KBWFYFgQGED0tKhVE6e6g@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=david@westcontrol.com \
--cc=gcc-help@gcc.gnu.org \
--cc=goran.steen@eis.semcon.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).