Re: clang broken on current?

2019-02-10 Thread Mark Millard via freebsd-toolchain
On 2019-Feb-10, at 12:02, Mark Millard wrote: > On 2019-Feb-10, at 11:34, Steve Kargl > wrote: > >> Having set CFLAGS+=-march=native -mtune=native and trying to >> force qt5-gui configure with -sse2 option, I have a config.summary >> that contains (my in-line comments ***) >> >> Build ty

Re: clang broken on current?

2019-02-10 Thread Mark Millard via freebsd-toolchain
On 2019-Feb-10, at 11:34, Steve Kargl wrote: > Having set CFLAGS+=-march=native -mtune=native and trying to > force qt5-gui configure with -sse2 option, I have a config.summary > that contains (my in-line comments ***) > > Build type: freebsd-clang (i386, CPU features: ) > > *** What? *

Re: clang broken on current?

2019-02-10 Thread Mark Millard via freebsd-toolchain
On 2019-Feb-10, at 11:24, Steve Kargl wrote: > On Sun, Feb 10, 2019 at 11:13:09AM -0800, Mark Millard wrote: >> >> On 2019-Feb-10, at 10:46, Steve Kargl >> wrote: >>> >>> On Sun, Feb 10, 2019 at 12:03:55PM +0100, Dimitry Andric wrote: On 10 Feb 2019, at 06:00, Steve Kargl >>> troutma

Re: clang broken on current?

2019-02-10 Thread Steve Kargl
Having set CFLAGS+=-march=native -mtune=native and trying to force qt5-gui configure with -sse2 option, I have a config.summary that contains (my in-line comments ***) Build type: freebsd-clang (i386, CPU features: ) *** What? *** Compiler: clang 7.0.1 Configuration: compile_examples largefi

Re: clang broken on current?

2019-02-10 Thread Steve Kargl
On Sun, Feb 10, 2019 at 11:13:09AM -0800, Mark Millard wrote: > > On 2019-Feb-10, at 10:46, Steve Kargl > wrote: > > > > On Sun, Feb 10, 2019 at 12:03:55PM +0100, Dimitry Andric wrote: > >> On 10 Feb 2019, at 06:00, Steve Kargl >> troutmask.apl.washington.edu> wrote: > >> > >> How did you arr

Re: clang broken on current?

2019-02-10 Thread Mark Millard via freebsd-toolchain
On 2019-Feb-10, at 10:46, Steve Kargl wrote: > > On Sun, Feb 10, 2019 at 12:03:55PM +0100, Dimitry Andric wrote: >> On 10 Feb 2019, at 06:00, Steve Kargl >> wrote: >> >> How did you arrive at the conclusion that this has anything to do with >> the specific compiler? From these errors, I t

Re: clang broken on current?

2019-02-10 Thread Steve Kargl
On Sun, Feb 10, 2019 at 12:03:55PM +0100, Dimitry Andric wrote: > On 10 Feb 2019, at 06:00, Steve Kargl > wrote: > > How did you arrive at the conclusion that this has anything to do with > the specific compiler? From these errors, I think it is more likely > something in Qt5 that is erroneousl

Re: clang broken on current?

2019-02-10 Thread Steve Kargl
On Sun, Feb 10, 2019 at 12:03:55PM +0100, Dimitry Andric wrote: > On 10 Feb 2019, at 06:00, Steve Kargl > wrote: > > > > If I add 'CFLAGS+=-march=native -mtune=native', I can build > > world and kernel without a problem. If I try to build > > x11-toolkits/qt5-gui the build dies with > > Might

Re: clang broken on current?

2019-02-10 Thread Steve Kargl
On Sun, Feb 10, 2019 at 12:03:55PM +0100, Dimitry Andric wrote: > On 10 Feb 2019, at 06:00, Steve Kargl > wrote: > > > > If I add 'CFLAGS+=-march=native -mtune=native', I can build > > world and kernel without a problem. If I try to build > > x11-toolkits/qt5-gui the build dies with > > > > H

Re: clang broken on current?

2019-02-10 Thread Steve Kargl
On Sun, Feb 10, 2019 at 12:03:55PM +0100, Dimitry Andric wrote: > On 10 Feb 2019, at 06:00, Steve Kargl > wrote: > > > > I have > > > > % uname -a > > FreeBSD mobile 13.0-CURRENT FreeBSD 13.0-CURRENT r343477 MOBILE i386 > > > > % dmesg | more > > ... > > FreeBSD clang version 7.0.1 (tags/RELE

Re: clang broken on current?

2019-02-10 Thread Dimitry Andric
On 10 Feb 2019, at 06:00, Steve Kargl wrote: > > I have > > % uname -a > FreeBSD mobile 13.0-CURRENT FreeBSD 13.0-CURRENT r343477 MOBILE i386 > > % dmesg | more > ... > FreeBSD clang version 7.0.1 (tags/RELEASE_701/final 349250) (based on LLVM > 7.0.1) > VT(vga): resolution 640x480 > CPU: Int