Board index » cppbuilder » linker warning puzzle...

linker warning puzzle...


2008-01-12 02:48:44 AM
cppbuilder16
bds2006
Should we be concerned about the executable(s) built where the linker
produced this warning?
What, really, does it mean?
[Linker Warning] Warning: LINN32: Last line 2029 (7EDh) is less than first
line 2029 (7EDh) for symbol "<null>" in module c:\<somepath>\<asourcefile>.c
[editor: <somepath>and <asourcefile>have been substituted for actual
names]
note: <asourcefile.c>is part of a library that is being linked in
Thanks
 
 

Re:linker warning puzzle...

dhoke wrote:
Quote
Should we be concerned about the executable(s) built where the linker
produced this warning?
Did you Google LINN32?
qc.borland.com/wc/qcmain.asp
 

Re:linker warning puzzle...

Well, in my case, it prevented me from debugging the unit at source level.
I traced down this problem to one rather complex expression.
With this expression broken down to pieces (on several lines), the warning
disappeared and the source level debugging worked again.
Pavel
"dhoke" < XXXX@XXXXX.COM >píše v diskusním příspěvku
Quote
bds2006

Should we be concerned about the executable(s) built where the linker
produced this warning?

What, really, does it mean?

[Linker Warning] Warning: LINN32: Last line 2029 (7EDh) is less than first
line 2029 (7EDh) for symbol "<null>" in module
c:\<somepath>\<asourcefile>.c

[editor: <somepath>and <asourcefile>have been substituted for actual
names]

note: <asourcefile.c>is part of a library that is being linked in

Thanks



 

{smallsort}

Re:linker warning puzzle...

FWIW, a provider of code (in a library to us) causing the warning contained
something similar to:
*++pI = !flag ? func(val1, val2) :
func(val3, val4) ;
when they changed that code to:
if(!flag) *++pI = func(val1, val2) ;
else *++pI = func(val3, val4);
the warning ceased to occur. (Thanks, Pavel.)
Quote
I traced down this problem to one rather complex expression.
With this expression broken down to pieces (on several lines), the warning
 

Re:linker warning puzzle...

Is that vendor a subsidiary of Write-Only Code Inc?
. Ed
Quote
dhoke wrote in message
news: XXXX@XXXXX.COM ...

FWIW, a provider of code (in a library to us) causing the warning
contained something similar to:
*++pI = !flag ? func(val1, val2) :
func(val3, val4) ;

when they changed that code to:
if(!flag) *++pI = func(val1, val2) ;
else *++pI = func(val3, val4);

the warning ceased to occur. (Thanks, Pavel.)