From: Peter Dyballa <Peter_Dyballa@Freenet.DE>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 766@emacsbugs.donarmstrong.com, bug-gnu-emacs@gnu.org
Subject: bug#766: 23.0.60; interesting warning during compilation
Date: Sun, 24 Aug 2008 00:23:29 +0200 [thread overview]
Message-ID: <904AC839-3CCF-4AE3-956D-D482B0EE1955@Freenet.DE> (raw)
In-Reply-To: <uod3j3aak.fsf@gnu.org>
Am 23.08.2008 um 19:34 schrieb Eli Zaretskii:
>> Could it work to type-cast the variable first into a type wider than
>> 32 bits?
>
> It could, if we could be sure that 64-bit wide integer types are
> supported on all platforms. I don't know if they are; does anyone
> know?
There aren't so many (elderly) systems left ... Besides, isn't the
long long, a data type of at least 64 bits, defined in C, ANSI C99 to
be exact? Actually, I think, it's sad that no compiler needs to
follow this option!
Another option is to check whether the size of the variable is bigger
than four bytes.
--
Greetings
Pete
Rain is saved up in cloud banks.
next prev parent reply other threads:[~2008-08-23 22:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87k5e2uvl4.fsf@cyd.mit.edu>
2008-08-23 9:00 ` bug#766: 23.0.60; interesting warning during compilation Peter Dyballa
2008-08-23 14:10 ` Eli Zaretskii
2008-08-23 14:58 ` Peter Dyballa
2008-08-23 17:34 ` Eli Zaretskii
2008-08-23 22:23 ` Peter Dyballa [this message]
2008-08-24 3:13 ` Eli Zaretskii
2008-08-24 7:27 ` Peter Dyballa
2008-08-24 18:12 ` Eli Zaretskii
2008-08-23 17:33 ` Andreas Schwab
2008-08-23 18:18 ` Eli Zaretskii
2008-08-23 18:56 ` Andreas Schwab
2008-08-23 19:06 ` Eli Zaretskii
2008-08-23 20:03 ` Andreas Schwab
2008-08-23 20:50 ` Eli Zaretskii
2008-08-23 23:12 ` Andreas Schwab
2008-08-24 3:14 ` Eli Zaretskii
2008-09-03 18:47 ` Stefan Monnier
2008-08-27 19:10 ` bug#766: marked as done (23.0.60; interesting warning during compilation) Emacs bug Tracking System
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=904AC839-3CCF-4AE3-956D-D482B0EE1955@Freenet.DE \
--to=peter_dyballa@freenet.de \
--cc=766@emacsbugs.donarmstrong.com \
--cc=bug-gnu-emacs@gnu.org \
--cc=eliz@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).