This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/14775] LFS tests missing
- From: "bkoz at redhat dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 29 Mar 2004 19:51:00 -0000
- Subject: [Bug libstdc++/14775] LFS tests missing
- References: <20040329191046.14775.bkoz@gcc.gnu.org>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From bkoz at redhat dot com 2004-03-29 19:50 -------
Subject: Re: LFS tests missing
>Hi. This is definitely in my TODO list. I already have the skeleton of a test,
>adapted from glibc. And, the nice thing is that most modern filesystems support
>sparse files, this means a 4G+eps file is never *actually* written! Good.
I figured you were on this: I just wanted to make sure it doesn't get lost.
>1- When and where running the test? Shall we run it everywhere, XFAILed? Or only
>on LFS-enabled machines, possibly just wrapping the test in _GLIBCXX_USE_LFS??
>Note that 64bit machines may actually be able to access > 4G files even if USE_LFS
>is not defined!
I think we should only run this test if _GLIBCXX_USE_LFS, regardless of
the underlying characteristics of the host os.
Probably something like the __enc_filebuf tests.
>2- The shell issue! We must make sure the ulimit are Ok when the test is run. This
>is not the case by default on bash and tcsh.
Yeah, I don't know what to do with this bit. Can't you just use something like
__gnu_test::set_memory_limits
?
-benjamin
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14775