llvm dev - Jan 2013 - [LLVMdev] Using C++'11 language features in LLVM itself

It's not a coincidence that GCC 4.2.1 is the baseline on FreeBSD 
considering the licensing of GPL restrictions on new releases.

- Marc

On 01/08/2013 04:46 PM, Krzysztof Parzyszek wrote:
> On 1/8/2013 5:45 PM, Chris Lattner wrote:
>>
>> some version of Clang and later (Freebsd folks?).
>
> FreeBSD 9.1 uses GCC 4.2.1 and Clang 3.0, although I have some doubts 
> about the clang, at least on PPC32.  Trunk clang compiled with the 
> system clang crashes on code that the same trunk clang compiles fine 
> when built with gcc.  It may as well be a source problem in trunk 
> though...
>
> -Krzysztof
>
>
-- 
Marc J. Driftmeyer
Email :: mjd at reanimality.com <mailto:mjd at reanimality.com>
Web :: http://www.reanimality.com
Cell :: (509) 435-5212
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20130108/57f4631f/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: mjd.vcf
Type: text/x-vcard
Size: 317 bytes
Desc: not available
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20130108/57f4631f/attachment.vcf>

On 9 Jan 2013, at 04:49, Marc J. Driftmeyer wrote:
> It's not a coincidence that GCC 4.2.1 is the baseline on FreeBSD
considering the licensing of GPL restrictions on new releases.
[With my FreeBSD hat on]

Our plan for 10.0 is to ship clang only, with gcc 4.2.1 relegated to a compat
package for tier 1 architectures.  This should be x86, x86-64, and ARMv6/7 (and
maybe v8 if we're very lucky, but probably not).  MIPS and PowerPC are
slowly migrating to clang, but will probably take a little bit longer (although
given the progress that these are making, possibly not).  As these are tier 2
architectures, I don't have a problem requiring an external compiler or a
cross compiler for the initial bootstrap build.

However, our release cycle is (in theory) 6 months, but is out of phase with
LLVM's and so at any given point we are likely to be one or two releases
behind.

As such, it's important to us to be able to build trunk clang with clang
from at least two releases ago, and ideally four.  Losing this ability makes it
very difficult for us to do the bootstrap toolchain build.

David

On Jan 9, 2013, at 2:38 AM, David Chisnall <David.Chisnall at
cl.cam.ac.uk> wrote:
> On 9 Jan 2013, at 04:49, Marc J. Driftmeyer wrote:
> 
>> It's not a coincidence that GCC 4.2.1 is the baseline on FreeBSD
considering the licensing of GPL restrictions on new releases.
> 
> [With my FreeBSD hat on]
> 
> Our plan for 10.0 is to ship clang only, with gcc 4.2.1 relegated to a
compat package for tier 1 architectures.  This should be x86, x86-64, and
ARMv6/7 (and maybe v8 if we're very lucky, but probably not).  MIPS and
PowerPC are slowly migrating to clang, but will probably take a little bit
longer (although given the progress that these are making, possibly not).  As
these are tier 2 architectures, I don't have a problem requiring an external
compiler or a cross compiler for the initial bootstrap build.
Ok, that's good news!
> 
> However, our release cycle is (in theory) 6 months, but is out of phase
with LLVM's and so at any given point we are likely to be one or two
releases behind.
> 
> As such, it's important to us to be able to build trunk clang with
clang from at least two releases ago, and ideally four.  Losing this ability
makes it very difficult for us to do the bootstrap toolchain build.

Can you make this more concrete for me?  If we made this change in LLVM 3.3,
what version of Clang would you need us to be compatible with?  Would it be ok
to require Clang 3.1 or later, or do you need clang 3.0 support?

-Chris