Your message dated Mon, 11 Sep 2017 12:36:53 +0200
with message-id <[email protected]>
and subject line Conflicting declarations of variable lastLineOffset
has caused the Debian Bug report #702361,
regarding Conflicting declarations of variable lastLineOffset
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
702361: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702361
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: basic256
Version: 0.9.6.69a-1
Usertags: goto-cc
While building the package using our research compiler infrastructure we noticed
the following conflicting declarations:
./LEX/basicParse.l:53:extern int lastLineOffset;
./LEX/basicParse.y:42:unsigned int lastLineOffset = 0; // store the byte offset
for the end of the last line - use in loops
The difference in signedness my cause undefined behaviour - in particular on big
endian systems this will become apparent immediately.
Best,
Michael
pgpm25AazLnoQ.pgp
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 1.1.4.0-1
lastLineOffset is no longer present in LEX/basicParse.l and
LEX/basicParse.y.
--- End Message ---
