This is the mail archive of the gcc-help@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: 16-bit int

From: Georg-Johann Lay <gjl at gcc dot gnu dot org>
To: David Brown <david at westcontrol dot com>
Cc: Göran Steen <goran dot steen at eis dot semcon dot com>, "gcc-help at gcc dot gnu dot org" <gcc-help at gcc dot gnu dot org>
Date: Fri, 10 Aug 2012 08:45:43 +0200
Subject: Re: 16-bit int
References: <D046C4666884894FB2C7C3FB30B2A14B04135A@se-got-mb01.semcon.se> <5023BD01.6090401@westcontrol.com>

David Brown schrieb:

On 09/08/2012 13:26, Göran Steen wrote:


I use gcc version 4.3.4, where int is 32-bit variables. Is it
possible to setup compiler to compile int as 16-bit variables?

The m86k port has 32-bit int, -mshort turns it to 16 bit.

The size of an int depends on the target - gcc supports dozens of targets. Most have 32-bit ints, but some have 16-bit ints and at least one has a compile-time option to support 8-bit ints (though that goes against C standards, and is deprecated on current builds). There are probably also targets with 64-bit ints.


You mean the avr port? int is 16 bits wide and -mint8 implements the
non-standard 8-bit int.  That option was broken for quite some time,
see PR46261. But that PR is fixed now.

Where in the release notes did you read about deprecation of -mint8?

Johann

Follow-Ups:
- Re: 16-bit int
  - From: David Brown

References:
- 16-bit int
  - From: Göran Steen
- Re: 16-bit int
  - From: David Brown

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]