From: Daniel Jacobowitz <drow@false.org>
To: Wu Zhou <woodzltc@cn.ibm.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA]: Patch to fix the SEGV error when printing f77 array element
Date: Thu, 09 Jun 2005 13:20:00 -0000 [thread overview]
Message-ID: <20050609132002.GB965@nevyn.them.org> (raw)
In-Reply-To: <Pine.LNX.4.63.0506091750410.27702@plinuxt18.cn.ibm.com>
On Thu, Jun 09, 2005 at 06:02:03PM +0800, Wu Zhou wrote:
> Daniel,
>
> I had cleaned up the patch to fix the SEGV error we discussed on gdb@ the
> days before and tested it on ppc64 arch with the latest CVS tree. It
> works ok. Please review and comment. Thanks.
Can you handle TYPE_CODE_PTR before the switch statement, instead?
Also, rather than default, you can probably check that the target type
of the pointer is TYPE_CODE_FUNC.
Do you feel up to adding our first compilable fortran test to the
testsuite?
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-06-09 13:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-09 11:00 Wu Zhou
2005-06-09 13:20 ` Daniel Jacobowitz [this message]
2005-06-10 7:37 ` Wu Zhou
2005-06-13 2:56 ` Daniel Jacobowitz
2005-06-13 8:10 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=20050609132002.GB965@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