From: Yao Qi <qiyaoltc@gmail.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [testsuite patch] Fix testsuite regression by: Do not skip prologue for asm (.S) files
Date: Fri, 10 Jul 2015 08:43:00 -0000 [thread overview]
Message-ID: <86lheol7wz.fsf@gmail.com> (raw)
In-Reply-To: <20150629163708.GA28795@host1.jankratochvil.net> (Jan Kratochvil's message of "Mon, 29 Jun 2015 18:37:08 +0200")
Jan Kratochvil <jan.kratochvil@redhat.com> writes:
> OK for check-in?
>
Yes, it is OK.
>
> Jan
> gdb/testsuite/
> 2015-06-29 Jan Kratochvil <jan.kratochvil@redhat.com>
>
> * gdb.asm/asm-source.exp (f at main): Stop at gdbasm_enter.
> (n at main): New.
> * gdb.asm/asmsrc1.s: Add comment "mark: main enter".
What does "f at main" and "n at main" in parenthesises mean here?
--
Yao (齐尧)
next prev parent reply other threads:[~2015-07-10 8:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-29 16:37 Jan Kratochvil
2015-07-10 8:43 ` Yao Qi [this message]
2015-07-10 11:47 ` Jan Kratochvil
2015-07-10 14:32 ` Yao Qi
2015-07-10 14:49 ` Jan Kratochvil
2015-07-10 13:07 ` [testsuite commit] " 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=86lheol7wz.fsf@gmail.com \
--to=qiyaoltc@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).