This is the mail archive of the
mailing list for the GCC project.
Re: Question about macro _GLIBCXX_RES_LIMITS in libstdc++ testsuite
- From: Hans-Peter Nilsson <hp at bitrange dot com>
- To: "Bin.Cheng" <amker dot cheng at gmail dot com>
- Cc: "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>, libstdc++ at gcc dot gnu dot org
- Date: Sat, 16 May 2015 05:35:32 -0400 (EDT)
- Subject: Re: Question about macro _GLIBCXX_RES_LIMITS in libstdc++ testsuite
- Authentication-results: sourceware.org; auth=none
- References: <CAHFci2_nbpqa2_SkCgAKkWgKouudWz_avyvO6SrYo-sJV5kEOA at mail dot gmail dot com>
On Thu, 23 Apr 2015, Bin.Cheng wrote:
> In libstdc++ testsuite, I noticed that macro _GLIBCXX_RES_LIMITS is
> checked/set by GLIBCXX_CHECK_SETRLIMIT, which is further guarded by
> GLIBCXX_IS_NATIVE as below:
> AC_DEFUN([GLIBCXX_CONFIGURE_TESTSUITE], [
> if $GLIBCXX_IS_NATIVE ; then
> # Do checks for resource limit functions.
> # Look for setenv, so that extended locale tests can be performed.
> For cross toolchain like arm-linux, _GLIBCXX_RES_LIMITS isn't set. As
> a result, function __gnu_test::set_file_limit is actually nullified
> and causing case 27_io/fpos/14775.cc failed.
> My question is why we want to guard the check with GLIBCXX_IS_NATIVE?
> Could we check it directly, if it's not supported, it's going to fail
> and undef the macro anyway?
Good question. I'm CC:ing the libstdc++ list, maybe that'll
bring an answer before another 1.5 months.