From: Robert Lipe <robertl@dgii.com>
To: law@cygnus.com
Cc: egcs@cygnus.com
Subject: Re: loop-2{f,g} failures
Date: Wed, 26 Aug 1998 20:55:00 -0000 [thread overview]
Message-ID: <19980826225631.A3677@dgii.com> (raw)
In-Reply-To: <5657.904186428@hurl.cygnus.com>
> > I have been adding another x86 target (essentially a SVR5-based target)
> > and trying to analyze two new failures that I haven't been seeing on
> > other similar x86 targets. Linux doesn't fail. OpenServer doesn't fail.
> > Unixware 2 doesn't fail.
> >
> > The tests in question were loop-2f and loop-2g. Now I see these exact
>
> They're designed to tickle very obscure bugs in the loop optimizer.
> It's unlikely they're bugs in your backend.
They must be really bizarre if they show up on Sparc/Solaris and UDK
targets on OpenServer but not any of the other x86 targets, including
OpenServer native.
I'll move my focus back to someplace where I can make a productive
contribution.
Thanx for the info.
RJL
next prev parent reply other threads:[~1998-08-26 20:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-08-25 23:05 Results for egcs-2.91.55 19980824 (gcc2 ss-980609 experimental) testsuite on sparc-sun-solaris2.5.1 Matthias Mueller
1998-08-26 11:57 ` loop-2{f,g} failures Robert Lipe
1998-08-26 20:55 ` Jeffrey A Law
1998-08-26 20:55 ` Robert Lipe [this message]
1998-08-27 12:32 ` David S. Miller
1998-08-27 0:40 ` Mark Mitchell
1998-08-27 7:40 ` David S. Miller
1998-08-27 8:22 ` Joern Rennecke
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=19980826225631.A3677@dgii.com \
--to=robertl@dgii.com \
--cc=egcs@cygnus.com \
--cc=law@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).