This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [PATCH 15/25] [RFC] GDBserver unit test to i386_tdesc

From: Yao Qi <qiyaoltc at gmail dot com>
To: Pedro Alves <palves at redhat dot com>
Cc: gdb-patches at sourceware dot org
Date: Thu, 29 Jun 2017 10:27:44 +0100
Subject: Re: [PATCH 15/25] [RFC] GDBserver unit test to i386_tdesc
Authentication-results: sourceware.org; auth=none
References: <1497256916-4958-1-git-send-email-yao.qi@linaro.org> <1497256916-4958-16-git-send-email-yao.qi@linaro.org> <77cae620-c97f-1baa-a5bf-bf320cb93213@redhat.com>

Pedro Alves <palves@redhat.com> writes:

> On 06/12/2017 09:41 AM, Yao Qi wrote:
>> This patch adds a unit test in GDBserver to test dynamically created
>> target descriptions equal to these pre-generated ones.
>> 
>> gdb/gdbserver:
>
> Are these temporary tests?  What's the plan for the pre-generated ones?

They are not temporary tests, we'll keep the tests, but they won't
change.  We also keep these pre-generated target descriptions, as legacy
target descriptions, for the tests.  Once we finish the target
description transition, we can move these pre-generated target
descriptions into testsuite/ directory.

Note that, after we finish the change for a given architecture, all
target descriptions are dynamically generated, so there is no new
pre-generated target description, and we don't update the tests.

-- 
Yao (齐尧)

References:
- [PATCH 00/25 V2] Make GDB builtin target descriptions more flexible
  - From: Yao Qi
- [PATCH 15/25] [RFC] GDBserver unit test to i386_tdesc
  - From: Yao Qi
- Re: [PATCH 15/25] [RFC] GDBserver unit test to i386_tdesc
  - From: Pedro Alves

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]