Re: [PATCH] tree-optimization/109609 - correctly interpret arg size in fnspec

2023-04-25 Thread Jan Hubicka via Gcc-patches
> By majority vote and a hint from the API name which is > arg_max_access_size_given_by_arg_p this interprets a memory access > size specified as given as other argument such as for strncpy > in the testcase which has "1cO313" as specifying the _maximum_ > size read/written rather than the exact si

[PATCH] tree-optimization/109609 - correctly interpret arg size in fnspec

2023-04-25 Thread Richard Biener via Gcc-patches
By majority vote and a hint from the API name which is arg_max_access_size_given_by_arg_p this interprets a memory access size specified as given as other argument such as for strncpy in the testcase which has "1cO313" as specifying the _maximum_ size read/written rather than the exact size. There