Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: Denis Joseph Barrow <DJBARROW@de.ibm.com>
Cc: gdb-patches@sourceware.cygnus.com, s390-patches@gnu.org,
	Martin Schwidefsky <schwidefsky@de.ibm.com>,
	Christoph Arenz <ARENZ@de.ibm.com>
Subject: Re: New gdb 31 & 64 bit patches for S/390
Date: Thu, 05 Jul 2001 10:11:00 -0000	[thread overview]
Message-ID: <3B449AC6.50801@cygnus.com> (raw)
In-Reply-To: <OFD9727B4C.E2B8843F-ONC1256A80.003B52E2@de.ibm.com>

> It'll be at least two weeks before I can go & update this stuff owing to
> other commitments.
> The asm/types.h in my opinion is currently needed, Andrew if you think it
> isn't, a
> config/arch/hosttypes.h with definitions for u8 u16 & u32 etc. definitions
> should be introduced  for all archs
> IMO bfd_btye etc. as per previous suggestion simply doesn't cut mustard.


I don't think u8, u16, ... are needed.  As I noted:


> In the past it has been suggested that types like _u32, _u8 etc would
> allow the user to exactly describe structures and hence allow the
> programmer to exactly describe structure layout.  Unfortunatly, that
> won't work since allignment (and hence packing) also varies between
> hosts.
> 
> If you need to read structures from memory you can use functions like:
> 
>      LONGEST read_memory_integer (CORE_ADDR memaddr, int len);
>      ULONGEST read_memory_unsigned_integer (CORE_ADDR memaddr, int len);
> 
> If you already have the memory local then:
> 
>      LONGEST extract_signed_integer (void *, int);
>      ULONGEST extract_unsigned_integer (void *, int);
> 
> will do the trick.


All other targets have managed to get things working using just the above.

	Andrew


  parent reply	other threads:[~2001-07-05 10:11 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-05  3:57 Denis Joseph Barrow
2001-07-05 10:11 ` Andrew Cagney
2001-07-05 10:11 ` Andrew Cagney [this message]
     [not found] <OFEFF0AD94.761C34C1-ONC1256AB6.005503EE@de.ibm.com>
2001-08-28 16:33 ` Daniel Jacobowitz
2001-09-05 21:45   ` Andrew Cagney
  -- strict thread matches above, loose matches on Subject: below --
2001-08-15  2:22 Denis Joseph Barrow
2001-08-15  9:03 ` Andrew Cagney
2001-08-15  9:54 ` Andrew Cagney
2001-08-13  9:47 Denis Joseph Barrow
2001-08-13  3:06 Denis Joseph Barrow
2001-08-13  9:31 ` Andrew Cagney
2001-07-06  2:31 Denis Joseph Barrow
2001-07-05 10:24 Denis Joseph Barrow
2001-07-05 12:46 ` Andrew Cagney
2001-07-08  0:53   ` Eli Zaretskii
2001-07-08 19:23     ` Andrew Cagney
2001-07-05  9:19 Denis Joseph Barrow
2001-07-05 12:36 ` Andrew Cagney
2001-07-05  9:15 Denis Joseph Barrow
2001-07-05  5:04 Denis Joseph Barrow
2001-07-05  3:12 Denis Joseph Barrow
2001-06-18  3:32 DJBARROW
     [not found] <C1256A02.00573066.00@d12mta09.de.ibm.com>
2001-03-01 10:39 ` Nick Clifton
2001-03-01  2:50 DJBARROW
2001-03-01 10:37 ` Nick Clifton
2001-02-27 12:39 DJBARROW
2001-02-28 16:13 ` Nick Clifton
2001-06-15  9:53 ` Andrew Cagney
2001-06-15 11:46   ` Andreas Jaeger
2001-06-15 12:22     ` Andrew Cagney
2001-07-04 11:25 ` Andrew Cagney
2001-07-04 21:02 ` Andrew Cagney
2001-07-04 21:02 ` Andrew Cagney
2001-07-04 21:02 ` Andrew Cagney

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=3B449AC6.50801@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=ARENZ@de.ibm.com \
    --cc=DJBARROW@de.ibm.com \
    --cc=gdb-patches@sourceware.cygnus.com \
    --cc=s390-patches@gnu.org \
    --cc=schwidefsky@de.ibm.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