From: Dimitar Dimitrov <dimitar@dinux.eu>
To: Mike Frysinger <vapier@gentoo.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v2 1/2] PRU Simulator port
Date: Tue, 14 Feb 2017 21:25:00 -0000 [thread overview]
Message-ID: <2742027.O7fFqzyZ6y@tpdeb> (raw)
In-Reply-To: <20170213053609.GF28432@vapier>
Hi Mike,
Thank you for the review.
On понеделник, 13 февруари 2017 г. 0:36:09 EET Mike Frysinger wrote:
> On 27 Dec 2016 23:25, Dimitar Dimitrov wrote:
> > The corresponding libgloss changes have not yet been mainlined.
> > The PRU patches are available here:
> > https://github.com/dinuxbg/gnupru/tree/for-next/patches/newlib-cygwin
>
> have you sent them to the mailing list ? i don't see them ...
> https://sourceware.org/ml/newlib/
I have not sent the newlib patches yet. My understanding is that I should first
mainline binutils and simulator, then GCC, and finally newlib.
...
> > --- /dev/null
> > +++ b/sim/pru/pru.h
> >
> > +/* (void)0 is a guard against using RD as a left-hand side value. */
> > +#define RD (void)0; rd_is_modified = 1; _RDVAL
>
> the standard way to handle (void)0 is with a do{...}while(0) loop
I'll do it.
>
> looks like you want to make a helper call macro anyways. something like
> #define FOO(x) do { ...; _RDVAL = x; } while (0)
My intention was to keep pru.isa simple and clear, resembling an ISA
specification. Compare
RD = RS1 & OP2
to
STORE_RD (RS1 & OP2)
>
> also, RD depends on _RDVAL which only exists inside a single func.
> this should be moved to interp.c i think for the one user.
I'll do it.
>
Regards,
Dimitar
prev parent reply other threads:[~2017-02-14 21:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-27 21:26 Dimitar Dimitrov
2016-12-27 21:26 ` [PATCH v2 2/2] Add testsuite for the PRU simulator port Dimitar Dimitrov
2017-02-13 5:36 ` Mike Frysinger
2017-01-14 7:05 ` [PATCH v2 1/2] PRU Simulator port Dimitar Dimitrov
2017-02-11 18:35 ` [PING] " Dimitar Dimitrov
2017-02-13 5:36 ` Mike Frysinger
2017-02-14 21:25 ` Dimitar Dimitrov [this message]
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=2742027.O7fFqzyZ6y@tpdeb \
--to=dimitar@dinux.eu \
--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