aboutsummaryrefslogtreecommitdiff
path: root/lib/Driver/ToolChains.cpp
diff options
context:
space:
mode:
authorChandler Carruth <chandlerc@gmail.com>2011-10-04 09:58:21 +0000
committerChandler Carruth <chandlerc@gmail.com>2011-10-04 09:58:21 +0000
commitc916377785b917e369b8ec9e9af43a4bb6c4699c (patch)
tree4db803e31d09dd48f9c6bdf825924ca8acf3f4b0 /lib/Driver/ToolChains.cpp
parenta24b9802d3009c448387174f70bcd9ab44b8a7ea (diff)
Add a comment explaining that I have a better plan for implementing the
GCC installation search that requires fewer filesystem operations. Planning to implement that next as the current approcah while thorough (and so far looks correct) does a very unfortunate number of filesystem operations. I'm motivated to fix this in no small part because I would like to support a much larger space of triples and GCC versions, which would explode the current algorithm. git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@141073 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'lib/Driver/ToolChains.cpp')
-rw-r--r--lib/Driver/ToolChains.cpp2
1 files changed, 2 insertions, 0 deletions
diff --git a/lib/Driver/ToolChains.cpp b/lib/Driver/ToolChains.cpp
index dd84992a9c..b67f001e78 100644
--- a/lib/Driver/ToolChains.cpp
+++ b/lib/Driver/ToolChains.cpp
@@ -1605,6 +1605,8 @@ public:
// accuracy, and architecture specificity in that order. The inverted walk
// requires testing the filesystem more times than is ideal, but shouldn't
// matter in practice as this is once on startup.
+ // FIXME: Instead of this, we should walk from the root down through each
+ // layer, and if it is "better" than prior installations found, use it.
static const char* GccVersions[] = {
"4.6.1", "4.6.0", "4.6",
"4.5.3", "4.5.2", "4.5.1", "4.5",