https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66258
--- Comment #7 from jim.wilson at linaro dot org --- On Sat, Jun 6, 2015 at 2:02 AM, pinskia at gcc dot gnu.org <gcc-bugzi...@gcc.gnu.org> wrote: >> Do you plan to backport this to gcc-5-branch? I didn't realize it was broken on the gcc-5 release branch. I only checked mainline. I can check the gcc-5 release branch and backport, but I'm a little out of touch, and not sure what approval I need for the backport. If I can't backport to the FSF gcc-5 release branch for some reason, I can backport to the linaro gcc-5 branch instead. I've also discovered that I got a little bad info on grub. The person who tried -mgeneral-regs-only accidentally compiled linux user space with that option, which is why the build with it failed. Grub itself apparently doesn't use FP. So with correct makefiles, changing grub to use -mgeneral-regs-only instead of +nofp does solve the problem. Since the linux kernel already uses -mgeneral-regs-only, and this option is (presumably) not broken in gcc-5, I believe that grub will be changed to use -mgeneral-regs-only to match the kernel, in which case a build will work with gcc-5. There is still the problem that grub versions before the change was made (this week? last week?) will still fail with gcc-5 unless the patch is backported, or users make local mods to grub to use -mgeneral-regs-only instead of +nofp. Jim
