]> git.ipfire.org Git - thirdparty/gcc.git/commit
ranger: Verify gimple_call_num_args for several builtins [PR123431]
authorJakub Jelinek <jakub@redhat.com>
Sat, 10 Jan 2026 10:35:30 +0000 (11:35 +0100)
committerJakub Jelinek <jakub@gcc.gnu.org>
Sat, 10 Jan 2026 10:35:30 +0000 (11:35 +0100)
commit8a6ff9ca60cf532f5b4fa55a85a289076819e625
tree4ce85bf4ec7687e42398e15531481e79c22b5ac6
parent00b6346d5374efab8dabbf99d2647ad69b1df706
ranger: Verify gimple_call_num_args for several builtins [PR123431]

While gimple_call_combined_fn already do call
gimple_builtin_call_types_compatible_p and for most of builtins ensures
the right types of arguments, for type generic builtins it does not,
from POV of that function those functions are rettype (...).
Now, while the FE does some number of argument checking for the type
generic builtins, as the testcase below shows, it can be gamed.

So, this patch checks the number of arguments for type generic builtins
and does nothing if they have unexpected number of arguments.
Also for the returns arg verifies it can access the first argument.

2026-01-10  Jakub Jelinek  <jakub@redhat.com>

PR tree-optimization/123431
* gimple-range-op.cc (gimple_range_op_handler::maybe_builtin_call):
Punt if type-generic builtins with a single argument don't have
exactly one argument.  For returns_arg punt if call doesn't have
at least one argument.

* gcc.dg/pr123431.c: New test.
gcc/gimple-range-op.cc
gcc/testsuite/gcc.dg/pr123431.c [new file with mode: 0644]