On Tue, 31 May 2016, Kyrill Tkachov wrote: > Hi Richard, > > On 27/05/16 12:43, Richard Biener wrote: > > The first release candidate for GCC 5.4 is available from > > > > ftp://gcc.gnu.org/pub/gcc/snapshots/5.4.0-RC-20160527 > > > > and shortly its mirrors. It has been generated from SVN revision 236809. > > > > I have sofar bootstrapped the release candidate on x86_64-suse-linux-gnu. > > > > Please test the release candidate and report any issues to bugzilla. > > > > If all goes well I'd like to release GCC 5.4 at the beginning of next > > week. > > > > Bootstrap and test on arm-none-linux-gnueabihf looks fine. > Unfortunately, on aarch64-none-linux-gnu I noticed a regression compared to > GCC 5.3: > FAIL: gcc.target/aarch64/vbslq_u64_1.c scan-assembler-times bif\\tv 1 > > This is PR 68696 that has been triggered on that branch. > The patch fixing that is at: > https://gcc.gnu.org/ml/gcc-patches/2015-12/msg00826.html > > I have bootstrapped and tested it on aarch64-none-linux-gnu on top of the 5.4 > RC > and it fixes the regression. It applies cleanly to that branch. > > Is it okay to backport it to the branch?
While it doesn't look like having the same cause (r231178) the patch looks safe to me to backport. Thus, ok. Thanks, Richard. > Thanks, > Kyrill > > -- Richard Biener <rguent...@suse.de> SUSE LINUX GmbH, GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nuernberg)