On Mon, 27 Feb 2023 at 11:15, Aditya saini via Gcc wrote:
>
> Hi , Carolyn Clarke
> I am interested to participate in the GSOC 2023.
> Sorry for the late reply, I don't know why this mail is in my spam folder..
Because it's spam, and the sender has nothing to do with GSoC.
> Please guide me with
Hi , Carolyn Clarke
I am interested to participate in the GSOC 2023.
Sorry for the late reply, I don't know why this mail is in my spam folder..
Please guide me with the next step.
Regards
Aditya Saini..
On Tue, 21 Feb, 2023, 9:50 PM Carolyn Clarke via Gcc,
wrote:
> Good day to you,
>
> I've vi
Richard Henderson wrote:
As a practical short-term concern, rtx_addr_can_trap_p will not return
true for any stack based reference, including push/pop. So for 4.1,
nothing need be done. Longer term, the answer to the "what does notrap
Actually, the SHcompact save / restores use neither
On Thu, Sep 01, 2005 at 08:52:29PM +0100, Joern RENNECKE wrote:
> What are the exact semantics of MEM_NOTRAP_P ? The documentation
> does not agree with the source. reload sets MEM_NOTRAP_P on
> registers that are spilled to memory. However, writing to these
> MEMs can trap if we have a stack ov
My current thinking is that, with a few exceptions like prologue
and epilogue generation, it should be considered a BUG if a port
uses gen_rtx_MEM. Almost always one should be using something
from the adjust_address family of routines.
What are the exact semantics of MEM_NOTRAP_P ? The documen
