From: Michael Elizabeth Chastain <mec@shout.net>
To: geoffk@apple.com
Cc: drow@mvista.com, gcc-patches@gcc.gnu.org, gdb@sources.redhat.com
Subject: Re: Two possible function stabs patches
Date: Wed, 30 Jul 2003 22:29:00 -0000 [thread overview]
Message-ID: <200307302229.h6UMTiw1005391@duracef.shout.net> (raw)
Geoff K suggests:
int main(void)
{
static int foo(void) { return 1; }
return foo() == 1 ? 0 : 1;
}
break foo
Hmmmm. I'll bet that this would be the first code in the test
suite with nested functions. It is a supported gcc feature,
so that would be good to test. We'll probably generate a bunch
of new KFAILs with this.
I'll put this on my TODO list, but I have to postpone this until
after the gdb 6.0 release. It's a question of tuits.
Michael C
next reply other threads:[~2003-07-30 22:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-30 22:29 Michael Elizabeth Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-07-30 14:18 Fwd: " Andrew Cagney
2003-08-01 22:36 ` Geoffrey Keating
2003-07-30 5:47 Fwd: " Michael Elizabeth Chastain
2003-07-30 21:43 ` Geoffrey Keating
2003-07-30 1:05 Geoffrey Keating
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=200307302229.h6UMTiw1005391@duracef.shout.net \
--to=mec@shout.net \
--cc=drow@mvista.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb@sources.redhat.com \
--cc=geoffk@apple.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