Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Andrew Burgess" <aburgess@broadcom.com>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: RE: [PATCH] Multi-dimensional Fortran arrays issue PR11104
Date: Wed, 17 Nov 2010 08:45:00 -0000	[thread overview]
Message-ID: <89AE14E37D740B4796DC14566DF6325ECB7F8F140B@SJEXCHCCR02.corp.ad.broadcom.com> (raw)
In-Reply-To: <89AE14E37D740B4796DC14566DF6325ECB7F1F6E81@SJEXCHCCR02.corp.ad.broadcom.com>

Hi,

If anyone has the time please could this patch be reviewed. I realise that there's an overlap with some of the code currently in the Archer VLA branch, but as this keeps some of the bounds checking in place I hoped this might be acceptable.
The revised patch includes the ChangeLog entry as text ahead of the patch content, I've since been told that's not the preferred format and will split it out if that would make people life easier.
I'm happy to make any changes requested.

At the time I submitted the patch I built & tested on x86-64 with no regressions.

Thanks,

Andrew




> -----Original Message-----
> From: gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] On Behalf Of Andrew Burgess
> Sent: 19 October 2010 17:23
> To: gdb-patches@sourceware.org
> Cc: Jan Kratochvil
> Subject: RE: [PATCH] Multi-dimensional Fortran arrays issue PR11104
> 
> Jan, thanks for taking the time to look through the original patch.
> 
> > On 18 October 2010 22:20, Jan Kratochvil wrote:
> >
> > multi-dim.tar.bz2 (.exp + .f90) should be submitted as a normal
> patch,
> 
> Done.
> 
> >
> > ChangeLog should be submitted as a text, not as patch.
> >
> 
> I've included the ChangeLog entries within the patch file as plain text
> before the start of that patch content, this seems to be what others
> have done, but I can pull them out if this is not correct.
> 
> > There are several minor issues with formatting:
> > 	http://www.gnu.org/prep/standards/
> 
> I believe that these have all been addressed. If I've still missed
> anything then please let me know.
> 
> >
> > This functionality is implemented by archer-jankratochvil-vla from:
> > 	http://sourceware.org/gdb/wiki/ArcherBranchManagement
> >
> > (out of bounds access is not detected by the VLA patchset though)
> >
> > which is currently not submitted for a review as it has more
> > prerequisites.
> 
> As I had the patch pretty much ready I cleaned it up anyway. I guess
> it's up to someone else to decide to merge this or wait for the Archer
> branch to land.
> 
> Thanks,
> 
> Andrew
> 
> 



  reply	other threads:[~2010-11-17  8:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-16 17:26 Andrew Burgess
2010-10-18  7:53 ` Andrew Burgess
2010-10-18 21:20   ` Jan Kratochvil
2010-10-19 16:23     ` Andrew Burgess
2010-11-17  8:45       ` Andrew Burgess [this message]
2010-11-22  7:10         ` Jan Kratochvil
2010-11-23  8:02         ` Jan Kratochvil
2010-11-23 10:04           ` Andrew Burgess
2010-11-23 17:23             ` Jan Kratochvil
2010-11-23 19:10               ` Jan Kratochvil
2010-10-18 21:21   ` Jan Kratochvil

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=89AE14E37D740B4796DC14566DF6325ECB7F8F140B@SJEXCHCCR02.corp.ad.broadcom.com \
    --to=aburgess@broadcom.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