From: Randolph Chung <tausq@debian.org>
To: Matthias Klose <doko@cs.tu-berlin.de>
Cc: parisc-linux@lists.parisc-linux.org, debian-hppa@lists.debian.org
Subject: Re: [parisc-linux] running gcc testsuite triggers ongoing page faults
Date: Sun, 11 Jan 2004 06:25:54 -0800 [thread overview]
Message-ID: <20040111142547.GG533@tausq.org> (raw)
In-Reply-To: <16385.13815.94626.165424@gargle.gargle.HOWL>
> well, the last testcase logged in build/gcc/testsuite/gcc.log is
>
> gcc.c-torture/execute/931004-12.c compilation, -O1
>
> the next one would be
>
> gcc.c-torture/execute/931004-12.c compilation, -O2
does it always die at the same test case?
randolph
next prev parent reply other threads:[~2004-01-11 13:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-11 9:16 [parisc-linux] running gcc testsuite triggers ongoing page faults Matthias Klose
2004-01-11 10:08 ` Randolph Chung
2004-01-11 10:08 ` Randolph Chung
2004-01-11 11:39 ` Matthias Klose
2004-01-11 11:39 ` Matthias Klose
2004-01-11 14:25 ` Randolph Chung
2004-01-11 14:25 ` Randolph Chung [this message]
2004-01-11 20:49 ` John David Anglin
2004-01-11 20:49 ` John David Anglin
-- strict thread matches above, loose matches on Subject: below --
2004-01-11 9:16 Matthias Klose
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=20040111142547.GG533@tausq.org \
--to=tausq@debian.org \
--cc=debian-hppa@lists.debian.org \
--cc=doko@cs.tu-berlin.de \
--cc=parisc-linux@lists.parisc-linux.org \
/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