Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jiri Smid <smid@suse.cz>
To: gdb-patches@sources.redhat.com
Cc: ac131313@cygnus.com
Subject: [RFA]: config stuff for x86_64
Date: Wed, 25 Jul 2001 00:07:00 -0000	[thread overview]
Message-ID: <s8vn15to5b6.fsf@naga.suse.cz> (raw)

Hello,

  I am working on new target - AMD 64 bit processor and I want to start
with committing changes to mainline.

Andrew Cagney <ac131313@cygnus.com> writes:

> If you can then just submit a two line minimal patch (to config say?) I'll have
> a reason to get you into the write after approval list.

Here is the first patch to config files:

Index: gdb/ChangeLog
===================================================================
RCS file: /cvs/src/src/gdb/ChangeLog,v
retrieving revision 1.1511
diff -c -3 -p -r1.1511 ChangeLog
*** ChangeLog	2001/07/24 21:51:36	1.1511
--- ChangeLog	2001/07/25 07:03:48
***************
*** 1,3 ****
--- 1,8 ----
+ 2001-07-25  Jiri Smid	<smid@suse.cz>
+ 
+ 	* configure.host: Recognize x86_64-*-linux*.
+ 	* configure.tgt: Likewise.
+ 
  2001-07-24  Stephen P. Smith <ischis2@home.com>
  
  	* MAINTAINERS (Stephen P. Smith): Added to write after approval 
Index: gdb/configure.host
===================================================================
RCS file: /cvs/src/src/gdb/configure.host,v
retrieving revision 1.23
diff -c -3 -p -r1.23 configure.host
*** configure.host	2001/07/10 20:41:54	1.23
--- configure.host	2001/07/25 07:03:48
*************** mips*)			gdb_host_cpu=mips ;;
*** 20,25 ****
--- 20,26 ----
  powerpc*)		gdb_host_cpu=powerpc ;;
  sparc64)		gdb_host_cpu=sparc ;;
  s390*)			gdb_host_cpu=s390 ;;
+ x86_64*)		gdb_host_cpu=i386 ;;
  *)			gdb_host_cpu=$host_cpu ;;
  
  esac
*************** xscale-*-*)		gdb_host=arm ;;
*** 162,166 ****
--- 163,169 ----
  vax-*-bsd*)		gdb_host=vaxbsd ;;
  vax-*-ultrix2*)		gdb_host=vaxult2 ;;
  vax-*-ultrix*)		gdb_host=vaxult ;;
+ 
+ x86_64-*-linux*)	gdb_host=x86_64 ;;
  
  esac
Index: gdb/configure.tgt
===================================================================
RCS file: /cvs/src/src/gdb/configure.tgt,v
retrieving revision 1.34
diff -c -3 -p -r1.34 configure.tgt
*** configure.tgt	2001/07/19 05:10:38	1.34
--- configure.tgt	2001/07/25 07:03:48
*************** s390*)			gdb_target_cpu=s390 ;;
*** 27,32 ****
--- 27,33 ----
  strongarm*)		gdb_target_cpu=arm ;;
  xscale*)		gdb_target_cpu=arm ;;
  v850*)			gdb_target_cpu=v850 ;;
+ x86_64*)		gdb_target_cpu=i386 ;;
  *)			gdb_target_cpu=$target_cpu ;;
  
  esac
*************** v850*-*-*)		gdb_target=v850
*** 312,317 ****
--- 313,321 ----
  			;;
  
  # OBSOLETE w65-*-*)		gdb_target=w65 ;;
+ 
+ x86_64-*-linux*)	gdb_target=x86_64
+  		configdirs="${configdirs} gdbserver" ;;
  
  z8k-*-coff*)		gdb_target=z8k ;;
  



-- 
Jiri Smid

---------------------------------------------------------------------
SuSE CR, s.r.o.                                 e-mail: smid@suse.cz
Drahobejlova 27                                tel:+420 2 83095 373
190 00 Praha 9                                 fax:+420 2 83095 374
Ceska republika                                http://www.suse.cz


             reply	other threads:[~2001-07-25  0:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-25  0:07 Jiri Smid [this message]
2001-07-25 11:10 ` Andrew Cagney
2001-07-25 11:44   ` Tom Tromey

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=s8vn15to5b6.fsf@naga.suse.cz \
    --to=smid@suse.cz \
    --cc=ac131313@cygnus.com \
    --cc=gdb-patches@sources.redhat.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