public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: Andrew Bennett <Andrew.Bennett@imgtec.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Add micromips support to the MIPS simulator
Date: Tue, 24 Feb 2015 05:44:00 -0000	[thread overview]
Message-ID: <20150224054441.GA6655@vapier> (raw)
In-Reply-To: <0DA23CC379F5F945ACB41CF394B9827720F51185@LEMAIL01.le.imgtec.org>

[-- Attachment #1: Type: text/plain, Size: 1869 bytes --]

On 21 Jan 2015 12:44, Andrew Bennett wrote:

the igen files i pretty much skimmed over

> --- a/sim/mips/Makefile.in
> +++ b/sim/mips/Makefile.in
>
>  support.o: sim-main.h support.c $(SIM_EXTRA_DEPS)
>  idecode.o: sim-main.h idecode.c $(SIM_EXTRA_DEPS)
>  itable.o: sim-main.h itable.c $(SIM_EXTRA_DEPS)
> -m16run.o: sim-main.h m16_idecode.h m32_idecode.h $(SIM_EXTRA_DEPS)
> +m16run.o: sim-main.h m16_idecode.h m32_idecode.h m16run.c $(SIM_EXTRA_DEPS)
> +micromipsrun.o: sim-main.h micromips16_idecode.h micromips32_idecode.h \
> +	micromips_m32_idecode.h micromipsrun.c $(SIM_EXTRA_DEPS)

pretty sure you don't need any of this hand maintained dependency info anymore.  
can you please try deleting it all instead ?

> --- a/sim/mips/configure.ac
> +++ b/sim/mips/configure.ac
>
> +      *:*micromips32*:*)
> +	# Run igen thrice, once for micromips32, once for micromips16,
> +        # and once for m32.
> +	ws="micromips_m32 micromips16 micromips32"

indentation is broken slightly on the second comment line.  seems to come up a 
few times ... you should fix them all.

> --- a/sim/mips/interp.c
> +++ b/sim/mips/interp.c
>  
> +/* microMIPS ISA mode */
> +int isa_mode;

why is this a global instead of being part of the sim state ?

the comment also needs tweaking to match GNU style

> --- /dev/null
> +++ b/sim/mips/micromipsrun.c
>
> +/*  Run function for the micromips simulator
> +
> +    Copyright (C) 2005-2013 Free Software Foundation, Inc.

years needs updating

> +    This file is part of GDB, the GNU debugger.

i think you mean:
	This file is part of the GNU simulators.

> +#define SD sd
> +#define CPU cpu

unused ?

> +void
> +sim_engine_run (SIM_DESC sd, int next_cpu_nr, int nr_cpus, int signal);

you should include sim-engine.h instead of declaring the prototype yourself
-mike

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2015-02-24  5:44 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-21 12:44 Andrew Bennett
2015-02-24  5:44 ` Mike Frysinger [this message]
2015-08-27 15:05   ` Andrew Bennett
2015-09-11 10:24     ` Andrew Bennett
2016-01-01  7:07       ` Joel Brobecker
2016-01-05 14:40         ` Andrew Bennett
2016-01-06  5:43           ` Joel Brobecker
2015-09-17  4:42     ` Mike Frysinger
2015-09-25 12:06       ` Andrew Bennett
2015-09-25 14:07         ` Mike Frysinger
2015-09-25 20:22           ` Andrew Bennett
2015-09-25 20:57             ` Mike Frysinger
2016-01-12 23:01             ` Maciej W. Rozycki
2016-01-15 16:22               ` Andrew Bennett
2016-01-15 17:45                 ` Mike Frysinger

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=20150224054441.GA6655@vapier \
    --to=vapier@gentoo.org \
    --cc=Andrew.Bennett@imgtec.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).