Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: gdb-patches@sourceware.org
Cc: Joel Brobecker <brobecker@adacore.com>,
	Stephen.Kilbane@analog.com, Stuart.Henderson@analog.com,
	David.Gibson@analog.com
Subject: Re: [PATCH] sim: add --map-info option
Date: Tue, 14 Dec 2010 18:34:00 -0000	[thread overview]
Message-ID: <201012141333.11297.vapier@gentoo.org> (raw)
In-Reply-To: <201012141016.23030.vapier@gentoo.org>

[-- Attachment #1: Type: Text/Plain, Size: 1280 bytes --]

On Tuesday, December 14, 2010 10:16:21 Mike Frysinger wrote:
> On Tuesday, December 14, 2010 02:35:58 Joel Brobecker wrote:
> > How about:
> >     
> >     char *
> >     io_map_to_str (unsigned nr_map)
> >     {
> 
> but this idea is good, so i'll implement it

ah, someone already beat us to it.  there's a map_to_str() func.

> > > +		sim_io_printf (sd, " map ");
> > > +		if (mapping->space != 0)
> > > +		  sim_io_printf (sd, "0x%lx:", (long) mapping->space);
> > > +		sim_io_printf (sd, "0x%08lx", (long) mapping->base);
> > > +		if (mapping->level != 0)
> > > +		  sim_io_printf (sd, "@0x%lx", (long) mapping->level);
> > > +		sim_io_printf (sd, ",0x%lx", (long) mapping->nr_bytes);
> > > +		modulo = mapping->mask + 1;
> > > +		if (modulo != 0)
> > > +		  sim_io_printf (sd, "%%0x%lx", (long) modulo);
> > 
> > I don't understand the necessity to cast everything to long. Can you
> > explain?
> 
> it's taken largely unchanged from the OPTION_MEMORY_INFO case block just
> above my new block.  i guess my new code could review the types and do it
> right.

ok, some of the (long) casts are necessary.  specifically, the ones who have a 
type of "unsigned_word" as those depend on the target bitness (which could be 
16, 32, or 64).
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2010-12-14 18:34 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-01 16:15 Mike Frysinger
2010-12-14  7:36 ` Joel Brobecker
2010-12-14 15:17   ` Mike Frysinger
2010-12-14 18:34     ` Mike Frysinger [this message]
2010-12-14 18:50       ` Pedro Alves
2010-12-14 19:03         ` Mike Frysinger
2010-12-14 19:12           ` Pedro Alves
2010-12-14 19:30             ` Mike Frysinger
2010-12-15  4:54     ` Joel Brobecker
2010-12-15 11:50       ` Mike Frysinger
2010-12-14 18:37 ` [PATCH v2] " Mike Frysinger
2010-12-15  5:02   ` Joel Brobecker
2010-12-15 11:21     ` Mike Frysinger
2010-12-15 11:48       ` Joel Brobecker
2010-12-15 12:02         ` [toolchain-devel] " Mike Frysinger
2010-12-15 13:16           ` Eli Zaretskii

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=201012141333.11297.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=David.Gibson@analog.com \
    --cc=Stephen.Kilbane@analog.com \
    --cc=Stuart.Henderson@analog.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    /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