search for: generic_gcc

...9 Jul 2013, at 02:14, Eli Friedman <eli.friedman at gmail.com> wrote: > It's straightforward: you just need to make toolchains::FreeBSD > inherit directly from ToolChain and implement all the methods it would > otherwise inherit from Generic_ELF (which in turn inherits from > Generic_GCC). Wouldn't it make more sense to move the Linux-specific code out of Generic_GCC and into the Linux toolchain, rather than making all of the other subclasses of Generic_GCC reimplement the common code? David

...it > call stat() a little over two hundred times, each time > the compiler is started up. It's straightforward: you just need to make toolchains::FreeBSD inherit directly from ToolChain and implement all the methods it would otherwise inherit from Generic_ELF (which in turn inherits from Generic_GCC). -Eli

Greetings - I'm a user of clang (3.3), as it is the system compiler for my installation of FreeBSD. (In FreeBSD 10, it will be the default compiler, but that's not my point.) My system identifies itself as: FreeBSD 9.2-PRERELEASE #0: Tue Jul 16 13:00:08 EDT 2013 lidl at nine0:/usr/obj/usr/src/sys/GENERIC Recently, in preparation for the upcoming 9.2 release, they imported the llvm

...respective operating system kernels in the very few places where it is needed, such as which standard preprocessor defines there are ([clang]/lib/Basic/Targets.cpp:LinuxTargetInfo::getOSDefines), or how the target specifier maps to include and library directories ([clang]/lib/Driver/ToolChains.cpp:Generic_GCC::GCCInstallationDetector::CollectLibDirsAndTriples, for example). The question is what LinuxDistrib, LinuxTargetInfo, and a few others should be renamed to; we need new names to mean something like "not depending on the Linux kernel but still glibc". In GCC we use files such as gnu-user...

...8 @@ TargetArch == llvm::Triple::ppc64 || TargetArch == llvm::Triple::systemz) Suffix = "/64"; + else if (TargetTriple.getEnvironment() == llvm::Triple::GNUX32) + Suffix = "/x32"; else Suffix = "/32"; @@ -1358,9 +1391,10 @@ } void Generic_GCC::GCCInstallationDetector::ScanLibDirForGCCTriple( - llvm::Triple::ArchType TargetArch, const ArgList &Args, + llvm::Triple TargetTriple, const ArgList &Args, const std::string &LibDir, StringRef CandidateTriple, bool NeedsBiarchSuffix) { + llvm::Triple::ArchType TargetA...

Hi, I'm working on bringing up complete coverage for a Gentoo x32 "desktop" system. I've been cooking up quite a few patches for various packages to push upstream, but right now, the biggest blocker is the lack of support for building with/codegen targeting x32 in llvm/clang. Since the x32 patches were sent last year, I see support code has landed in LLVM, and basic handling of

...8 @@ TargetArch == llvm::Triple::ppc64 || TargetArch == llvm::Triple::systemz) Suffix = "/64"; + else if (TargetTriple.getEnvironment() == llvm::Triple::GNUX32) + Suffix = "/x32"; else Suffix = "/32"; @@ -1358,9 +1391,10 @@ } void Generic_GCC::GCCInstallationDetector::ScanLibDirForGCCTriple( - llvm::Triple::ArchType TargetArch, const ArgList &Args, + llvm::Triple TargetTriple, const ArgList &Args, const std::string &LibDir, StringRef CandidateTriple, bool NeedsBiarchSuffix) { + llvm::Triple::ArchType TargetA...

Hi, We are now about halfway between the 3.4 and 3.5 releases, and I would like to start preparing for a 3.4.1 release. Here is my proposed release schedule: Mar 26 - April 9: Identify and backport additional bug fixes to the 3.4 branch. April 9 - April 18: Testing Phase April 18: 3.4.1 Release How you can help: - If you have any bug fixes you think should be included to 3.4.1, send me an