public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: lrtaylor@micron.com
To: <niverson@pillardata.com>, <gcc-help@gcc.gnu.org>
Subject: RE: Does Cygwin's GCC support 64-bit constants?
Date: Tue, 02 Mar 2004 23:17:00 -0000	[thread overview]
Message-ID: <363801FFD7B74240A329CEC3F7FE4CC4015F3A15@ntxboimbx07.micron.com> (raw)

Try adding 'L' to the end of the constant:

0xFF00000000000000L

That tells the compiler that it's a long and not an integer.

Cheers,
Lyle


-----Original Message-----
From: gcc-help-owner@gcc.gnu.org [mailto:gcc-help-owner@gcc.gnu.org] On
Behalf Of Nate Iverson
Sent: Tuesday, March 02, 2004 4:16 PM
To: gcc-help@gcc.gnu.org
Subject: Does Cygwin's GCC support 64-bit constants?

I'm getting the following warning message when I try to compile source
code that contains 0xFF00000000000000 as a constant.
warning: integer constant is too large for "long" type

Cywin's GCC appears to have 64-bit integer support since there are no
warnings/errors for uint64_t variables.

Below are the gcc details:
$ gcc -v
Reading specs from /bin/../lib/gcc-lib/i686-pc-cygwin/3.3.1/specs
Configured with: /GCC/gcc-3.3.1-3/configure --with-gcc --with-gnu-ld
--with-gnu-as --prefix=/usr --exec-prefix=/usr --sysconfdir=/etc
--libdir=/usr/lib --libexecdir=/usr/sbin --mandir=/usr/share/man
--infodir=/usr/share/info
--enable-languages=c,ada,c++,f77,pascal,java,objc --enable-libgcj
--enable-threads=posix --with-system-zlib --enable-nls
--without-included-gettext --enable-interpreter --enable-sjlj-exceptions
--disable-version-specific-runtime-libs --enable-shared
--disable-win32-registry --enable-java-gc=boehm
--disable-hash-synchronization --verbose --target=i686-pc-cygwin
--host=i686-pc-cygwin --build=i686-pc-cygwin
Thread model: posix
gcc version 3.3.1 (cygming special)

I have also tried to cast the constant (long long)0xFF00000000000000 --
it didn't change anything. Additionally, I have compiled this on Linux
and QNX with no issues.

Any insight is appreciated,
Nate


             reply	other threads:[~2004-03-02 23:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-02 23:17 lrtaylor [this message]
2004-03-03  0:22 ` Mark Woollard
  -- strict thread matches above, loose matches on Subject: below --
2004-03-02 23:16 Nate Iverson
2004-03-03  2:39 ` Eljay Love-Jensen

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=363801FFD7B74240A329CEC3F7FE4CC4015F3A15@ntxboimbx07.micron.com \
    --to=lrtaylor@micron.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=niverson@pillardata.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).