public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Guillermo A. Loyola" <gmo@epigram.com>
To: egcs@egcs.cygnus.com
Subject: RE: `quad' printf format specifier ?
Date: Mon, 08 Feb 1999 09:25:00 -0000	[thread overview]
Message-ID: <8C36CEF2AF34D211922D00A0C9D60A54020D0F@epimail.epigram.com> (raw)

> Come to think of that, does it imply that we can do 'short 
> short' for an eight-bit byte? =)

From the list of gcc ports that never saw the light of day,
Microunity had one that defined:

		long long : 128 bits
		     long : 64 bits
			int : 64 bits
		    short : 32 bits
	    short short : 16 bits
		     char : 8 bits

Gmo.

WARNING: multiple messages have this Message-ID
From: "Guillermo A. Loyola" <gmo@epigram.com>
To: egcs@egcs.cygnus.com
Subject: RE: `quad' printf format specifier ?
Date: Sun, 28 Feb 1999 22:53:00 -0000	[thread overview]
Message-ID: <8C36CEF2AF34D211922D00A0C9D60A54020D0F@epimail.epigram.com> (raw)
Message-ID: <19990228225300.rnNqftS2AJs-aVGPhhAj0Nz4KLOBgSAfEnFFusgdyoM@z> (raw)

> Come to think of that, does it imply that we can do 'short 
> short' for an eight-bit byte? =)

             reply	other threads:[~1999-02-08  9:25 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-02-08  9:25 Guillermo A. Loyola [this message]
     [not found] ` < 8C36CEF2AF34D211922D00A0C9D60A54020D0F@epimail.epigram.com >
1999-02-08 11:48   ` Alex Buell
     [not found]     ` < Pine.LNX.4.05.9902081436140.307-100000@lo-pc3035a.hitc.com >
1999-02-08 12:24       ` Jeffrey A Law
     [not found]         ` < 1997.918505244@hurl.cygnus.com >
1999-02-08 13:12           ` Alex Buell
     [not found]             ` < Pine.LNX.4.05.9902081606350.164-100000@lo-pc3035a.hitc.com >
1999-02-08 13:57               ` Joe Buck
1999-02-28 22:53                 ` Joe Buck
1999-02-08 14:00               ` Jeffrey A Law
1999-02-28 22:53                 ` Jeffrey A Law
1999-02-28 22:53             ` Alex Buell
1999-02-28 22:53         ` Jeffrey A Law
1999-02-28 22:53     ` Alex Buell
1999-02-28 22:53 ` Guillermo A. Loyola
  -- strict thread matches above, loose matches on Subject: below --
1999-02-10 11:33 Kaveh R. Ghazi
1999-02-28 22:53 ` Kaveh R. Ghazi
1999-02-10  8:02 Kaveh R. Ghazi
1999-02-28 22:53 ` Kaveh R. Ghazi
1999-02-09  7:13 John Breen
     [not found] ` < 19990209150626.21275.qmail@hotmail.com >
1999-02-09  8:59   ` Alan Lehotsky
1999-02-08 15:20 Ross Smith
1999-02-28 22:53 ` Ross Smith
     [not found] <19990206133120.26761@liafa1.liafa.jussieu.fr>
1999-02-06 11:04 ` Zack Weinberg
     [not found]   ` < 199902061904.OAA02631@blastula.phys.columbia.edu >
1999-02-06 12:27     ` Alex Buell
1999-02-28 22:53       ` Alex Buell
1999-02-06 13:23     ` Marc Espie
1999-02-08  1:44       ` Andreas Schwab
1999-02-28 22:53         ` Andreas Schwab
     [not found]       ` < 19990206222305.19585@liafa1.liafa.jussieu.fr >
1999-02-08 20:51         ` Zack Weinberg
1999-02-28 22:53           ` Zack Weinberg
1999-02-28 22:53       ` Marc Espie
1999-02-28 22:53   ` Zack Weinberg

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=8C36CEF2AF34D211922D00A0C9D60A54020D0F@epimail.epigram.com \
    --to=gmo@epigram.com \
    --cc=egcs@egcs.cygnus.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).