Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: thorpej@wasabisystems.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH/RFC] Get Alpha target to GDB_MULTI_ARCH_PARTIAL
Date: Sat, 20 Apr 2002 22:48:00 -0000	[thread overview]
Message-ID: <3CC2529E.9040900@cygnus.com> (raw)
In-Reply-To: <20020420095435.T1627@dr-evil.shagadelic.org>

Jason,

This and the fallout it causes can go in separatly.  Note the tweak.


> +++ alpha-tdep.h	19 Apr 2002 23:32:25 -0000
> @@ -0,0 +1,74 @@
> +/* Common target dependent code for GDB on Alpha systems.
> +   Copyright 1993, 1994, 1995, 1996, 1998, 1999, 2000, 2002 Free
> +   Software Foundation, Inc.
> +
> +   This file is part of GDB.
> +
> +   This program is free software; you can redistribute it and/or modify
> +   it under the terms of the GNU General Public License as published by
> +   the Free Software Foundation; either version 2 of the License, or
> +   (at your option) any later version.
> +
> +   This program is distributed in the hope that it will be useful,
> +   but WITHOUT ANY WARRANTY; without even the implied warranty of
> +   MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
> +   GNU General Public License for more details.
> +
> +   You should have received a copy of the GNU General Public License
> +   along with this program; if not, write to the Free Software
> +   Foundation, Inc., 59 Temple Place - Suite 330,
> +   Boston, MA 02111-1307, USA.  */

#ifndef ...
#define ...

You could also consider making much of this enum's (until the CPP stuff 
gets resolved).


> +/* Say how long (ordinary) registers are.  This is a piece of bogosity
> +   used in push_word and a few other places;  REGISTER_RAW_SIZE is the
> +   real way to know how big a register is.  */
> +#define ALPHA_REGISTER_SIZE 8
> +
> +/* Number of machine registers.  */
> +#define ALPHA_NUM_REGS 66
> +
> +/* Total amount of space needed to store our copies of the machine's
> +   register state.  */
> +#define ALPHA_REGISTER_BYTES (ALPHA_NUM_REGS * 8)
> +
> +/* Largest value REGISTER_RAW_SIZE can have.  */
> +#define ALPHA_MAX_REGISTER_RAW_SIZE 8
> +
> +/* Largest value REGISTER_VIRTUAL_SIZE can have.  */
> +#define ALPHA_MAX_REGISTER_VIRTUAL_SIZE 8
> +
> +/* Register numbers of various important registers.
> +   Note that most of these values are "real" register numbers,
> +   and correspond to the general registers of the machine,
> +   and FP_REGNUM is a "phony" register number which is too large
> +   to be an actual register number as far as the user is concerned
> +   but serves to get the desired value when passed to read_register.  */
> +
> +#define ALPHA_V0_REGNUM	     0  /* Function integer return value */
> +#define ALPHA_T7_REGNUM	     8  /* Return address register for OSF/1 __add* */
> +#define ALPHA_GCC_FP_REGNUM 15  /* Used by gcc as frame register */
> +#define ALPHA_A0_REGNUM     16  /* Loc of first arg during a subr call */
> +#define ALPHA_T9_REGNUM     23  /* Return address register for OSF/1 __div* */
> +#define ALPHA_T12_REGNUM    27  /* Contains start addr of current proc */
> +#define ALPHA_SP_REGNUM     30  /* Contains address of top of stack */
> +#define ALPHA_RA_REGNUM     26  /* Contains return address value */
> +#define ALPHA_ZERO_REGNUM   31  /* Read-only register, always 0 */
> +#define ALPHA_FP0_REGNUM    32  /* Floating point register 0 */
> +#define ALPHA_FPA0_REGNUM   48  /* First float arg during a subr call */
> +#define ALPHA_FPCR_REGNUM   63  /* Floating point control register */
> +#define ALPHA_PC_REGNUM     64  /* Contains program counter */
> +#define ALPHA_FP_REGNUM     65  /* Virtual frame pointer */
> +
> +/* The alpha has two different virtual pointers for arguments and locals.
> +   
> +   The virtual argument pointer is pointing to the bottom of the argument
> +   transfer area, which is located immediately below the virtual frame
> +   pointer. Its size is fixed for the native compiler, it is either zero
> +   (for the no arguments case) or large enough to hold all argument registers.
> +   gcc uses a variable sized argument transfer area. As it has
> +   to stay compatible with the native debugging tools it has to use the same
> +   virtual argument pointer and adjust the argument offsets accordingly.
> +   
> +   The virtual local pointer is localoff bytes below the virtual frame
> +   pointer, the value of localoff is obtained from the PDR.  */
> +#define ALPHA_NUM_ARG_REGS   6

Andrew


  parent reply	other threads:[~2002-04-21  5:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-20  9:54 Jason R Thorpe
2002-04-20 13:31 ` Jason R Thorpe
2002-04-20 13:37   ` Daniel Jacobowitz
2002-04-23 11:45   ` Michael Snyder
2002-04-20 17:10 ` Jason R Thorpe
2002-04-20 22:38 ` Andrew Cagney
2002-04-22  6:32   ` Joel Brobecker
2002-04-20 22:48 ` Andrew Cagney [this message]
2002-04-20 22:51 ` Andrew Cagney
2002-04-23 11:49 ` Michael Snyder

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=3CC2529E.9040900@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=thorpej@wasabisystems.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