diff options
author | Kewen.Lin <linkw@gcc.gnu.org> | 2022-09-13 04:13:59 -0500 |
---|---|---|
committer | Kewen Lin <linkw@linux.ibm.com> | 2022-09-13 05:39:04 -0500 |
commit | 94504c9ae157db937a2e62d533a36d56598f3c09 (patch) | |
tree | c04e839132473c4111c890780fa3ef0ff3cbdeed /libbacktrace | |
parent | 0ee1548d96884d2689482054d925967a9a21d697 (diff) | |
download | gcc-94504c9ae157db937a2e62d533a36d56598f3c09.zip gcc-94504c9ae157db937a2e62d533a36d56598f3c09.tar.gz gcc-94504c9ae157db937a2e62d533a36d56598f3c09.tar.bz2 |
rs6000: Handle unresolved overloaded builtin [PR105485]
PR105485 exposes that new builtin function framework doesn't handle
unresolved overloaded builtin function well. With new builtin
function support, we don't have builtin info for any overloaded
rs6000_gen_builtins enum, since they are expected to be resolved to
one specific instance. So when function rs6000_gimple_fold_builtin
faces one unresolved overloaded builtin, the access for builtin info
becomes out of bound and gets ICE then.
We should not try to fold one unresolved overloaded builtin there
and as the previous support we should emit one error message during
expansion phase like "unresolved overload for builtin ...".
PR target/105485
gcc/ChangeLog:
* config/rs6000/rs6000-builtin.cc (rs6000_gimple_fold_builtin): Add
the handling for unresolved overloaded builtin function.
(rs6000_expand_builtin): Likewise.
gcc/testsuite/ChangeLog:
* g++.target/powerpc/pr105485.C: New test.
Diffstat (limited to 'libbacktrace')
0 files changed, 0 insertions, 0 deletions