From: "Nate Iverson" <niverson@pillardata.com>
To: <gcc-help@gcc.gnu.org>
Subject: Does Cygwin's GCC support 64-bit constants?
Date: Tue, 02 Mar 2004 23:16:00 -0000 [thread overview]
Message-ID: <0565CAF35FADD64DA09B86C3637BE7292E8C5C@coex01.trans.corp> (raw)
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
next reply other threads:[~2004-03-02 23:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-02 23:16 Nate Iverson [this message]
2004-03-03 2:39 ` Eljay Love-Jensen
2004-03-02 23:17 lrtaylor
2004-03-03 0:22 ` Mark Woollard
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=0565CAF35FADD64DA09B86C3637BE7292E8C5C@coex01.trans.corp \
--to=niverson@pillardata.com \
--cc=gcc-help@gcc.gnu.org \
/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).