Roland McGrath wrote:
In the meantime, I think the new thing for you to work on this week
is the
"smart reader" hooks (now DwarfTasks 4.2). That does not have other
prerequisites from me holding it up. It should naturally mix in well with
the tail end of the dwarflint reloc work, as that is used in its testing plan.
Do the new libdw C hooks on a separate branch for now. (It would be nice
to make it a fork from master, but if it's easier to hack on it using a
fork from dwarf, that is fine too.) We'll review those hook details
carefully before merging C changes. When they are in shape, my plan is to
merge into master the use of the hooks in the libdw C code, with just stub
definitions of the hooks. That will keep it easy to maintain use of the
hooks in the C code on master and e.g. be sure to use them if we merge the
CFI support to master, though they will be inline stubs that compile away.
The real definitions of the hooks will come later on the dwarf branch only.
I'm on it. Will commit something later today, so that you can comment
on if you want.
But browsing through the source I realized another thing: block forms
can contain relocatable data. What with these? Shall libdw handle them
too? I suspect it has to, client doesn't know about reloc hooks...
PM