public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Kaushik M Phatak <kphatak@gmail.com>
To: Mike Stump <mikestump@comcast.net>,
	dj@redhat.com, gcc-patches@gcc.gnu.org, 	nickc@redhat.com
Cc: "kaushik.phatak@kpit.com" <kaushik.phatak@kpit.com>
Subject: Re: [PATCH : RL78] Disable interrupts during hardware multiplication routines
Date: Thu, 07 Jan 2016 11:27:00 -0000	[thread overview]
Message-ID: <CAJA2CV2L82S+5QPr5F5cpv+2nfKVv-p01tKBiTKfJVUTeHn8Ow@mail.gmail.com> (raw)
In-Reply-To: <C6735D72-E033-470D-A8B2-1949D7A04AEE@comcast.net>

 Hi Mike,
Thanks for the feedback regarding the ABI.

I have added Nick and DJ in the loop to see if they can review this
patch posted last month,
https://gcc.gnu.org/ml/gcc-patches/2015-12/msg00733.html

Best Regards,
Kaushik


On Wed, Dec 9, 2015 at 10:23 PM, Mike Stump <mikestump@comcast.net> wrote:
> On Dec 9, 2015, at 1:53 AM, Kaushik M Phatak <kphatak@gmail.com> wrote:
>> Thank you for your feedback on my patch. (27 August 2015)
>> I have posted an updated patch for this issue,
>> https://gcc.gnu.org/ml/gcc-patches/2015-12/msg00733.html
>>
>> To reply to your question, the RL78 ABI does not specify anything for the MDUC
>> registers (Multiply/Divide).
>
> Three options then, either you're inventing the abi, then you decide and document what you did, you ask someone else what the abi is, or you follow the abi set by another compiler.  You cannot escape the abi.  As port contributor, you get to pick and make the best choice you can.  If you cannot, then I will pick, the registers are always saved.  Correspondingly, they are free to code-gen to be used by the compiler and optimizer.  If that's the case, then there should be no flag.  An os (aka target) that wants a different choice will responsible for adding in the code that can do something else.
>
> Let us know what your choice is.   Maybe Nick knows of a reason why the abi should be a certain way, Nick?  One we know the choice, we can then judge the patch to see if it implements the abi.

       reply	other threads:[~2016-01-07 11:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAJA2CV1y0Mk20KqgFbdFs19tyPCH7HvR_XGAwy=OyhYcgNLuWQ@mail.gmail.com>
     [not found] ` <C6735D72-E033-470D-A8B2-1949D7A04AEE@comcast.net>
2016-01-07 11:27   ` Kaushik M Phatak [this message]
2016-01-07 12:03     ` Nick Clifton
2016-01-12  7:21 Kaushik M Phatak
2016-01-12 12:20 ` Nick Clifton
2016-01-12 15:54 ` Mike Stump
2016-05-04 11:47   ` Kaushik Phatak
2016-05-09 11:46     ` Nick Clifton
  -- strict thread matches above, loose matches on Subject: below --
2015-06-05  6:44 Kaushik Phatak
2015-06-05  8:02 ` DJ Delorie
2015-08-27 13:14   ` Kaushik Phatak
2015-08-27 17:11     ` Mike Stump
2015-08-27 17:25     ` DJ Delorie
2015-12-07 12:36       ` Kaushik Phatak

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=CAJA2CV2L82S+5QPr5F5cpv+2nfKVv-p01tKBiTKfJVUTeHn8Ow@mail.gmail.com \
    --to=kphatak@gmail.com \
    --cc=dj@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=kaushik.phatak@kpit.com \
    --cc=mikestump@comcast.net \
    --cc=nickc@redhat.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).