public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jsm28 at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/23867] New: libstdc++ ABI testsuite should work for installed compiler testing
Date: Tue, 13 Sep 2005 19:22:00 -0000	[thread overview]
Message-ID: <20050913192216.23867.jsm28@gcc.gnu.org> (raw)

The libstdc++ ABI testsuite does not work when testing an installed compiler
because:

* abi.exp checks for "../src/.libs/libstdc++.so", which of course is not
available with an installed compiler.

* abi.exp requires baseline_file to be set in site.exp; with installed compiler
testing, site.exp is generally created to set generic variables such as CC and
CXX being the compilers to test, but not libstdc++-specific ones such as
baseline_file.

The testsuite should be arranged so that it can find the libstdc++ being used by
an installed toolchain, and the logic to find the baseline file should be
implemented within the testsuite.  It would probably then no longer be necessary
to restrict the ABI testing to native compilers only.

Mark has asked for this PR to be assigned to him.

-- 
           Summary: libstdc++ ABI testsuite should work for installed
                    compiler testing
           Product: gcc
           Version: 4.1.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: testsuite
        AssignedTo: mark at codesourcery dot com
        ReportedBy: jsm28 at gcc dot gnu dot org
                CC: gcc-bugs at gcc dot gnu dot org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23867


             reply	other threads:[~2005-09-13 19:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-13 19:22 jsm28 at gcc dot gnu dot org [this message]
2005-09-13 19:59 ` [Bug testsuite/23867] " pinskia at gcc dot gnu dot org

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=20050913192216.23867.jsm28@gcc.gnu.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).