On Wed, 15 Feb 2012, Christian Bruel wrote: > Removal of this NOP_EXPR if !CAN_HAVE_LOCATION_P fixes the problem. > looks safe from my testing, because the loc is inserted using > 'protected_set_expr_location', whereas no loc for a constant case > doesn't seem to introduce new problems with the debugging information. > But in case I also added a few paranoid gcc_assert.
Is it safe to set TREE_NO_WARNING without that check? I'd have thought the check was to avoid setting TREE_NO_WARNING on a shared node when warnings are to be disabled in only one context where that node is used. -- Joseph S. Myers jos...@codesourcery.com
