On Wed, Jun 13, 2018 at 5:08 PM, Jakub Jelinek <ja...@redhat.com> wrote: > > On Wed, Jun 13, 2018 at 04:12:25PM -0400, Jason Merrill wrote: > > On Mon, Jun 11, 2018 at 2:38 PM, Jason Merrill <ja...@redhat.com> wrote: > > > The fix for 80178 was broken, because I forgot that copy_fn_p is false > > > for move constructors. As a result, the calling convention for a > > > class with a trivial move constructor and deleted copy constructor > > > changed inappropriately. > > > > This patch restores the broken behavior to -fabi-version=12 and adds > > -fabi-version=13 for the fix; people can use -Wabi=12 with GCC 8.2 to > > check for compatibility issues against 8.1, or -Wabi=11 to check > > compatibility with GCC 7. > > > > Tested x86_64-pc-linux-gnu, applying to trunk and 8. Do we want to > > accelerate 8.2 because of this issue? > > I'd like to see the powerpc64le-linux __ieee128 long double support in 8.2 > too, accelerating 8.2 because of this would make that impossible.
I'd think we could put that support in an August release regardless of what version number is on that release. Is it important that it be numbered 8.2? Jason
