Re: clang default: when?

[Jiri B]

On Mon, Jan 23, 2017 at 11:41:37PM +0800, Tinker wrote:
> Ah. So.. support for compiling all the default distro with both gcc and
> clang, for all platforms, is in the works?
> 
> Did arm64 spark this because the clang was better suited for arm64 for some
> reason, if so which?

Maybe you should follow https://marc.info/?l=openbsd-cvs=2=1=llvm=b

j.

Re: clang default: when?

[Stuart Henderson]

On 2017-01-23, Tinker  wrote:
> On 2017-01-23 23:36, Stuart Henderson wrote:
>> On 2017-01-23, Андрей Болконский  wrote:
>>> when you done migration to clang compiler on openbsd base system amd64 
>>> (and
>>> i386)?
>> 
>> When it's ready.
>
> Ah. So.. support for compiling all the default distro with both gcc and 
> clang, for all platforms, is in the works?

I'm not working on it myself (though I'll probably help in ports-land),
but I doubt that there's any plan to compile any particular platform with
_both_. That never happened when we've had a choice of compilers before.

> Did arm64 spark this because the clang was better suited for arm64 for 
> some reason, if so which?

GCC started supporting aarch64 in 4.8 (a GPLv3 version), so the GPLv2-
licensed version of GCC in base was a non-starter.

Re: clang default: when?

[Tinker]

On 2017-01-23 23:36, Stuart Henderson wrote:

On 2017-01-23, Андрей Болконский  wrote:
when you done migration to clang compiler on openbsd base system amd64 
(and

i386)?


When it's ready.


Ah. So.. support for compiling all the default distro with both gcc and 
clang, for all platforms, is in the works?


Did arm64 spark this because the clang was better suited for arm64 for 
some reason, if so which?

Re: clang default: when?

[Stuart Henderson]

On 2017-01-23, Андрей Болконский  wrote:
> when you done migration to clang compiler on openbsd base system amd64 (and
> i386)?

When it's ready.

clang default: when?

[Андрей Болконский]

when you done migration to clang compiler on openbsd base system amd64 (and
i386)?