https://gcc.gnu.org/bugzilla/show_bug.cgi?id=125311
--- Comment #4 from anlauf at gcc dot gnu.org --- (In reply to anlauf from comment #2) > Funny. > > -fcheck=bounds,no-bounds > > is a no-op as expected, but > > -fcheck=bounds -fcheck=no-bounds > > seems to fail. When I add "-v" to the options, I see: COLLECT_GCC_OPTIONS='-fcheck=bounds,no-bounds' ... vs. COLLECT_GCC_OPTIONS='-fbounds-check' '-fcheck=no-bounds' ... Huh? Who rewrites -fcheck=bounds to -fbounds-check ?
