On Mar 24, 2021, Jonathan Wakely <jwak...@redhat.com> wrote: > This works for me on x86_64-linux and powerpc64le-linux, and also on > x86_64-linux when I kluge the config macros so that the new code path > gets used. Does this work for VxWorks?
Thanks. I (trivially) backported it to apply on our gcc-10 tree, and tested that on x86_64-vx7r2, and I confirm it works there too. However, I suspect there's a series of typos in the patch. You appear to be using the 'which' enum variable for bit testing, but with '|' rather than '&'. Unless I'm missing something in my reading of the modified code, this may cause a backend different from that requested by the token to be selected, but it doesn't look like we have any test that detects this problem. -- Alexandre Oliva, happy hacker https://FSFLA.org/blogs/lxo/ Free Software Activist GNU Toolchain Engineer Vim, Vi, Voltei pro Emacs -- GNUlius Caesar
