Re: GCC 8.2 Status Report (2018-07-19), branch frozen for release
On Wed, 25 Jul 2018, Richard Earnshaw (lists) wrote: > On 24/07/18 17:30, Richard Biener wrote: > > On July 24, 2018 5:50:33 PM GMT+02:00, Ramana Radhakrishnan > > wrote: > >> On Thu, Jul 19, 2018 at 10:11 AM, Richard Biener > >> wrote: > >>> > >>> Status > >>> == > >>> > >>> The GCC 8 branch is frozen for preparation of the GCC 8.2 release. > >>> All changes to the branch now require release manager approval. > >>> > >>> > >>> Previous Report > >>> === > >>> > >>> https://gcc.gnu.org/ml/gcc/2018-07/msg00194.html > >> > >> Is there any chance we can get some of the spectrev1 mitigation > >> patches reviewed and into 8.2 . > > > > It's now too late for that and it has to wait for 8.2. > > Why? It was waiting on YOU for a review and was posted before you > announced the freeze. There's nothing like posting before freeze gives you extra time like we do when transitioning to stage3. You are requesting a feature backport anyway. Anyway, you got a review from ME that showed the series isn't ready, esp. for going into a stable code-base last minute before a release. But I assume "YOU" addressed all volunteer GCC reviewers. Richard.
Re: GCC 8.2 Status Report (2018-07-19), branch frozen for release
On Wed, 25 Jul 2018, Richard Earnshaw (lists) wrote: > On 24/07/18 17:30, Richard Biener wrote: > > On July 24, 2018 5:50:33 PM GMT+02:00, Ramana Radhakrishnan > > wrote: > >> On Thu, Jul 19, 2018 at 10:11 AM, Richard Biener > >> wrote: > >>> > >>> Status > >>> == > >>> > >>> The GCC 8 branch is frozen for preparation of the GCC 8.2 release. > >>> All changes to the branch now require release manager approval. > >>> > >>> > >>> Previous Report > >>> === > >>> > >>> https://gcc.gnu.org/ml/gcc/2018-07/msg00194.html > >> > >> Is there any chance we can get some of the spectrev1 mitigation > >> patches reviewed and into 8.2 . > > > > It's now too late for that and it has to wait for 8.2. > > Why? It was waiting on YOU for a review and was posted before you > announced the freeze. There's nothing like posting before freeze gives you extra time like we do when transitioning to stage3. You are requesting a feature backport anyway. Anyway, you got a review from ME that showed the series isn't ready, esp. for going into a stable code-base last minute before a release. But I assume "YOU" addressed all volunteer GCC reviewers. Richard.
Re: GCC 8.2 Status Report (2018-07-19), branch frozen for release
On 24/07/18 17:30, Richard Biener wrote: > On July 24, 2018 5:50:33 PM GMT+02:00, Ramana Radhakrishnan > wrote: >> On Thu, Jul 19, 2018 at 10:11 AM, Richard Biener >> wrote: >>> >>> Status >>> == >>> >>> The GCC 8 branch is frozen for preparation of the GCC 8.2 release. >>> All changes to the branch now require release manager approval. >>> >>> >>> Previous Report >>> === >>> >>> https://gcc.gnu.org/ml/gcc/2018-07/msg00194.html >> >> Is there any chance we can get some of the spectrev1 mitigation >> patches reviewed and into 8.2 . > > It's now too late for that and it has to wait for 8.2. Why? It was waiting on YOU for a review and was posted before you announced the freeze. R. > >> It would be quite useful to get these into a release as I see that the >> reviews are kinda petering out and there hasn't been any objection to >> the approach. > > It's not that people only use release tarballs. > > Richard. >> >> >> regards >> Ramana >
Re: GCC 8.2 Status Report (2018-07-19), branch frozen for release
On 24/07/18 17:30, Richard Biener wrote: > On July 24, 2018 5:50:33 PM GMT+02:00, Ramana Radhakrishnan > wrote: >> On Thu, Jul 19, 2018 at 10:11 AM, Richard Biener >> wrote: >>> >>> Status >>> == >>> >>> The GCC 8 branch is frozen for preparation of the GCC 8.2 release. >>> All changes to the branch now require release manager approval. >>> >>> >>> Previous Report >>> === >>> >>> https://gcc.gnu.org/ml/gcc/2018-07/msg00194.html >> >> Is there any chance we can get some of the spectrev1 mitigation >> patches reviewed and into 8.2 . > > It's now too late for that and it has to wait for 8.2. Why? It was waiting on YOU for a review and was posted before you announced the freeze. R. > >> It would be quite useful to get these into a release as I see that the >> reviews are kinda petering out and there hasn't been any objection to >> the approach. > > It's not that people only use release tarballs. > > Richard. >> >> >> regards >> Ramana >
Re: GCC 8.2 Status Report (2018-07-19), branch frozen for release
On July 24, 2018 5:50:33 PM GMT+02:00, Ramana Radhakrishnan wrote: >On Thu, Jul 19, 2018 at 10:11 AM, Richard Biener >wrote: >> >> Status >> == >> >> The GCC 8 branch is frozen for preparation of the GCC 8.2 release. >> All changes to the branch now require release manager approval. >> >> >> Previous Report >> === >> >> https://gcc.gnu.org/ml/gcc/2018-07/msg00194.html > >Is there any chance we can get some of the spectrev1 mitigation >patches reviewed and into 8.2 . It's now too late for that and it has to wait for 8.2. >It would be quite useful to get these into a release as I see that the >reviews are kinda petering out and there hasn't been any objection to >the approach. It's not that people only use release tarballs. Richard. > > >regards >Ramana
Re: GCC 8.2 Status Report (2018-07-19), branch frozen for release
On July 24, 2018 5:50:33 PM GMT+02:00, Ramana Radhakrishnan wrote: >On Thu, Jul 19, 2018 at 10:11 AM, Richard Biener >wrote: >> >> Status >> == >> >> The GCC 8 branch is frozen for preparation of the GCC 8.2 release. >> All changes to the branch now require release manager approval. >> >> >> Previous Report >> === >> >> https://gcc.gnu.org/ml/gcc/2018-07/msg00194.html > >Is there any chance we can get some of the spectrev1 mitigation >patches reviewed and into 8.2 . It's now too late for that and it has to wait for 8.2. >It would be quite useful to get these into a release as I see that the >reviews are kinda petering out and there hasn't been any objection to >the approach. It's not that people only use release tarballs. Richard. > > >regards >Ramana
Re: GCC 8.2 Status Report (2018-07-19), branch frozen for release
On Thu, Jul 19, 2018 at 10:11 AM, Richard Biener wrote: > > Status > == > > The GCC 8 branch is frozen for preparation of the GCC 8.2 release. > All changes to the branch now require release manager approval. > > > Previous Report > === > > https://gcc.gnu.org/ml/gcc/2018-07/msg00194.html Is there any chance we can get some of the spectrev1 mitigation patches reviewed and into 8.2 . It would be quite useful to get these into a release as I see that the reviews are kinda petering out and there hasn't been any objection to the approach. regards Ramana
Re: GCC 8.2 Status Report (2018-07-19), branch frozen for release
On Thu, Jul 19, 2018 at 10:11 AM, Richard Biener wrote: > > Status > == > > The GCC 8 branch is frozen for preparation of the GCC 8.2 release. > All changes to the branch now require release manager approval. > > > Previous Report > === > > https://gcc.gnu.org/ml/gcc/2018-07/msg00194.html Is there any chance we can get some of the spectrev1 mitigation patches reviewed and into 8.2 . It would be quite useful to get these into a release as I see that the reviews are kinda petering out and there hasn't been any objection to the approach. regards Ramana
