It's one of the things in the standard where it isn't defined directly because it's assumed that everyone understands what it means, the same way that the standard doesn't define what it means for two pointers to point to "the same address". That can get tricky around things like segmentation or bank switching where there can be multiple bit patterns that resolve to the same address, and rather than having to come up with a bunch of clauses that specify exactly how comparison should work for all possible addressing schemes that could ever exist the standard just assumes that everyone knows what it means without having to rigourously define it.

On 27 April 2025 09:15:22 BST, Federico Kircheis <federico_at_[hidden]> wrote:
>On 26/04/2025 10:44 pm, Jennifier Burnett wrote:
>>> But I am not able to find what "the same function" actually means.
>>
>> It isn't explicitly defined in the standard, it's normative.
>>
>
>Sorry, I'm not sure what that means.
>Could you clarify it for me?