From: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>
To: ehrhardt@mathematik.uni-ulm.de
Cc: dank@kegel.com, ebotcazou@libertysurf.fr, gcc@gcc.gnu.org
Subject: Re: Spurious testsuite failures on multi-cpu sparc-solaris2.9
Date: Sun, 19 Sep 2004 00:39:00 -0000 [thread overview]
Message-ID: <200409182319.i8INJ9ck007034@caip.rutgers.edu> (raw)
In-Reply-To: <20040908081204.10193.qmail@thales.mathematik.uni-ulm.de>
> On Tue, Sep 07, 2004 at 09:28:00PM -0400, Kaveh R. Ghazi wrote:
> > I'm trying to test GCC on a 4 cpu sparc-sun-solaris2.9 box using
> > expect-5.42.1, tcl8.4.7 and dejagnu-1.4.4. I'm getting lots of
> > spurious testsuite failures probably related to the solaris
> > kernel bug mentioned here:
> > http://gcc.gnu.org/ml/gcc/2004-04/msg01480.html
> >
> > Does any one know if bug 4927647 is addressed in any patch from Sun
> > yet?
>
> According to SUN a fix has been integrated into Sol10 and a patch for
> Sol9 will be release RSN. We were provided with a T-patch (raw
> binaries not an officially released patch) in response to my bug
> report.
I'm curious about whether this patch will be part of the "recommended"
bundle, and thus available to those without a sunsolve account. It'll
likely be part of the "recommended" set if the fix is located in files
already in that bundle. Are you able to figure that out? (Or simply
list the files and I'll try and determine it.)
At one point I worked for a company who received a "T" patch and I was
able to coax sun into releasing an official patch sooner. I did this
at the time because I felt that the more people using the code (more
than just me!), the more likely it didn't have some other horrible
problem. :-)
Do you think you could prod sun into releasing this officially more
quickly? I know that I personally would be able to be more productive
if I could run the testsuite in parallel and post results more
quickly.
> > Is the expect patch mentioned here helpful at all?
> > http://kegel.com/crosstool/current/patches/expect-5.39/pr12096.patch
>
> It didn't fix things for me, but it doesn't hurt either.
> regards Christian
That patch didn't fix the problem for me either.
Thanks,
--Kaveh
--
Kaveh R. Ghazi ghazi@caip.rutgers.edu
next prev parent reply other threads:[~2004-09-18 23:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-08 1:28 Kaveh R. Ghazi
2004-09-08 4:08 ` Dan Kegel
2004-09-08 8:12 ` Christian Ehrhardt
2004-09-19 0:39 ` Kaveh R. Ghazi [this message]
2004-10-04 13:29 ` Christian Ehrhardt
2004-10-04 14:24 ` Kaveh R. Ghazi
2004-10-04 21:57 ` Christian Ehrhardt
2004-10-05 15:10 ` Kaveh R. Ghazi
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=200409182319.i8INJ9ck007034@caip.rutgers.edu \
--to=ghazi@caip.rutgers.edu \
--cc=dank@kegel.com \
--cc=ebotcazou@libertysurf.fr \
--cc=ehrhardt@mathematik.uni-ulm.de \
--cc=gcc@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).