Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@imgtec.com>
To: Bhushan Attarde <Bhushan.Attarde@imgtec.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
	Matthew Fortune	<Matthew.Fortune@imgtec.com>,
	James Hogan <James.Hogan@imgtec.com>,
	Andrew Bennett <Andrew.Bennett@imgtec.com>,
	Jaydeep Patil <Jaydeep.Patil@imgtec.com>
Subject: Re: [PATCH 0/24] MIPS: Add support for reconfigurable FPR size, MIPS MSA and MIPSR6,support
Date: Mon, 25 Jul 2016 13:58:00 -0000	[thread overview]
Message-ID: <alpine.DEB.2.00.1607221502450.4076@tp.orcam.me.uk> (raw)
In-Reply-To: <9D3E5517712EFA419C6B9C50EDC1282CAA1FA536@PUMAIL01.pu.imgtec.org>

Bhushan,

 First of all thank you for your submission, and also apologies for the 
long RTT.

 Now a couple of general questions/notes:

1. Can you please reformat the e-mails with patches such that they can be 
   readily fed to Git?  Using `git format-patch' would be the usual way,
   although of course feel free to do it however you like.  In the form 
   you posted they have leading blanks across descriptions which do not
   work well with `git am' (see also 
   <https://sourceware.org/gdb/wiki/ContributionChecklist>).

2. You haven't told us how you verified these changes.  Have you run any 
   regression testing at all?  If so, the which targets have you tested?
   Also please make sure that you at least build changes which affect
   generic files with `--enable-targets=all'.

3. Some changes touch files in the include/ and opcodes/ subdirectories.  
   These (except for include/gdb/) are maintained as a part of the 
   binutils project and need to be posted to the relevant mailing list, 
   which is <binutils@sourceware.org>.  I'll review the relevant parts in 
   this round with an appropriate `Cc' added, but please pay attention to
   have the binutils mailing list included where appropriate in the 
   submission.  In fact especially changes to opcodes/ and include/opcode/ 
   appear self-contained and largely independent from the GDB part of the
   containing patch, so they may best be split off and submitted to the
   binutils project first.  More on this in replies to individual patches.

>     1. Handles run-time reconfigurable FPR size. MIPS revision 2 onwards 
> MIPS32
> 
>     and MIPS64 both can have either 32-bit or 64-bit FPRs. This is decided
> 
>     based on the values of CP1.FIR.F64, CP0.SR.FR and CP0.Config5.FRE bits.
> 
>     Patch 1 to patch 12 in the series handles this property. This work is
> based
> 
>     on the patch submitted earlier by Maciej W. Rozycki. Please refer to
> 
>     https://sourceware.org/ml/gdb-patches/2012-06/msg00201.html for details.
> So
> 
>     this series includes his patch (updated to GDB 7.11 release version) as
> the
> 
>     [patch 1] of the series.

 For the record please note that the availability of CP0.Status.FR goes 
back to the MIPS III ISA and therefore all 64-bit MIPS processors have it.
So if you need to determine the presence of this bit, then the algorithm 
conceptually is (isa_is_64bit || CP1.FIR.F64).

 This introduction is not going to end up in our Git repository, but for 
the sake of people's confusion avoidance please update it in patch 
resubmission.

 Finally please note that I cannot approve changes outside the MIPS 
target, but to speed up the process I'll check them regardless to see if 
there are any obvious issues.  You'll still have to seek a global 
maintainer's approval for those changes though.

  Maciej


       reply	other threads:[~2016-07-25 13:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <9D3E5517712EFA419C6B9C50EDC1282CAA1FA536@PUMAIL01.pu.imgtec.org>
2016-07-25 13:58 ` Maciej W. Rozycki [this message]
2016-10-04 17:48   ` Pedro Alves
2016-10-04 18:14     ` Maciej W. Rozycki

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=alpine.DEB.2.00.1607221502450.4076@tp.orcam.me.uk \
    --to=macro@imgtec.com \
    --cc=Andrew.Bennett@imgtec.com \
    --cc=Bhushan.Attarde@imgtec.com \
    --cc=James.Hogan@imgtec.com \
    --cc=Jaydeep.Patil@imgtec.com \
    --cc=Matthew.Fortune@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