mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jeff Garzik <garzik@havoc.gtf.org>
To: Horst von Brand <brand@jupiter.cs.uni-dortmund.de>
Cc: Daniel Phillips <phillips@bonn-fries.net>, linux-kernel@vger.kernel.org
Subject: Re: unresolved symbols __udivdi3 and __umoddi3
Date: Wed, 30 Jan 2002 03:23:00 -0500	[thread overview]
Message-ID: <20020130032300.G32317@havoc.gtf.org> (raw)
In-Reply-To: <phillips@bonn-fries.net> <200201291638.g0TGcohv001323@tigger.cs.uni-dortmund.de>
In-Reply-To: <200201291638.g0TGcohv001323@tigger.cs.uni-dortmund.de>; from brand@jupiter.cs.uni-dortmund.de on Tue, Jan 29, 2002 at 05:38:50PM +0100

On Tue, Jan 29, 2002 at 05:38:50PM +0100, Horst von Brand wrote:
> Has anyone gotten a instruction listing (just instructions and short
> description, not the whole other stuff in there), preferably in AT&T
> syntax?

What is the AT&T syntax for short descriptions accompanying insns?

:)

	Jeff




  parent reply	other threads:[~2002-01-30  8:23 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
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 [this message]
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=20020130032300.G32317@havoc.gtf.org \
    --to=garzik@havoc.gtf.org \
    --cc=brand@jupiter.cs.uni-dortmund.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=phillips@bonn-fries.net \
    /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®