The problem apparently is that the -mr10k-cache-barrier=store option is nowrejected for CPUs other than r10k. Explicitly including the CPU in thecheck fixes this and is safe because both options were introduced ingcc-4.4.