From: invalid AT erehwon DOT invalid (Graaagh the Mighty)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Strange behavior of compiler.
Organization: Low Charisma Anonymous
Message-ID: <3b31a94c.176308036@news.primus.ca>
References: <3b31a377 DOT 174815003 AT news DOT primus DOT ca> <3b31a893 DOT 176123084 AT news DOT primus DOT ca>
X-Newsreader: Forte Free Agent 1.11/32.235
Lines: 24
Date: Thu, 21 Jun 2001 07:59:38 GMT
NNTP-Posting-Host: 207.176.153.34
X-Complaints-To: news AT primus DOT ca
X-Trace: news2.tor.primus.ca 993110345 207.176.153.34 (Thu, 21 Jun 2001 03:59:05 EDT)
NNTP-Posting-Date: Thu, 21 Jun 2001 03:59:05 EDT
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

On Thu, 21 Jun 2001 07:58:54 GMT, invalid AT erehwon DOT invalid (Graaagh the
Mighty) sat on a tribble, which squeaked:

>I have more information. On a hunch I looked at the changes. There was
>a bug in one of the debugging bits I added that would in fact have
>jumped into never-never land -- *if* "bar" had ever been reached. So
>why weren't the call frame traceback EIPs more like:
>
>  0x01fc0000   0x1fc0000
>  0x00f00ba7   _bar+42, line 666 of bwlsm.c
>  0x0000178b   _main+275, line 195 of bwlsm.c
>  0x00057b7a   ___crt1_startup+174
>
>even with no aggressive optimizations? There's no way it was inlining
>bar -- not with less than -O3, not with bar as big as it is (~200
>loc), and not with bar called via a function pointer!

Oh, and by the way, it does work properly when the debugging printfs
in bar are fixed!
-- 
Bill Gates: "No computer will ever need more than 640K of RAM." -- 1980
"There's nobody getting rich writing software that I know of." -- 1980
"This antitrust thing will blow over." -- 1998
Combine neo, an underscore, and one thousand sixty-one to make my hotmail addy.