aboutsummaryrefslogtreecommitdiff
path: root/gcc/rust/backend/rust-compile-context.h
diff options
context:
space:
mode:
authorJakub Jelinek <jakub@redhat.com>2025-03-21 12:18:35 +0100
committerJakub Jelinek <jakub@gcc.gnu.org>2025-03-21 12:18:35 +0100
commit28caa267dc757d80ffe37d638d981d3572c164ae (patch)
tree4a29c7b8a8f4b45332958b2288d0234584eed923 /gcc/rust/backend/rust-compile-context.h
parent589c94da22ec71fe8518878e801e88b05deffe18 (diff)
downloadgcc-28caa267dc757d80ffe37d638d981d3572c164ae.zip
gcc-28caa267dc757d80ffe37d638d981d3572c164ae.tar.gz
gcc-28caa267dc757d80ffe37d638d981d3572c164ae.tar.bz2
icf: Punt for musttail call flag differences in ICF [PR119376]
The following testcase shows we were ignoring musttail flags on calls when deciding if two functions are the same. That can result in problems in both directions, either we silently lose musttail attribute because there is a similar function without it earlier and then we e.g. don't diagnose if it can't be tail called or don't try harder to do a tail call, or we get it even in functions which didn't have it before. The following patch for now just punts if it differs. Perhaps we could just merge it and get musttail flag if any of the merged functions had one in such position, but it feels to me that it is now too late in GCC 15 cycle to play with this. 2025-03-21 Jakub Jelinek <jakub@redhat.com> PR ipa/119376 * ipa-icf-gimple.cc (func_checker::compare_gimple_call): Return false for gimple_call_must_tail_p mismatches. * c-c++-common/musttail27.c: New test.
Diffstat (limited to 'gcc/rust/backend/rust-compile-context.h')
0 files changed, 0 insertions, 0 deletions