On Thu, Mar 12, 2015 at 11:51:51AM +0300, Ilya Enkovich wrote: > On 09 Mar 15:51, Jakub Jelinek wrote: > > On Mon, Mar 02, 2015 at 01:25:43PM +0300, Ilya Enkovich wrote: > > > > --- a/gcc/toplev.c > > > > +++ b/gcc/toplev.c > > > > @@ -1376,6 +1376,11 @@ process_options (void) > > > > { > > > > if (targetm.chkp_bound_mode () == VOIDmode) > > > > error ("-fcheck-pointer-bounds is not supported for this > > > > target"); > > > > + > > > > + if (flag_sanitize & SANITIZE_ADDRESS) > > > > + error ("-fcheck-pointer-bounds is not supported with Address > > > > Sanitizer"); > > > > + > > > > + flag_check_pointer_bounds = 0; > > > > } > > > > Doesn't this disable -fcheck-pointer-bounds always? > > I'd expect you want to clear flag_check_pointer_bounds only if you issued > > one of the two errors... > > > > Jakub > > Whoops! Here is a less destructive version.
Ok for trunk. Did the old version pass make check? If so, perhaps you want to add (incrementally) some test that would actually verify that -fcheck-pointer-bounds does what it should do (e.g. by scanning tree dumps etc.). Jakub