From: "Eli Zaretskii" <eliz@gnu.org>
To: Mark Kettenis <kettenis@gnu.org>
Cc: brobecker@adacore.com, gdb-patches@sources.redhat.com
Subject: Re: [RFA/sparc] pb doing next over struct-return function
Date: Tue, 23 Nov 2004 11:33:00 -0000 [thread overview]
Message-ID: <01c4d14f$Blat.v2.2.2$de142420@zahav.net.il> (raw)
In-Reply-To: <200411230833.iAN8X6Ru027549@juw15.nfra.nl> (message from Mark Kettenis on Tue, 23 Nov 2004 09:33:06 +0100 (CET))
> 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.
next prev parent reply other threads:[~2004-11-23 11:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-23 5:35 Joel Brobecker
2004-11-23 8:33 ` Mark Kettenis
2004-11-23 11:33 ` Eli Zaretskii [this message]
2004-11-23 12:06 ` Richard Earnshaw
2004-11-23 19:57 ` Paul Hilfinger
2004-11-23 19:29 ` Joel Brobecker
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='01c4d14f$Blat.v2.2.2$de142420@zahav.net.il' \
--to=eliz@gnu.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sources.redhat.com \
--cc=kettenis@gnu.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