This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [PATCH, testsuite] Fix PASS->UNSUPPORTED on g++.dg/tls/static-1.C

From: Adam Nemet <anemet at caviumnetworks dot com>
To: "H. J. Lu" <hjl at lucon dot org>
Cc: gcc-patches at gcc dot gnu dot org
Date: Thu, 24 May 2007 12:46:54 -0700
Subject: Re: [PATCH, testsuite] Fix PASS->UNSUPPORTED on g++.dg/tls/static-1.C
References: <18005.55961.997691.174870@localhost.localdomain> <20070524184006.GA16803@lucon.org> <18005.58019.27847.871878@localhost.localdomain> <20070524192540.GA16992@lucon.org>

H. J. Lu writes:
> They are 2 different kinds of tests. Tests in libssp make sure that
> libssp itself is OK. The ssp tests in gcc/testsuites make sure that
> compiler handles ssp properly. That is similar to C++ tests in
> gcc/testsuites and tests in libstdc++.

I don't think libstdc++ is a good example.  Look at gcc.dg/gomp.  The
tests there are all dg-do compile.  I think the distinction is that
you can only have compilation tests under gcc.  Run and link tests
should go under the library that the feature depends on.

Adam

References:
- [PATCH, testsuite] Fix PASS->UNSUPPORTED on g++.dg/tls/static-1.C
  - From: Adam Nemet
- Re: [PATCH, testsuite] Fix PASS->UNSUPPORTED on g++.dg/tls/static-1.C
  - From: H. J. Lu
- Re: [PATCH, testsuite] Fix PASS->UNSUPPORTED on g++.dg/tls/static-1.C
  - From: Adam Nemet
- Re: [PATCH, testsuite] Fix PASS->UNSUPPORTED on g++.dg/tls/static-1.C
  - From: H. J. Lu

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]