From: Pedro Alves <palves@redhat.com>
To: Thomas Preudhomme <thomas.preudhomme@foss.arm.com>,
GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH, gdb/testsuite] Fix wrong return type in tests
Date: Wed, 29 Nov 2017 11:04:00 -0000 [thread overview]
Message-ID: <964a7f20-21f0-3e7f-a46a-6ef34cef046c@redhat.com> (raw)
In-Reply-To: <e998867a-08b5-cbf2-004b-b9ce3d73c588@foss.arm.com>
On 11/29/2017 10:48 AM, Thomas Preudhomme wrote:
> index 0990430c128413ecc21bcf65ebf58a1899f535fa..9f63fefcaeb800f7444fe74225514d3330036e5b 100644
> --- a/gdb/testsuite/gdb.cp/psymtab-parameter.cc
> +++ b/gdb/testsuite/gdb.cp/psymtab-parameter.cc
> @@ -16,7 +16,7 @@
> along with this program. If not, see <http://www.gnu.org/licenses/>. */
>
> template <typename T>
> -long
> +void
> func ()
> {
> }
> diff --git a/gdb/testsuite/gdb.cp/psymtab-parameter.exp b/gdb/testsuite/gdb.cp/psymtab-parameter.exp
> index 3d78de91f4b3752d754bd776ae3532700a308a40..5c4b6ac71927fe9030bd9ce66111761425ab433b 100644
> --- a/gdb/testsuite/gdb.cp/psymtab-parameter.exp
> +++ b/gdb/testsuite/gdb.cp/psymtab-parameter.exp
> @@ -31,6 +31,6 @@ gdb_test_no_output "set language c++"
> # XFAIL than FAIL here. For example -readnow breaks it.
> gdb_test_no_output "maintenance info symtabs"
>
> -# GDB has shown only the `long func<short>()' ELF symbol before, not the DWARF
> +# GDB has shown only the `void func<short>()' ELF symbol before, not the DWARF
> # symbol
> gdb_test "complete p 'func<short>(" "p 'func<short>\\(\\)"
I think the return type may have been significant for this test.
See comments around DMGL_RET_DROP in commit 900e11f9ec1e.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2017-11-29 11:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-29 10:48 Thomas Preudhomme
2017-11-29 11:04 ` Pedro Alves [this message]
2017-11-29 11:59 ` Thomas Preudhomme
2017-11-29 12:06 ` Pedro Alves
2017-11-29 13:43 ` Thomas Preudhomme
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=964a7f20-21f0-3e7f-a46a-6ef34cef046c@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=thomas.preudhomme@foss.arm.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