From ac793822cd27554c6409b5c380555f94be48b431 Mon Sep 17 00:00:00 2001 From: Dan Gohman Date: Tue, 2 Nov 2010 23:19:55 +0000 Subject: Don't try to enforce MAXPATHLEN in sys::Path for Unix. OS's can check limits on their own. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@118113 91177308-0d34-0410-b5e6-96231b3b80d8 --- lib/System/Unix/Path.inc | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) (limited to 'lib/System') diff --git a/lib/System/Unix/Path.inc b/lib/System/Unix/Path.inc index b7afb8536d..c90092001e 100644 --- a/lib/System/Unix/Path.inc +++ b/lib/System/Unix/Path.inc @@ -96,10 +96,12 @@ Path::operator=(StringRef that) { bool Path::isValid() const { - // Check some obvious things - if (path.empty()) - return false; - return path.length() < MAXPATHLEN; + // Empty paths are considered invalid here. + // This code doesn't check MAXPATHLEN because there's no need. Nothing in + // LLVM manipulates Paths with fixed-sizes arrays, and if the OS can't + // handle names longer than some limit, it'll report this on demand using + // ENAMETOLONG. + return !path.empty(); } bool -- cgit v1.2.3