Date: Sun, 16 Apr 2000 09:56:39 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: "Alexei A. Frounze" <alex DOT fru AT mtu-net DOT ru>
cc: djgpp AT delorie DOT com
Subject: Re: inefficiency of GCC output code & -O problem
In-Reply-To: <38F8BA6F.13164C92@mtu-net.ru>
Message-ID: <Pine.SUN.3.91.1000416095608.2482F-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Sat, 15 Apr 2000, Alexei A. Frounze wrote:

> Hmm, how do we really know how many values are left by GCC on the FPU stack?

I think you can't, in general, not at compile time.

However, if you get to the point where you need such an intricate
knowledge about the code generated by GCC, perhaps some reality check
is in order.  IIRC, the original motivation for your inline assembly
was to avoid the cost of a call to the `ceil' library function.
Surely there must be an easier way of doing whatever you needed `ceil'
for without knowing which part of the FP stack is in use, right?

Suppose you describe the original problem(s) which led you to use the
inline assembly in the first place, in this particular case?  Chances
are, that problem has a much simpler solution.