public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Claudiu Zissulescu <Claudiu.Zissulescu@synopsys.com>
To: Sandra Loosemore <sandra@codesourcery.com>,
	"gcc-patches@gcc.gnu.org"	<gcc-patches@gcc.gnu.org>
Cc: "Francois.Bedard@synopsys.com" <Francois.Bedard@synopsys.com>,
	"andrew.burgess@embecosm.com" <andrew.burgess@embecosm.com>
Subject: RE: [PATCH 1/3] [ARC] Automatic context save/restore for regular interrupts.
Date: Wed, 26 Apr 2017 13:15:00 -0000	[thread overview]
Message-ID: <098ECE41A0A6114BB2A07F1EC238DE896661831A@de02wembxa.internal.synopsys.com> (raw)
In-Reply-To: <58FF6D3F.7020707@codesourcery.com>

> > +@item -mirq-ctrl-saved="REGS"
> 
> Use @var{regs} instead of REGS.  I assume the quotes are part of the
> literal syntax?

In fact here we should have a register range (e.g., -mirq-ctrl-saved=r0-r9).

> > +lp_count.  Registers needs to be specified as ranges such as "r0-r3".
> > +A register range always starts with r0.  Registers blink and lp_count
> > +can be specified individually.
> 
> You're contradicting yourself here:  you say that registers need to be
> specified as ranges, and then you say that some registers can be
> specified individually.  Can you come up with a better explanation of
> the syntax?  E.g., is it possible to specify multiple registers without
> using a range?  Or do you specify the option multiple times in that case?
> 

Blink (r31) and lp_count (r60) are special registers. The range can go from r0 up to r29.  Thus, the option is a sequence made of a register range starting with r0 to r29, and optional two individual registers: blink (r31) and lp_count (r60). Hence, such an option looks like this:
	-mirq-ctrl-saved=r0-r29,blink,lp_count


Thanks,
Claudiu

  reply	other threads:[~2017-04-26 13:11 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-25 13:06 [PATCH 0/3] [ARC] New features Claudiu Zissulescu
2017-04-25 13:21 ` [PATCH 3/3] [ARC] Add support for advanced mpy/mac instructions Claudiu Zissulescu
2017-05-08 15:10   ` Andrew Burgess
2017-05-09 14:42     ` Claudiu Zissulescu
2017-04-25 13:27 ` [PATCH 2/3] [ARC] Fast interrupts support Claudiu Zissulescu
2017-04-25 15:54   ` Sandra Loosemore
2017-04-26 13:14     ` Claudiu Zissulescu
2017-04-25 13:29 ` [PATCH 1/3] [ARC] Automatic context save/restore for regular interrupts Claudiu Zissulescu
2017-04-25 15:46   ` Sandra Loosemore
2017-04-26 13:15     ` Claudiu Zissulescu [this message]
2017-05-05 11:05     ` [PATCH 0/2] [ARC] New features (updated) Claudiu Zissulescu
2017-05-05 11:05       ` [PATCH 1/2] Automatic context save/restore for regular interrupts Claudiu Zissulescu
2017-05-08 14:50         ` Andrew Burgess
2017-05-09 14:24           ` Claudiu Zissulescu
2017-05-05 11:23       ` [PATCH 2/2] Fast interrupts support Claudiu Zissulescu
2017-05-08 14:54         ` Andrew Burgess
2017-05-09 14:25           ` Claudiu Zissulescu

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=098ECE41A0A6114BB2A07F1EC238DE896661831A@de02wembxa.internal.synopsys.com \
    --to=claudiu.zissulescu@synopsys.com \
    --cc=Francois.Bedard@synopsys.com \
    --cc=andrew.burgess@embecosm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=sandra@codesourcery.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).