Re: g++/linker bug on cygwin1.1.0 (win32)

[Marat Boshernitsan <maratb at CS dot Berkeley dot EDU>]

[ My mailer seems to have eaten the body of my message, leaving only the
attached testcase, at least in the copy I got back from the cygwin
mailing list. Here's the message without the attachment again. Sorry. ]

Marat Boshernitsan <maratb@CS.Berkeley.EDU> writes:

> Hello,
> 
> I've hit upon an obscure g++/linker bug on Cygwin1.1.0 which causes the
> resulting executable to have "call 0x0" instructions in a few places
> instead of proper calls.  The attached testcase (together with the
> Makefile) demonstrates the problem: just do make and run one of the
> resulting "bug*" executables to get a runtime error.
> 
> Few points of interest:
> 
> - the test case is fairly obscure, but it is distilled from a much
> larger system.
> 
> - if the return type of the argument type of "void* __stdcall
> I_RpcAllocate(unsigned int);" declaration in dlltest.cc are modified in
> any way the problem goes away.  (This declaration is not random: I
> actually pulled it out of one of the cygwin header files -- rpcdcep.h --
> after several hours of chasing this down).
> 
> - if the order of object files is changed during linking the problem
> goes away
> 
> 
> My environment is:
> 
> uname -a:
> CYGWIN_NT-4.0 DOGWOOD 1.1.0(0.17/3/2) 2000-03-01 00:15:19 i686 unknown
> 
> gcc -v:
> Reading specs from /usr/lib/gcc-lib/i686-pc-cygwin/2.95.2/specs
> gcc version 2.95.2 19991024 (release)
> 
> ld -v:
> GNU ld version 19990818 (with BFD 19990818)
> 
> as -v:
> GNU assembler version 19990818 (i686-pc-cygwin) using BFD version 19990818
> 
> 
> Any help, hints, or workarounds will be greatly appreciated.
> 
> Thanks,
> 
> Marat.

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com