public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Eljay Love-Jensen <eljay@adobe.com>
To: Vincent Torri <torri@math.u-strasbg.fr>, gcc-help@gcc.gnu.org
Subject: Re: long long constant
Date: Fri, 18 Jun 2004 12:08:00 -0000	[thread overview]
Message-ID: <6.1.1.1.0.20040618070731.021fcc50@iplan-mn.corp.adobe.com> (raw)
In-Reply-To: <Pine.SOL.4.21.0406180035310.27739-100000@irmasrv2>

Hi Vincent,

Both long long, and long long numeric literals, are extensions.

A long long numeric literal requires the LL suffix.  The compiler doesn't 
automagically promote "too big" numeric literals into long longs.

My recommendation is to rely upon the 5 year old C99 header file <stdint.h> 
(even in C++), and use their facilities.

#include <stdint.h>
static int64_t const rounder = INT64_C(0x0000400000004000);

HTH,
--Eljay

  reply	other threads:[~2004-06-18 12:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-17 22:40 Vincent Torri
2004-06-18 12:08 ` Eljay Love-Jensen [this message]
2004-06-18 12:32   ` Falk Hueffner
2004-06-18 13:08     ` Eljay Love-Jensen
2004-06-18 20:48       ` Vincent Torri

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=6.1.1.1.0.20040618070731.021fcc50@iplan-mn.corp.adobe.com \
    --to=eljay@adobe.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=torri@math.u-strasbg.fr \
    /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).