Date:	Thu, 24 Jun 1999 12:02:01 +0300 (IDT)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	Eric Rudd <rudd AT cyberoptics DOT com>
cc:	djgpp-workers AT delorie DOT com
Subject:	Re: libm sources from cyberoptics
In-Reply-To:	<37710B48.65EFC737@cyberoptics.com>
Message-ID:	<Pine.SUN.3.91.990624120124.25071G-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp-workers AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Wed, 23 Jun 1999, Eric Rudd wrote:

> The whole business would bother me less if gas had a manual defining the
> quirky mnemonics and their actions.  However, I know of no such manual, so
> we have to go back to the Intel docs, which are buggy in various ways.
> Thus, there is really *no* documentation of what those mnemonics do.  I'd
> submit a bug report, but I honestly don't know what I should suggest that
> they do.

I would suggest to submit a bug report anyway, and let the maintainer
decide what would be the best practical way of solving that.
Documenting the problem would be a good idea (IMHO), so if you can
afford writing some text, perhaps the Binutils maintainer will simply
add it to the next release.

> I still need to know what to do about exp2 and pow2.

The pow2 and pow10 cases are taken care of by libc/stubs.h, so you
don't have to do anything.  As for exp2 and exp10, since they aren't
ANSI, I suggest to remove _exp2 and _exp10 labels from pow2.S and
pow10.S, and add two short .S files that jmp to __pow2 and __pow10,
respectively.

> I will zip up the corrected docs along with the new source.

Thanks.

- Raw text -