This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: [RFA/sparc] pb doing next over struct-return function
- From: "Eli Zaretskii" <eliz at gnu dot org>
- To: Mark Kettenis <kettenis at gnu dot org>
- Cc: brobecker at adacore dot com, gdb-patches at sources dot redhat dot com
- Date: Tue, 23 Nov 2004 13:29:40 +0200
- Subject: Re: [RFA/sparc] pb doing next over struct-return function
- References: <20041123053544.GM1141@adacore.com> <200411230833.iAN8X6Ru027549@juw15.nfra.nl>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> Date: Tue, 23 Nov 2004 09:33:06 +0100 (CET)
> From: Mark Kettenis <kettenis@gnu.org>
> CC: gdb-patches@sources.redhat.com
>
> Return non-zero if the instruction at PC is an "unimp" instruction.
> ^^^^^^^^ ^
>
> + else
> + {
> + /* There is no debugging information for this function to
> + help us determine whether this function returns a struct
> + or not. So we rely on another heuristic which is to check
> + the instruction at the return address and see if this is
> + a "unimp" instruction. If it is, then it is struct-return
> + function. */
>
> an "unimp" instruction.
> ^ ^
Really? I'm not a native English speaker, but I think "a unimp" is
correct. It's like "a university", isn't it?
Perhaps "the unimp instruction" would be better, though, since it's a
name of a specific instruction.