On Wed, Sep 15, 2021 at 5:39 PM Jason Merrill via Gcc-patches < gcc-patches@gcc.gnu.org> wrote:
> On Wed, Sep 15, 2021 at 11:37 AM Jeff Law <jeffreya...@gmail.com> wrote: > > > > > > > On 9/15/2021 9:31 AM, Jason Merrill via Gcc-patches wrote: > > > Most any compilation on ARM/AArch64 was warning because the default L1 > > cache > > > line size of 32B was smaller than the default > > > std::hardware_constructive_interference_size of 64B. This is mostly > due > > to > > > inaccurate --param l1-cache-line-size, but it's not helpful to complain > > to a > > > user that didn't set the values. > > > > > > gcc/cp/ChangeLog: > > > > > > * decl.c (cxx_init_decl_processing): Only warn about odd > > > interference sizes if they were specified with --param. > > I wonder if that'll fix the arm-linux build failures that started > > showing up recently: > > > > armeb-linux-gnueabi: > > > > <built-in>: error: '--param constructive-interference-size=64' is > > greater than '--param l1-cache-line-size=32' [-Werror=interference-size] > > > > I expect the other arm- linux configurations would show it as well, but > > they're only run once a week in my tester and I don't think they've been > > run since the recent changes in this space. > > > > Yes, that is exactly the purpose of this change. > > I can confirm that those targets build again, thanks. > Jason >