From: Yao Qi <qiyaoltc@gmail.com>
To: Pedro Alves <palves@redhat.com>
Cc: Philipp Rudo <prudo@linux.vnet.ibm.com>, gdb-patches@sourceware.org
Subject: Re: [RFC 4/7] Share code in initialize_tdesc_ functions
Date: Thu, 18 May 2017 11:21:00 -0000 [thread overview]
Message-ID: <867f1e8l75.fsf@gmail.com> (raw)
In-Reply-To: <148caa86-619a-9941-071b-7f38c817db33@redhat.com> (Pedro Alves's message of "Wed, 17 May 2017 16:43:20 +0100")
Pedro Alves <palves@redhat.com> writes:
Hi Philipp and Pedro,
Thanks for your comments.
>> This function is actually the part I like least of your implementation. Its
>> way to long and barely readable. The way I understand, it is needed to create
>> unique macro and function names. So why don't you simply use the filename of
>> the XML file where the feature is defined? It already is unique. Or use an
>> gdbarch hook so every architecture can decide for itself how to name them?
>
> Agreed. I was reading the patch and thinking how there must be a better
> way to handle this.
I dislike my implementation either. I thought about using xml feature
file name to distinguish features with the same name. However it
doesn't work because the file name is lost after processing xi:include.
GDB processes XML target descriptions in two steps,
1) process xi:include, copy feature xml files into a buffer,
2) parse the buffer with gdb-target.dtd then,
All tdesc_features are created in step 2, and GDB doesn't know what file
is this feature from. For example, there is an XML target description,
<target>
<xi:include href="32bit-core.xml"/>
</target>
after step 1, the buffer contains XML contents from 32bit-core.xml,
<target>
<feature name="org.gnu.gdb.i386.core">
...
</feature>
</target>
GDB starts parse it in buffer, but doesn't know where is this feature
from. I'll think about gdbarch hook you suggested.
--
Yao (齐尧)
prev parent reply other threads:[~2017-05-18 11:21 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-11 15:55 [RFC 0/7] Make GDB builtin target descriptions more flexible Yao Qi
2017-05-11 15:55 ` [RFC 3/7] Adjust the order of 32bit-linux.xml and 32bit-sse.xml in i386/i386-linux.xml Yao Qi
2017-05-11 15:55 ` [RFC 1/7] Move initialize_tdesc_mips* calls from mips-linux-nat.c to mips-linux-tdep.c Yao Qi
2017-05-11 15:55 ` [RFC 2/7] Add unit test to builtin tdesc generated by xml Yao Qi
2017-05-16 12:00 ` Philipp Rudo
2017-05-16 15:46 ` Yao Qi
2017-05-17 9:09 ` Philipp Rudo
2017-05-17 16:06 ` Pedro Alves
2017-05-30 8:00 ` Philipp Rudo
2017-06-01 17:53 ` Philipp Rudo
2017-05-17 15:41 ` Pedro Alves
2017-05-18 9:54 ` Yao Qi
2017-05-18 11:34 ` Pedro Alves
2017-05-19 15:47 ` Yao Qi
2017-05-22 8:51 ` Yao Qi
2017-05-11 15:55 ` [RFC 7/7] Remove builtin tdesc_i386_*_linux Yao Qi
2017-05-16 12:02 ` Philipp Rudo
2017-05-17 15:46 ` Pedro Alves
2017-05-11 15:55 ` [RFC 6/7] Lazily and dynamically create i386-linux target descriptions Yao Qi
2017-05-11 18:14 ` John Baldwin
2017-05-11 21:03 ` Yao Qi
2017-05-17 15:43 ` Pedro Alves
2017-05-18 15:12 ` Yao Qi
2017-05-19 10:15 ` Pedro Alves
2017-05-19 14:27 ` Yao Qi
2017-05-11 15:55 ` [RFC 5/7] Centralize i386 linux " Yao Qi
2017-05-11 16:06 ` [RFC 0/7] Make GDB builtin target descriptions more flexible Eli Zaretskii
2017-05-11 20:56 ` Yao Qi
2017-05-11 20:55 ` [RFC 4/7] Share code in initialize_tdesc_ functions Yao Qi
2017-05-16 12:02 ` Philipp Rudo
2017-05-17 15:43 ` Pedro Alves
2017-05-18 11:21 ` Yao Qi [this message]
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=867f1e8l75.fsf@gmail.com \
--to=qiyaoltc@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=prudo@linux.vnet.ibm.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).