From: Yao Qi <qiyaoltc@gmail.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Yao Qi <qiyaoltc@gmail.com>,
Andreas Schwab <schwab@linux-m68k.org>,
gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix wrong assertions
Date: Mon, 01 Jun 2015 11:35:00 -0000 [thread overview]
Message-ID: <86twuroe55.fsf@gmail.com> (raw)
In-Reply-To: <20150529141027.GA8159@host1.jankratochvil.net> (Jan Kratochvil's message of "Fri, 29 May 2015 16:10:27 +0200")
Jan Kratochvil <jan.kratochvil@redhat.com> writes:
> diff --git a/gdb/dwarf2loc.c b/gdb/dwarf2loc.c
> index 3aa8ddd..68d6cb4 100644
> --- a/gdb/dwarf2loc.c
> +++ b/gdb/dwarf2loc.c
> @@ -825,9 +825,9 @@ chain_candidate (struct gdbarch *gdbarch, struct call_site_chain **resultp,
>
> /* See call_site_find_chain_1 why there is no way to reach the bottom callee
> PC again. In such case there must be two different code paths to reach
> - it, therefore some of the former determined intermediate PCs must differ
> - and the unambiguous chain gets shortened. */
> - gdb_assert (result->callers + result->callees < result->length);
> + it. Still it may CALLERS+CALLEES==LENGTH in the case of optional
> + tail-call calling itself. */
> + gdb_assert (result->callers + result->callees <= result->length);
I am not a native English speaker, but I can't parse the comment. How
about "CALLERS + CALLEES equal to LENGTH in the case of self tail-call"?
Otherwise, the patch is OK to me.
--
Yao (齐尧)
next prev parent reply other threads:[~2015-06-01 11:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-09 18:57 Andreas Schwab
2015-05-13 14:01 ` Jan Kratochvil
2015-05-13 14:35 ` Andreas Schwab
2015-05-29 9:31 ` Yao Qi
2015-05-29 11:31 ` Jan Kratochvil
2015-05-29 13:43 ` Yao Qi
2015-05-29 14:10 ` Jan Kratochvil
2015-05-29 16:33 ` Yao Qi
2015-05-30 7:44 ` Jan Kratochvil
2015-06-01 11:35 ` Yao Qi [this message]
2015-06-01 12:05 ` [commit] " Jan Kratochvil
2015-05-19 20:47 ` [patch] testcase: tailcall assertion [Re: [PATCH] Fix wrong assertions] Jan Kratochvil
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=86twuroe55.fsf@gmail.com \
--to=qiyaoltc@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=schwab@linux-m68k.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