From: Nick Clifton <nickc@redhat.com>
To: gdb-patches@sourceware.org, Mike Frysinger <vapier@gentoo.org>
Subject: Re: RFA: AArch64 sim
Date: Thu, 19 Nov 2015 14:51:00 -0000 [thread overview]
Message-ID: <564DE205.10501@redhat.com> (raw)
In-Reply-To: <20151110073245.GN5154@vapier.lan>
[-- Attachment #1: Type: text/plain, Size: 805 bytes --]
Hi Mike,
Thanks for review.
> i've posted a patch to clean up the others. you should trim it from this
> one in the meantime.
OK - I have done that.
> i'm not seeing how this is cleaner. when you call sim_engine_halt, the
> code stops at that point. there is no returning/etc... afterwards.
>
> plus, when i look at some of these funcs, they only ever return READY.
> which leads to a lot of return code paths that are pointless.
Okey dokey - I have now refactored the code, removing the StatusCode
return value from lots of functions, and calling sim_engine_halt from
any location where a problem or break is encountered.
> you should scan the files and trim trailing whitespace while you're at it.
> sed -i -r 's:[[:space:]]+$::' *.[ch]
Also done.
Is this version OK ?
Cheers
Nick
[-- Attachment #2: aarch64.sim.patch.4.xz --]
[-- Type: application/x-xz, Size: 50424 bytes --]
next prev parent reply other threads:[~2015-11-19 14:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-28 12:25 Nick Clifton
2015-07-02 9:17 ` Andre Vieira
2015-07-02 13:53 ` Nicholas Clifton
2015-07-02 14:43 ` Andre Vieira
[not found] ` <55954DEE.50609@arm.com>
2015-07-02 15:20 ` Nicholas Clifton
2015-07-07 17:12 ` Mike Frysinger
2015-07-15 16:58 ` Nick Clifton
2015-07-16 15:19 ` Mike Frysinger
2015-07-17 14:10 ` Nicholas Clifton
2015-11-10 7:32 ` Mike Frysinger
2015-11-19 14:51 ` Nick Clifton [this message]
2015-11-20 9:13 ` Mike Frysinger
2015-11-20 10:56 ` Nick Clifton
2015-11-20 19:28 ` Mike Frysinger
2015-11-24 8:50 ` Nick Clifton
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=564DE205.10501@redhat.com \
--to=nickc@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=vapier@gentoo.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