On 7/22/20 1:31 PM, Tianon Gravi wrote: > On Fri, 15 May 2020 at 10:15, Rod Smith <rodsm...@rodsbooks.com> wrote: >> The below-described bug can be fixed with a change to compiler options >> -- namely, adding -fno-tree-loop-distribute-patterns. I've implemented >> this change in commit e34a16 on the rEFInd Sourceforge git repository: >> >> https://sourceforge.net/p/refind/code/commit_browser >> >> This change doesn't seem to negatively affect compilation on earlier >> versions of GCC (at least, not GCC 7.5.0, which is what my main >> development system uses); but AFAIK there's also no benefit to applying >> this change unless it's necessary, so I don't think there's a need to >> apply the patch unless rEFInd is being built on a system with GCC 10. > > It looks like this is more urgent now (refind will be kicked out of > Debian Bullseye/Testing soon if we don't fix it) -- did you want to do > a new upstream release with this change, or would you prefer I just > cherry pick that one commit into a patch in Debian for now? > > (I don't have a strong preference either way. Happy to do whatever you > prefer!)
At the moment, I don't have enough changes to justify a 0.12.1 release -- just the GCC 10 fix, a few small documentation changes, and the addition of a Debian Secure Boot key. I don't think I've got any actual code changes waiting, unless I'm missing something in my git logs. Thus, I'd suggest you just cherry-pick that one commit, which is a one-line change to Make.common. -- Rod Smith rodsm...@rodsbooks.com
