On Tue, Mar 27, 2018 at 6:32 AM, Richard Biener <rguent...@suse.de> wrote: > > Status > ====== > > The GCC 8 trunk is open for regression and documentation fixes. Following > past releases we are aiming at a first release candidate mid April though > if you look at the quality data below that looks ambitious. > > So please help tackling (and confirming, bisecting, reducing, etc.) > regressions to make a timely release of GCC 8 possible. > > > Quality Data > ============ > > Priority # Change from last report > -------- --- ----------------------- > P1 22 - 14 > P2 104 - 29 > P3 15 - 42 > P4 183 + 25 > P5 26 - 1 > -------- --- ----------------------- > Total P1-P3 141 - 85 > Total 350 - 61 > > > Previous Report > =============== > > https://gcc.gnu.org/ml/gcc/2018-01/msg00083.html
I have 3 Intel CET patches pending review: https://gcc.gnu.org/ml/gcc-patches/2018-03/msg01356.html https://gcc.gnu.org/ml/gcc-patches/2017-12/msg00485.html https://gcc.gnu.org/ml/gcc-patches/2017-10/msg01741.html I also opened: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85086 I have a patch at https://github.com/hjl-tools/gcc/commit/e9ff815941406e38fa629947af4d809b9129e860 which requires unwind ABI extension. I'd like to see them fixed to get working Intel CET support in GCC 8. Thanks. -- H.J.
