From:	buers AT gmx DOT de (Dieter Buerssner)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: inefficiency of GCC output code & -O problem
Date:	13 Apr 2000 21:49:31 GMT
Lines:	27
Message-ID:	<8d5mi0.3vvqipv.0@buerssner-17104.user.cis.dfn.de>
References:	<200004121649 DOT SAA12655 AT acp3bf DOT physik DOT rwth-aachen DOT de> <38F4C0D9 DOT C73A8E0A AT mtu-net DOT ru> <8d4rse DOT 3vvrn3d DOT 0 AT buerssner-17104 DOT user DOT cis DOT dfn DOT de> <38F60FE4 DOT 31BF32BB AT mtu-net DOT ru>
NNTP-Posting-Host:	pec-115-232.tnt7.s2.uunet.de (149.225.115.232)
Mime-Version:	1.0
X-Trace:	fu-berlin.de 955662571 7566287 149.225.115.232 (16 [17104])
X-Posting-Agent:	Hamster/1.3.13.0
User-Agent:	Xnews/03.02.04
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Alexei A. Frounze wrote:

>OKay guys, please explain me what do you mean by BUGGY? Plese explain what
>*exactly* do you mean. 

I have shown and explained some bugs already. If you didn't understand,
what I have said, or if you think it was wrong, you may point out
where the problems are.

>It must notify me if it lacks of free registers. Don't you think?

No. Once again: you didn't ask for registers with the "g".

>Btw, this program works as it should. Try yourself. I bet you'll get the
>same result as mine (if you use the latest GCC).

Your were just lucky. The next version of gcc, or even different
command line options, may cause a failure.
Why can't you accept, that the working program doesn't prove anything.

BTW. You have snipped the part, where I said, that minor modifications,
that do *not* touch your inline assembly and your variables, will make 
your program fail. Yes, I tried it.

-- 
Regards, Dieter

- Raw text -