[5.0.0 Release] Please help fix the remaining blockers (2 days left!)

Hello everyone,

According to the release schedule, we're supposed to be tagging
'final' on Wednesday. Unfortunately, I suspect we will be a little
late.

There are currently 32 open release blockers:
https://bugs.llvm.org/buglist.cgi?f1=blocked&o1=equals&v1=33849&query_format=advanced&resolution=---

Some of those have traction, but many don't. Some just need bisection,
checking if the issue still reproduces, etc.

Please help take a look at the bugs in that list. It would be really
great if we could drive it down to zero blockers and tag rc3 by the
end of the week.

Many thanks,
Hans

Hello everyone,

According to the release schedule, we're supposed to be tagging
'final' on Wednesday. Unfortunately, I suspect we will be a little
late.

There are currently 32 open release blockers:
https://bugs.llvm.org/buglist.cgi?f1=blocked&o1=equals&v1=33849&query_format=advanced&resolution=---

Some of those have traction, but many don't. Some just need bisection,
checking if the issue still reproduces, etc.

Please help take a look at the bugs in that list. It would be really
great if we could drive it down to zero blockers and tag rc3 by the
end of the week.

It would be nice to backport this patch as is to 5.0.0.

"Use sys::Memory::AllocateRWX for JIT code"
https://reviews.llvm.org/D35558

It JIT unbreaks code for NetBSD-8.x.

A proper solution, to revamp the JIT code, with a better API is under
development and should land LLVM-6.0.0.

It sounds like the review is stuck though. I'd rather not block on it.