Home | History | Annotate | Download | only in Driver

Lines Matching refs:gcc

702     // it was previously found in the gcc lib dir. However, for all the Darwin
740 // instead of the gcc-provided one (which is also incidentally
741 // only present in the gcc lib dir, which makes it hard to find).
770 // more opaque. For now, we follow gcc closely solely for the
828 // Sob. These is strictly gcc compatible for the time being. Apple
829 // gcc translates options twice, which means that self-expanding
1227 /// Generic_GCC - A tool chain using the 'gcc' command to perform
1228 /// all subcommands; this relies on gcc translating the majority of
1327 // The library directories which may contain GCC installations.
1329 // The compatible GCC triples for this particular architecture.
1353 // Then look for gcc installed alongside clang.
1361 // Loop over the various components which exist and select the best GCC
1362 // installation available. GCC installs are ranked by version number.
1389 OS << "Found candidate GCC installation: " << InstallPath << "\n";
1392 OS << "Selected GCC installation: " << GCCInstallPath << "\n";
1497 static const char *const SolarisSPARCLibDirs[] = {"/gcc"};
2185 // Solaris is a special case. The GCC installation is under
2186 // /usr/gcc/<major>.<minor>/lib/gcc/<triple>/<major>.<minor>.<patch>/, so we
2203 LibDir + "/" + VersionText.str() + "/lib/gcc/" + CandidateTriple.str();
2207 // If we make it here there has to be at least one GCC version, let's just
2242 {"/gcc/" + CandidateTriple.str(), "/../../.."},
2244 // Debian puts cross-compilers in gcc-cross
2245 {"/gcc-cross/" + CandidateTriple.str(), "/../../.."},
2247 {"/" + CandidateTriple.str() + "/gcc/" + CandidateTriple.str(),
2250 // The Freescale PPC SDK has the gcc libraries in
2258 {"/i386-linux-gnu/gcc/" + CandidateTriple.str(), "/../../../.."}};
2328 Preprocess.reset(new tools::gcc::Preprocessor(*this));
2332 Compile.reset(new tools::gcc::Compiler(*this));
2343 Tool *Generic_GCC::buildLinker() const { return new tools::gcc::Linker(*this); }
2346 // Print the information about how we detected the GCC installation.
2397 // The vanilla GCC layout of libstdc++ headers uses a triple subdirectory. If
2398 // that path exists or we have neither a GCC nor target multiarch triple, use
2408 // GCC surprisingly uses *both* the GCC triple with a multilib suffix and
3345 getDriver().SysRoot + "/usr/gcc/" +
3350 getDriver().SysRoot + "/usr/gcc/" + Version.MajorStr +
3637 // Cross-compiling binutils and GCC installations (vanilla and openSUSE at
3639 // of the GCC installation. We use the GCC triple here to ensure that we end
3641 // detected GCC installation. For example, if we find a GCC installation
3642 // targeting x86_64, but it is a bi-arch GCC installation, it can also be
3693 // the GCC driver itself uses, as this is part of the GCC-compatible driver.
3694 // This was determined by running GCC in a fake filesystem, creating all
3709 // a biarch-like suffix of the GCC installation.
3713 // GCC cross compiling toolchains will install target libraries which ship
3715 // any part of the GCC installation in
3716 // <prefix>/<libdir>/gcc/<triple>/<version>. This decision is somewhat
3719 // whomever is doing the cross build targeting a sysroot using a GCC
3729 // Note that this matches the GCC behavior. See the below comment for where
3730 // Clang diverges from GCC's behavior.
3735 // If the GCC installation we found is inside of the sysroot, we want to
3736 // prefer libraries installed in the parent prefix of the GCC installation.
3737 // It is important to *not* use these paths when the GCC installation is
3741 // the cross. Note that GCC does include some of these directories in some
3750 // Similar to the logic for GCC above, if we currently running Clang inside
3765 // Try walking via the GCC triple path in case of biarch or multiarch GCC
3796 // Similar to the logic for GCC above, if we are currently running Clang
4062 // We need a detected GCC installation on Linux to provide libstdc++'s
4068 // the lib directory of the GCC installation. Note that this is expect to be
4090 // Gentoo is weird and places its headers inside the GCC install,
4098 // without a subdirectory corresponding to the gcc version.
4336 // This won't work to find gcc. Instead we give the installation detector an
4351 // The contents of LibDir are independent of the version of gcc.
4361 // These files are tied to a particular version of gcc.