From: Jim Blandy <jimb@redhat.com>
To: Andrew Cagney <ac131313@ges.redhat.com>
Cc: David Carlton <carlton@math.stanford.edu>,
gdb-patches@sources.redhat.com
Subject: Re: [RFA] convert blocks to dictionaries, phase 1, main part
Date: Sun, 22 Sep 2002 14:51:00 -0000 [thread overview]
Message-ID: <vt2r8flogh4.fsf@zenia.red-bean.com> (raw)
In-Reply-To: <3D87893F.4090203@ges.redhat.com>
Andrew Cagney <ac131313@ges.redhat.com> writes:
> >>>> - 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.
What's the value of building across all target architectures? It's
not clear to me that different targets will exercise different parts
of the symtab code; making sure all the debug formats are covered
should be sufficient.
It seems to me that architecture-specific issues in the symtab code
will be pretty rare, and easily picked off as they are noticed. It's
very hard for me to imagine broad target coverage revealing problems
in the design. For regcache work, sure --- but for the symtab, I
don't see it.
next prev parent reply other threads:[~2002-09-22 21:51 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-16 15:26 David Carlton
2002-09-16 15:30 ` David Carlton
2002-09-17 7:35 ` Daniel Jacobowitz
2002-09-17 9:03 ` Andrew Cagney
2002-09-17 10:43 ` David Carlton
2002-09-17 10:49 ` Daniel Jacobowitz
2002-09-17 11:34 ` David Carlton
2002-09-17 12:24 ` Andrew Cagney
2002-09-17 11:44 ` Andrew Cagney
2002-09-17 12:30 ` Daniel Jacobowitz
2002-09-17 12:49 ` Andrew Cagney
2002-09-17 13:32 ` Daniel Jacobowitz
2002-09-17 21:48 ` Daniel Berlin
2002-09-18 7:26 ` Andrew Cagney
2002-09-20 9:13 ` Jim Blandy
2002-09-17 12:59 ` Daniel Berlin
2002-09-17 13:13 ` Andrew Cagney
2002-09-17 9:29 ` Andrew Cagney
2002-09-17 11:04 ` David Carlton
2002-09-17 12:16 ` Andrew Cagney
2002-09-17 12:35 ` Daniel Jacobowitz
2002-09-17 12:46 ` David Carlton
2002-09-17 12:57 ` Andrew Cagney
2002-09-22 14:51 ` Jim Blandy [this message]
2002-09-17 12:54 ` Michael Snyder
2002-09-17 12:59 ` Daniel Berlin
2002-09-18 2:56 ` Richard Earnshaw
2002-09-18 14:07 ` Andrew Cagney
2002-09-19 3:14 ` Richard Earnshaw
2002-09-19 6:18 ` Elena Zannoni
2002-09-19 7:52 ` Richard Earnshaw
2002-09-19 7:51 ` Andrew Cagney
2002-09-22 14:41 ` Jim Blandy
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=vt2r8flogh4.fsf@zenia.red-bean.com \
--to=jimb@redhat.com \
--cc=ac131313@ges.redhat.com \
--cc=carlton@math.stanford.edu \
--cc=gdb-patches@sources.redhat.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