On 01/04/2018 10:52 AM, Richard Sandiford wrote:
Martin Sebor writes:
In addition to assuming that built-in functions are called with
the correct number of arguments (bug 83603), the restrict pass
also assumes that they are called with arguments of the expected
types. When a built-in is declar
Martin Sebor writes:
> In addition to assuming that built-in functions are called with
> the correct number of arguments (bug 83603), the restrict pass
> also assumes that they are called with arguments of the expected
> types. When a built-in is declared with no prototype and called
> with argum
On 01/02/2018 04:02 PM, Martin Sebor wrote:
> In addition to assuming that built-in functions are called with
> the correct number of arguments (bug 83603), the restrict pass
> also assumes that they are called with arguments of the expected
> types. When a built-in is declared with no prototype a
In addition to assuming that built-in functions are called with
the correct number of arguments (bug 83603), the restrict pass
also assumes that they are called with arguments of the expected
types. When a built-in is declared with no prototype and called
with arguments of the wrong type (such as
