aboutsummaryrefslogtreecommitdiff
path: root/gcc/value-range.cc
diff options
context:
space:
mode:
authorMikael Morin <mikael@gcc.gnu.org>2022-08-31 11:00:45 +0200
committerMikael Morin <mikael@gcc.gnu.org>2022-09-25 14:44:53 +0200
commit2b393f6f83903cb836676bbd042c1b99a6e7e6f7 (patch)
tree11dda7d311f3477abab35c27decdf9ea87544c25 /gcc/value-range.cc
parent323c38c915f34883439e9e53b9eac5fe07cb8378 (diff)
downloadgcc-2b393f6f83903cb836676bbd042c1b99a6e7e6f7.zip
gcc-2b393f6f83903cb836676bbd042c1b99a6e7e6f7.tar.gz
gcc-2b393f6f83903cb836676bbd042c1b99a6e7e6f7.tar.bz2
fortran: Move the clobber generation code
This change inlines the clobber generation code from gfc_conv_expr_reference to the single caller from where the add_clobber flag can be true, and removes the add_clobber argument. What motivates this is the standard making the procedure call a cause for a variable to become undefined, which translates to a clobber generation, so clobber generation should be closely related to procedure call generation, whereas it is rather orthogonal to variable reference generation. Thus the generation of the clobber feels more appropriate in gfc_conv_procedure_call than in gfc_conv_expr_reference. Behaviour remains unchanged. gcc/fortran/ChangeLog: * trans.h (gfc_conv_expr_reference): Remove add_clobber argument. * trans-expr.cc (gfc_conv_expr_reference): Ditto. Inline code depending on add_clobber and conditions controlling it ... (gfc_conv_procedure_call): ... to here.
Diffstat (limited to 'gcc/value-range.cc')
0 files changed, 0 insertions, 0 deletions