On Mon, Oct 24, 2016 at 7:15 PM, Jerry DeLisle <jvdeli...@charter.net> wrote: > On 10/24/2016 07:49 AM, Janne Blomqvist wrote: >> >> On Mon, Oct 24, 2016 at 2:53 PM, Jerry DeLisle <jvdeli...@charter.net> >> wrote: >>> >>> On 10/18/2016 04:48 PM, Jerry DeLisle wrote: >>>> >>>> >>>> Hi Folks, >>>> >>>> The attached patch does some minor cleanup and bumps the libgfortran >>>> version >>>> number. I have wanted to reorder the dtp structure for many years now. >>>> Not >>>> strictly needed but it has bugged me forever. >>>> >>>> The bump is needed because of the significant changes from >>>> implementation >>>> of DTIO. >>>> >>> >>> --- snip --- >>> >>> Revised patch. Changed a single byte char to int for better memory >>> alignment >>> on 32 bit boundaries. Regression tested on x86-64-linux, FreeBSD, and >>> Power8. >>> >>> I plan to commit this to trunk sometime today. >> >> >> I understood from https://gcc.gnu.org/ml/fortran/2016-10/msg00168.html >> that fortran-dev won't be in shape for merging until GCC 8 stage 1. If >> so, shouldn't we avoid breaking the ABI until then? >> > > The ABI is already changed with the UD-DTIO changes, so we need to bump > version to avoid surprises with other earlier versions.
Ugh. Is is possible to un-break the ABI then, or is the plan to merge fortran-dev regardless and fix the performance issues later? Seems to me that breaking the ABI for GCC 7 and again for GCC 8 is the worst choice. -- Janne Blomqvist
