Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Wu Zhou <woodzltc@cn.ibm.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] New testcase to evaluate Fortran substring expression
Date: Sun, 03 Jul 2005 18:57:00 -0000	[thread overview]
Message-ID: <20050703185733.GI13811@nevyn.them.org> (raw)
In-Reply-To: <Pine.LNX.4.63.0506221044490.11343@wks190384wss.cn.ibm.com>

On Wed, Jun 22, 2005 at 10:53:35AM +0800, Wu Zhou wrote:
> Eli/Daniel and all,
> 
> Here is my new testcase to evaluate Fortran substring expression.  The 
> intention is to test whehter current GDB could correctly handle substring 
> expression evaluation of Fortran.  I tested it against g77-3.2.3 and 
> gfortran-4.0.0.  The last four tests failed for both configuration. 
> 
> I am also thinking of fixing these errors.  It is easy to fix str(exp:exp) 
> and str(:), but I am not sure how to fix str(:exp) and str(exp:) yet. Any 
> hints/tips on this?  TIA.

Let's hold this thought, OK?  I would rather add the tests when you
have a patch to fix them.  Alternatively PRs could be filed and the new
tests KFAILd, but I don't think that adds much value.

What's the problem with parsing (:exp)?  An exp can't be empty, and a
colon can't appear at the start of an exp.  I don't think (exp:) will
be any harder but my yacc is rusty.


-- 
Daniel Jacobowitz
CodeSourcery, LLC


  reply	other threads:[~2005-07-03 18:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-22  4:02 Wu Zhou
2005-07-03 18:57 ` Daniel Jacobowitz [this message]
2005-07-09  3:12   ` Wu Zhou
2005-07-14 23:46     ` Daniel Jacobowitz
2005-07-15  5:25       ` Wu Zhou
2005-07-15 11:49         ` Wu Zhou
2005-08-01  2:12           ` Daniel Jacobowitz
2005-08-01  4:44             ` Wu Zhou
2005-08-01  6:23               ` Mark Kettenis
2005-08-02  3:10               ` Daniel Jacobowitz
2005-08-02 10:16                 ` 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=20050703185733.GI13811@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sources.redhat.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