public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: rrh@cray.com
To: gcc-gnats@gcc.gnu.org
Subject: other/8113: gcc 3.* on sparc-sun-solaris2.8 incompatible with Rationale's purify
Date: Tue, 01 Oct 2002 15:16:00 -0000 [thread overview]
Message-ID: <20021001220901.27563.qmail@sources.redhat.com> (raw)
>Number: 8113
>Category: other
>Synopsis: gcc 3.* on sparc-sun-solaris2.8 incompatible with Rationale's purify
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Tue Oct 01 15:16:01 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator: rrh@cray.com
>Release: gcc 3.* sparc-sun-solaris2.8
>Organization:
>Environment:
>Description:
The executables produced for sparc-sun-solaris2.8 by g++ 3.0
g++ 3.1 and g++ 3.2 do not work with Rationale's latest
release of their purify product. Purify only works on releases
< g++ 3.0. As of this writing,
Rational is beta-testing purify support for g++ 3.0
and g++ 3.1,
but has no plans (yet) for supporting g++ 3.2.
Rationale has not been able to keep up with
the changes to the ABI and debug information.
That's too bad, since (leaving aside the issue of software
patents) purify is a pretty good tool for finding memory
problems.
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
next reply other threads:[~2002-10-01 22:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-01 15:16 rrh [this message]
2002-10-01 15:29 davem
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=20021001220901.27563.qmail@sources.redhat.com \
--to=rrh@cray.com \
--cc=gcc-gnats@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).