On Mon, Mar 2, 2020 at 3:46 AM Jakub Jelinek <ja...@redhat.com> wrote: > > On Mon, Mar 02, 2020 at 03:41:06AM -0800, H.J. Lu wrote: > > On Mon, Mar 2, 2020 at 2:46 AM Jakub Jelinek <ja...@redhat.com> wrote: > > > > > > The second release candidate for GCC 8.4 is available from > > > > > > https://gcc.gnu.org/pub/gcc/snapshots/8.4.0-RC-20200302/ > > > ftp://gcc.gnu.org/pub/gcc/snapshots/8.4.0-RC-20200302/ > > > > > > and shortly its mirrors. It has been generated from git commit > > > r8-10102-g0afd41f8e6530b13421679801cf73cb6bef55553. > > > > > > I have so far bootstrapped and tested the release candidate on > > > x86_64-linux and i686-linux. Please test it and report any issues to > > > bugzilla. > > > > > > If all goes well, I'd still like to release 8.4 on Wednesday, March 4th. > > > > > > > I'd like to backport: > > > > commit r10-6965-g577350603a657590c4b54a4a966cb49497e2514c > > Author: H.J. Lu <hjl.to...@gmail.com> > > Date: Mon Mar 2 03:08:57 2020 -0800 > > > > lto: Also copy .note.gnu.property section > > > > When generating the separate file with LTO debug sections, we should > > also copy .note.gnu.property section. > > > > PR lto/93966 > > * simple-object.c (handle_lto_debug_sections): Also copy > > .note.gnu.property section. > > > > to GCC 8. Is it OK? > > Richi said on IRC that GCC 8 is unaffected and does copy all sections.
GCC 8 is affected. > Also, I've made GCC 8.4-rc2 already and would strongly prefer not to do > another one, so if it is needed even for GCC 8, my preference would be > defer til 8.5 (i.e. commit after Wednesday). I will do it for Wednesday. -- H.J.
