svn commit: r331838 - in stable/11: . contrib/compiler-rt/include/sanitizer contrib/compiler-rt/include/xray contrib/compiler-rt/lib/BlocksRuntime contrib/compiler-rt/lib/asan contrib/compiler-rt/l...

[Warner Losh]

On Mon, Apr 2, 2018, 10:22 PM Ian Lepore <ian at freebsd.org> wrote:

> On Mon, 2018-04-02 at 19:02 -0700, Rodney W. Grimes wrote:
> > >
> > > So, the takeaway is, this change stays, and stable/11 users that build
> > > their own ports are on their own?
> > >
> > > Whatever happened to POLA?
> > I have no idea, but I fully agree that changing compilers 30 days before
> > a code slush is just a very bad move.
> >
> > The llvm in 11.1 is 4.
> > Is there some pressing reason that we need llvm 6 to be in release 11.2?
> >
> > Looks like I wont be upgrading to 11.2 as I am sure I'll have blocking
> > issues with some ports.
> >
> > Though I could probably build them with 11.1, I hate that idea as then
> > I have to keep an 11.1 around incase I need to rebuild something.
> >
> > :-(
>
> I was hoping to import 11.2 to our repo at $work and be shipping
> products based on it later this year. But there's no way we have
> resources available to sidetrack and start debugging out of the blue
> failures of ports that have been working fine for us until now. I guess
> the best I can do now is import 11-stable immediately before the
> compiler change. At least I was lucky enough to get all the arm changes
> important for us MFC'd before the compiler change.
>

All depends on which ports are broken... would be nice to have a list...

Warner

>