From: Daniel Phillips <phillips@bonn-fries.net>
To: Momchil Velikov <velco@fadata.bg>
Cc: "" <simon@baydel.com>, Tim Schmielau <tim@physik3.uni-rostock.de>,
<linux-kernel@vger.kernel.org>
Subject: Re: unresolved symbols __udivdi3 and __umoddi3
Date: Mon, 28 Jan 2002 21:06:52 +0100 [thread overview]
Message-ID: <E16VI3J-0000C4-00@starship.berlin> (raw)
In-Reply-To: <Pine.LNX.3.95.1020125114634.762A-100000@chaos.analogic.com> <E16VHH9-0000Ba-00@starship.berlin> <87k7u2jm2v.fsf@fadata.bg>
In-Reply-To: <87k7u2jm2v.fsf@fadata.bg>
On January 28, 2002 08:46 pm, Momchil Velikov wrote:
> >>>>> "Daniel" == Daniel Phillips <phillips@bonn-fries.net> writes:
> >> Is this asm syntax documented anywhere ?
>
> Daniel> It's painful, isn't it? And no, I don't know where it's documented.
>
> It is documented in "Using and Porting GNU Compiler Collection"
> http://gcc.gnu.org/onlinedocs/gcc-3.0.3/gcc_5.html#SEC103
I suppose we could dignify that with the term 'documentation'. (To me, it
reads more like a tutorial than a reference work, though as always I'm
grateful to RMS and the FSF for having contributed this. And the price can't
be beat.)
Do you know where to find documentation for the assembly instructions
themselves?
--
Daniel
next prev parent reply other threads:[~2002-01-28 20:04 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-25 6:31 simon
2002-01-25 16:45 ` Andreas Dilger
2002-01-25 16:56 ` Richard B. Johnson
2002-01-25 21:42 ` Tim Schmielau
2002-01-28 4:21 ` simon
2002-01-28 17:38 ` Tim Schmielau
2002-01-28 19:17 ` Daniel Phillips
2002-01-28 19:28 ` Mark Zealey
2002-01-28 19:46 ` Momchil Velikov
2002-01-28 20:06 ` Daniel Phillips [this message]
2002-01-28 20:14 ` Momchil Velikov
2002-01-29 16:38 ` Horst von Brand
2002-01-30 8:09 ` Daniel Phillips
2002-01-30 8:43 ` Jeff Garzik
2002-01-30 8:23 ` Jeff Garzik
2002-01-28 11:08 ` Daniel Phillips
2002-01-28 11:10 ` Arjan van de Ven
2002-01-28 11:47 ` Daniel Phillips
2002-01-25 17:06 ` christophe barbé
2002-01-25 18:53 ` Christoph Hellwig
2002-01-25 19:03 ` christophe barbé
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E16VI3J-0000C4-00@starship.berlin \
--to=phillips@bonn-fries.net \
--cc=linux-kernel@vger.kernel.org \
--cc=simon@baydel.com \
--cc=tim@physik3.uni-rostock.de \
--cc=velco@fadata.bg \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®