public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeffrey A Law <law@cygnus.com>
To: Mark Klein <mklein@dis.com>
Cc: gcc@gcc.gnu.org
Subject: Re: MPE Port
Date: Thu, 30 Sep 1999 18:02:00 -0000	[thread overview]
Message-ID: <28316.936780362@upchuck.cygnus.com> (raw)
Message-ID: <19990930180200.gOcnPEBeLvFtdBcZZhFLV7MptOgMEW_HDEVXskBfuOo@z> (raw)
In-Reply-To: <4.1.19990906102604.00c75df0@garfield.dis.com>

  In message < 4.1.19990906102604.00c75df0@garfield.dis.com >you write:
  > Explanation:
  > 
  > Handle certain MPE nuances such as bcopy() not being able to do
  > overlapped moves. Invoke millicode instead of bcopy().
  > 
  > Sat Sep  4 18:00:00 PDT 1999 Mark Klein (mklein@dis.com)
  > 
  >         * pa/xm-pampeix.h: New file for the MPE port.
  > 
  > *** egcs/gcc/config/pa/xm-pampeix.h	Wed Dec 31 16:00:00 1969
  > --- egcs-ss/gcc/config/pa/xm-pampeix.h	Mon Aug 30 21:52:06 1999
  > ***************
  > *** 0 ****
  > --- 1,109 ----
  > + /* Configuration for GNU C-compiler for PA-RISC.
  > +    Copyright (C) 1998 Free Software Foundation, Inc.
  > +    Contributed by Mark Klein (mklein@dis.com)           
Copyright date.

  > + You should have received a copy of the GNU General Public License
  > + along with GNU CC; see the file COPYING.  If not, write to
  > + the Free Software Foundation, 675 Mass Ave, Cambridge, MA 02139, USA.  */
Address update.

  > + /* Use System V memory functions.  */
  > + #ifndef _BCMP_DEFINED
  > + #define _BCMP_DEFINED
  > + #ifndef BSTRING
  > + #define BSTRING
  > + #endif
  > + #if !defined(bcopy) && !defined(HAS_BCOPY)
  > + inline static void
  > + bcopy(const void *src,void *dst,int len) {
  > + 	asm volatile (
  > + 			".import $$lr_unk_unk,MILLICODE;	
  > + 			copy %0, %%r26;
  > + 			copy %1, %%r25;
  > + 			bl $$lr_unk_unk,%%r31;
  > + 			copy %2, %%r24"
  > + 					:
  > + 					: "r" (src),
  > + 					  "r" (dst),
  > + 					  "r" (len)
  > + 					: "%r24",
  > + 					  "%r25",
  > + 					  "%r26",
  > + 					  "%r31");
  > + }
  > + #endif
Ouch.  I presume you do not have a function memcpy, memmove or similar routine?

I'd like to hold off on that fragment for now -- we may be able to make the
entire point moot by having libiberty available for host and build machines.


  > + #define STARTFILE_SPEC		""
?!?  This does not belong in an xm.h file.


jeff

  reply	other threads:[~1999-09-30 18:02 UTC|newest]

Thread overview: 96+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-09-06 10:40 Mark Klein
1999-09-08  1:49 ` Jeffrey A Law [this message]
1999-09-08 20:31   ` Mark Klein
1999-09-30 18:02     ` Mark Klein
1999-09-30 18:02   ` Jeffrey A Law
1999-09-30 18:02 ` Mark Klein
  -- strict thread matches above, loose matches on Subject: below --
1999-09-07  8:42 Mark Klein
1999-09-30 18:02 ` Mark Klein
1999-10-25 22:41 ` Jeffrey A Law
1999-10-26  7:03   ` Mark Klein
1999-10-26 19:12     ` Jeffrey A Law
1999-10-26 19:52       ` Mark Klein
1999-10-31 23:35         ` Mark Klein
1999-10-31 23:35       ` Jeffrey A Law
1999-10-31 23:35     ` Mark Klein
1999-10-31 23:35   ` Jeffrey A Law
1999-09-06 10:40 Mark Klein
1999-09-30 18:02 ` Mark Klein
1999-09-06 10:40 Mark Klein
1999-09-30 18:02 ` Mark Klein
1999-09-06 10:40 Mark Klein
1999-09-08  1:41 ` Jeffrey A Law
1999-09-08  6:37   ` Mark Klein
1999-09-30 18:02     ` Mark Klein
1999-09-30 18:02   ` Jeffrey A Law
1999-09-30 18:02 ` Mark Klein
1999-09-06 10:40 Mark Klein
1999-09-08  1:39 ` Jeffrey A Law
1999-09-08  6:35   ` Mark Klein
1999-09-15  2:52     ` Jeffrey A Law
1999-09-15  8:26       ` Mark Klein
1999-09-30 18:02         ` Mark Klein
1999-09-30 18:02       ` Jeffrey A Law
1999-09-30 18:02     ` Mark Klein
1999-09-30 18:02   ` Jeffrey A Law
1999-09-30 18:02 ` Mark Klein
1999-09-06 10:40 Mark Klein
1999-09-07  2:38 ` Jeffrey A Law
1999-09-07  6:39   ` Mark Klein
1999-09-08  0:45     ` Jeffrey A Law
1999-09-08 20:04       ` Mark Klein
1999-09-15  2:47         ` Jeffrey A Law
1999-09-15  8:32           ` Mark Klein
1999-09-30 18:02             ` Mark Klein
1999-09-30 18:02           ` Jeffrey A Law
1999-10-09 20:18           ` Mark Klein
1999-10-14  4:03             ` Jeffrey A Law
1999-10-14  7:20               ` Mark Klein
1999-10-14 10:45                 ` Jeffrey A Law
1999-10-14 11:05                   ` Mark Klein
1999-10-31 23:35                     ` Mark Klein
1999-10-31 23:35                   ` Jeffrey A Law
1999-10-31 23:35                 ` Mark Klein
1999-10-31 23:35               ` Jeffrey A Law
1999-10-31 23:35             ` Mark Klein
1999-11-08 19:34           ` Mark Klein
1999-11-08 19:54             ` Jeffrey A Law
1999-11-09  6:52               ` Mark Klein
1999-11-30 23:37                 ` Mark Klein
1999-11-30 23:37               ` Jeffrey A Law
1999-11-30 23:37             ` Mark Klein
1999-09-30 18:02         ` Mark Klein
1999-09-30 18:02       ` Jeffrey A Law
1999-09-30 18:02     ` Mark Klein
1999-09-30 18:02   ` Jeffrey A Law
1999-09-30 18:02 ` Mark Klein
1999-09-06 10:40 Mark Klein
1999-09-30 18:02 ` Mark Klein
1999-09-06 10:40 Mark Klein
1999-09-30 18:02 ` Mark Klein
1999-10-25 22:32 ` Jeffrey A Law
1999-10-26  6:51   ` Mark Klein
1999-10-26 19:05     ` Jeffrey A Law
1999-10-26 19:21       ` Mark Klein
1999-10-31 23:35         ` Mark Klein
1999-10-31 23:35       ` Jeffrey A Law
1999-10-31 23:35     ` Mark Klein
1999-10-31 23:35   ` Jeffrey A Law
1999-09-06 10:40 Mark Klein
1999-09-08  1:40 ` Jeffrey A Law
1999-09-30 18:02   ` Jeffrey A Law
1999-09-30 18:02 ` Mark Klein
1999-09-06 10:39 Mark Klein
1999-09-30 18:02 ` Mark Klein
1999-09-06 10:39 Mark Klein
1999-09-07  3:20 ` Jeffrey A Law
1999-09-07  6:46   ` Mark Klein
1999-09-08  0:43     ` Jeffrey A Law
1999-09-30 18:02       ` Jeffrey A Law
1999-09-30 18:02     ` Mark Klein
1999-09-30 18:02   ` Jeffrey A Law
1999-09-30 18:02 ` Mark Klein
1999-09-06 10:39 Mark Klein
1999-09-30 18:02 ` Mark Klein
1999-08-27 17:20 HARD_REGNO_MODE_OK on PA-RISC (revisited) Mark Klein
1999-08-29  3:19 ` Jeffrey A Law
1999-09-06 10:39   ` MPE Port Mark Klein
1999-09-30 18:02     ` Mark Klein

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=28316.936780362@upchuck.cygnus.com \
    --to=law@cygnus.com \
    --cc=gcc@gcc.gnu.org \
    --cc=mklein@dis.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).