public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeffrey A Law <law@cygnus.com>
To: Geoff Keating <geoffk@cygnus.com>
Cc: aoliva@cygnus.com, gcc@gcc.gnu.org
Subject: Re: new automated testing facility now operational
Date: Fri, 31 Mar 2000 09:33:00 -0000	[thread overview]
Message-ID: <13175.954524031@upchuck> (raw)
In-Reply-To: <200003310129.RAA09770@localhost.cygnus.com>

  In message < 200003310129.RAA09770@localhost.cygnus.com >you write:
  > > OTOH, it is one for which the build takes significantly longer than
  > > for any other target I've ever built, because of the huge number of
  > > multilibs.  Which means it runs tests less often.
  > 
  > There are only 10 multilibs, and it spends most of its time actually
  > running the testsuite.  It would be more scary if I had it running
  > tests on the multilibs.
  > 
  > I think the other targets I suggested have a similar number of
  > multilibs, except for i960, and ARM (which have many fewer and many
  > more, respectively).
The mn103 only has 2 multilibs (mn103 & am33).  It's not a particularly
interesting target other than it works, has few multilibs and a simulator.

jeff

  reply	other threads:[~2000-03-31  9:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-30 15:01 Geoff Keating
2000-03-30 15:57 ` Alexandre Oliva
2000-03-30 16:30   ` Geoff Keating
2000-03-30 16:59     ` Alexandre Oliva
2000-03-30 17:29       ` Geoff Keating
2000-03-31  9:33         ` Jeffrey A Law [this message]
2000-03-30 17:01     ` Michael Meissner
2000-04-02 15:59 ` Gerald Pfeifer
2000-04-02 16:17   ` Geoff Keating
2000-03-30 15:57 Mike Stump

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=13175.954524031@upchuck \
    --to=law@cygnus.com \
    --cc=aoliva@cygnus.com \
    --cc=gcc@gcc.gnu.org \
    --cc=geoffk@cygnus.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).