This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH 06/25] Generate c for feature instead of tdesc
Eli Zaretskii <eliz@gnu.org> writes:
>> The created
>> +source file can be used in @value{GDBN} when an XML parser is not
>> +available to parse the description.
>
> I also have some clarification requests (and I do realize that the
> original text had the same issues):
>
> . I think we should say a few words regarding the argument FILE: I
> don't believe _any_ file will do in this role, so we should tell
> what kind of files are expected here.
It is an XML target description.
> . "The created source file can be used in GDB ..." -- used how? I'd
> prefer that we said a sentence or tow about that as well, or had a
> cross-reference to where that is described.
The created source file is built into GDB. How is the doc and NEWS
entry below? Note that I removed the last sentence "... when an XML
parser is not available to parse the description", because these created
c files are builtin target descriptions which are used too when an XML
parser is available.
@kindex maint print c-tdesc @r{[}@var{file}@r{]}
@item maint print c-tdesc
Print the target description (@pxref{Target Descriptions}) as
a C source file. By default, the target description is for the current
target, but if the optional argument @var{file} is provided, that file
is used to produce the description. The @var{file} is an XML document,
of the form described in @ref{Target Description Format}. The created
source file is built in @value{GDBN}.
>
> Also, what about a NEWS entry?
* The "maintenance print c-tdesc" command now takes an optional
argument which is the file name of XML target description.
--
Yao (齐尧)