aboutsummaryrefslogtreecommitdiff
path: root/libphobos/src
diff options
context:
space:
mode:
authorJakub Jelinek <jakub@redhat.com>2020-03-16 09:03:59 +0100
committerJakub Jelinek <jakub@redhat.com>2020-03-16 09:03:59 +0100
commit6d44c881286762628afce5169d921a388ae6a1ff (patch)
tree376e430f555c8c4be0ded35925345b06deb61266 /libphobos/src
parent5ba25b2ef179aec8ba4c47612fbc5c388f41cb36 (diff)
downloadgcc-6d44c881286762628afce5169d921a388ae6a1ff.zip
gcc-6d44c881286762628afce5169d921a388ae6a1ff.tar.gz
gcc-6d44c881286762628afce5169d921a388ae6a1ff.tar.bz2
tree-inline: Fix a -fcompare-debug issue in the inliner [PR94167]
The following testcase fails with -fcompare-debug. The problem is that bar is marked as address_taken only with -g and not without. I've tracked it down to insert_init_stmt calling gimple_regimplify_operands even on DEBUG_STMTs. That function will just insert normal stmts before the DEBUG_STMT if the DEBUG_STMT operand isn't gimple val or invariant. While DCE will turn those statements into debug temporaries, it can cause differences in SSA_NAMEs and more importantly, the ipa references are generated from those before the DCE happens. On the testcase, the DEBUG_STMT value is (int)bar. We could generate DEBUG_STMTs with debug temporaries instead, but I fail to see the reason to do that, DEBUG_STMTs allow other expressions and all we want to ensure is that the expressions aren't too large (arbitrarily complex), but during inlining/function versioning I don't see why something would queue a DEBUG_STMT with arbitrarily complex expressions in there. 2020-03-16 Jakub Jelinek <jakub@redhat.com> PR debug/94167 * tree-inline.c (insert_init_stmt): Don't gimple_regimplify_operands DEBUG_STMTs. * gcc.dg/pr94167.c: New test.
Diffstat (limited to 'libphobos/src')
0 files changed, 0 insertions, 0 deletions