From: "Andrej Borsenkow" <borsenkow.msk@sni.de>
To: "Peter Stephenson" <pws@ibmth.df.unipi.it>,
"Zsh hackers list" <zsh-workers@sunsite.auc.dk>
Subject: RE: pws-19
Date: Thu, 20 May 1999 11:10:35 +0400 [thread overview]
Message-ID: <004501bea28f$db10d8d0$21c9ca95@mow.siemens.ru> (raw)
In-Reply-To: <9905191127.AA40561@ibmth.df.unipi.it>
>
> Please try --enable-lfs if you have a 32-bit system with large file
> support.
>
I get here quite a lot of warnings, that look like
glob.c 1261: [warning]: CFE1859 result of small arithmetic used as wider
type
r = b->_links - a->_links;
^
glob.c 1265: [warning]: CFE1808 Cast of a large integral may lose bits
return (int) ((*s & GS_DESC) ? -r : r);
^
glob.c 2046: [warning]: CFE1807 Conversion of a large integral may lose
bits
int rstart = zstrtol(str+1,&dots,10), rend = 0, err = 0, rev = 0;
^
(glob.c was just an example).
Some (many? all?) of them are probbaly harmless - this is the case, when the
value definitely fits in 32 bit. But still there are possible problems:
1. is there any chance, that some variables were not converted to 64 bit?
2. I already have seen weird side effects with casts between 32 and 64 bit
values. The problem is, signed/unsigned conversion between 32 bit values is
always harmless - it does not change bit pattern. Unfortunately, when
casting 32 bit value to 64 bit one, this becomes *very* important. That is,
unsigned i; long j; i = (unsigned)j;
is noop, but
zulong i; long j; i = (unsigned)j;
does not sign extend - instead of small negative we get large positive
number.
I can post the messages here or send privately. Is anybody interested?
/andrej
next prev parent reply other threads:[~1999-05-20 7:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-05-19 11:27 pws-19 Peter Stephenson
1999-05-19 21:33 ` pws-19 Vin Shelton
1999-05-20 7:10 ` Andrej Borsenkow [this message]
1999-05-20 7:45 ` pws-19 Peter Stephenson
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='004501bea28f$db10d8d0$21c9ca95@mow.siemens.ru' \
--to=borsenkow.msk@sni.de \
--cc=pws@ibmth.df.unipi.it \
--cc=zsh-workers@sunsite.auc.dk \
/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.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).