Re: [RFA] convert blocks to dictionaries, phase 1, main part

[Andrew Cagney <ac131313@ges.redhat.com>]

>> Yep.  If you think accessor macro's are a good idea, try debugging /
>> using sim/common some time :-(

(I can say this cos I was part responsible for that code :-)

>> Then just mention those that do apply.
>> (I thought DanielJ indicated that you just doing an initial linear
>> implementation?)
> 
> 
> No, I'm doing initial implementations that are almost exactly the same
> as currently used in struct block, namely hashtable + linear.  (And
> the linear has an 'expandable' variant for use by jv-lang.c and
> mdebugread.c: this doesn't affect symbol searching, but it does affect
> how you are allowed to add symbols.)
> 
> I don't want to get rid of hashtables, certainly: that would slow
> things down enormously.

Ok.

>>>> - you'll want to start compiling all targets
> 
> 
>>> Sure.  How do I go about doing this?  I don't have access to a wide
>>> range of machines; are there machines at Red Hat that I can use?
> 
> 
>> target's not hosts :-) There is some sed in MAINTAINERS for
>> generating the target list.  Richard E, I believe, posted a script
>> for doing all the config's and builds.
> 
> 
> Oh, right.  Thanks, that script looks useful.
> 
> I'm curious exactly how long it will take my machine to do all those
> builds - it's a 4-year-old 333 MHz PII, and I don't think it would be
> proper for me to ask the math department to buy a new machine just for
> working on GDB - but they might all finish overnight.  If not, they'll
> certainly finish over the weekend.

There are now only 16(?) targets.  I was originally building 50 targets 
(gdb not gdb+dejagnu -- dejagnu is what takes the time) using a P200 and 
it took ~8 hours.

Andrew