Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: David Lecomber <david@allinea.com>
To: Wu Zhou <woodzltc@cn.ibm.com>
Cc: ramana.radhakrishnan@codito.com,
	Joel Brobecker <brobecker@adacore.com>,
	 gdb-patches@sources.redhat.com
Subject: Re: Suggest closing some old pending PRs
Date: Fri, 04 Nov 2005 14:48:00 -0000	[thread overview]
Message-ID: <1131100784.15860.42.camel@cpc2-oxfd8-3-0-cust199.oxfd.cable.ntl.com> (raw)
In-Reply-To: <Pine.LNX.4.63.0511041713060.22104@linux.site>

Hi Wu,
> - PR 648: Indexing is incorrect for printing elements of multi-dimensional 
> FORTRAN (g77) array
> 
> This is already fixed by David Lecomber patch (at least for DWARF reader).  
> And I had coded a testcase for that.  Could it get into mainline and gdb-6.4 branch?

I presume you mean the testcase ?  The actual code has been mainline for
18 months at least!

> - PR 822: Finding 'main' in languages other than C/C++
> 
> This PR is opened by Elena.  And I coded an intial patch to let gdb 
> set fortran main function to "MAIN__", which is used by both g77 and 
> gfortran.  Although it could not resolve the error completely.  It can let 
> gdb recoginize that the language is fortran after just loading the binary.
> Could I get this into the source tree and go on to implement the case 
> insensitive symbol lookup for Fortran?

There are other compilers - IBM XLF, Intel IFC, Portland pgf77, and
Pathscale EKO at the very least -- and I've never been able to find a
consistent behaviour that worked across the board - regexp or otherwise
matching!!  

Cheers
d.


  reply	other threads:[~2005-11-04 10:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-03  0:13 Joel Brobecker
2005-11-04  5:02 ` Ramana Radhakrishnan
2005-11-04 10:20 ` Wu Zhou
2005-11-04 11:56   ` Wu Zhou
2005-11-04 14:48     ` David Lecomber [this message]
2005-11-04 23:26       ` Wu Zhou

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=1131100784.15860.42.camel@cpc2-oxfd8-3-0-cust199.oxfd.cable.ntl.com \
    --to=david@allinea.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=ramana.radhakrishnan@codito.com \
    --cc=woodzltc@cn.ibm.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