linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Hendricks <khendricks@ivey.uwo.ca>
To: David Edelsohn <dje@watson.ibm.com>, Moritz Thomas <motho@gmx.net>
Cc: linuxppc-dev@lists.linuxppc.org,
	linuxppc-user@lists.linuxppc.org,
	Kevin_Hendricks <khendricks@admin.ivey.uwo.ca>
Subject: Re: still no accelerated X ($#!$*)
Date: Thu, 20 Jan 2000 13:25:40 -0500	[thread overview]
Message-ID: <00012013281100.00851@localhost.localdomain> (raw)
In-Reply-To: <200001201819.NAA25088@mal-ach.watson.ibm.com>


Hi,

Thanks for your reply.

> Why does each application/library define its own, incorrect
> definition of byte-reversed instructions?  Doesn't some Linux/PPC header
> file define this once in a awy that could be imported by others?

I could not find one.  I will look again.

> 	One cannot use "r" as a constraint for a base address, that is
> what the GCC PowerPC port defines "b" for.  The load/store instruction
> patterns in the GCC PowerPC machine description file use a different
> constraint letter for the base address, and anyone writing inlined
> assembly -- especially loads and stores -- should browse the GCC machine
> description.

Thanks I will as soon as I find it ;-).  But the assembler generated was exactly
the same in my simple test case.  Is this just luck?

Thanks,

Kevin

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2000-01-20 18:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-01-19 10:38 still no accelerated X ($#!$*) Moritz Thomas
2000-01-20 18:19 ` David Edelsohn
2000-01-20 18:25   ` Kevin Hendricks [this message]
2000-01-20 18:42     ` Geert Uytterhoeven
     [not found] <20000117135832.10037gmx1@mx2.gmx.net>
     [not found] ` <l03130300b4aa3cb5b581@[213.6.51.119]>
2000-01-18 17:15   ` Ruben Malchow

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=00012013281100.00851@localhost.localdomain \
    --to=khendricks@ivey.uwo.ca \
    --cc=dje@watson.ibm.com \
    --cc=khendricks@admin.ivey.uwo.ca \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=linuxppc-user@lists.linuxppc.org \
    --cc=motho@gmx.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;
as well as URLs for NNTP newsgroup(s).