search for: generic_elf

...ing used as the system compiler, to have 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

On 19 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

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

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

On Fri, May 22, 2015 at 9:29 AM, Philip Reames <listmail at philipreames.com> wrote: > Let me start by emphasizing that I only speak for myself. This is my > opinion, and nothing more. > > On 05/22/2015 03:55 AM, Neil Henning wrote: >> >> 'Maintenance and support obligations' - the only maintenance obligations >> would be don't regress our tests