Re: Memory access in GIMPLE

2025-04-04 Thread Richard Biener via Gcc
gt; >> > >> As before, each section starts with a description of the semantics I've > >> implemented (or plan to implement), followed by concrete questions if > >> relevant. Let me know if the described semantics are incorrect or > >> incomplete. > &g

Re: Memory access in GIMPLE

2025-04-03 Thread Krister Walfridsson via Gcc
ed by concrete questions if relevant. Let me know if the described semantics are incorrect or incomplete. Accessing memory Memory access in GIMPLE is done using GIMPLE_ASSIGN statements where the lhs and/or rhs is a memory reference expression (such as MEM_REF). When both lhs an

Re: Memory access in GIMPLE

2025-04-02 Thread Richard Biener via Gcc
s if > relevant. Let me know if the described semantics are incorrect or > incomplete. > > > Accessing memory > > Memory access in GIMPLE is done using GIMPLE_ASSIGN statements where the > lhs and/or rhs is a memory reference expression (such as MEM_REF). W

Memory access in GIMPLE

2025-04-02 Thread Krister Walfridsson via Gcc
plete. Accessing memory Memory access in GIMPLE is done using GIMPLE_ASSIGN statements where the lhs and/or rhs is a memory reference expression (such as MEM_REF). When both lhs and rhs access memory, one of the following must hold -- otherwise the access is UB: 1. There is no ov