the argument when calling memcpy() alone will resolve this warning.
This retains the volatile nature of the variable as well as resolves the
warnings produced
due to the above function call with volatile g_current_regs argument.
Are there any concerns with the above mentioned modifi
Hello Greg and Nathan,
Any input on the warnings generated due to the g_current_regs volatile type
qualifier?
Best Regards,
Bhindhiya Raja
SBU | Engineer
TATA ELXSI LIMITED
ITPB Road Whitefield
Bengaluru 560 048 India
www.tataelxsi.com<https://apc01.safelinks.protection.outlook.com/?
s are okay.
Regards,
Bhindhiya Raja
From: Nathan Hartman
Sent: Tuesday, September 1, 2020 6:32 PM
To: dev@nuttx.apache.org
Subject: Re: Warnings in Renesas common files
**This is an external email. Please check the sender’s
ld fails.
As the above mentioned files are common files to m16 and sh1 architectures
also, can you confirm whether the above modifications are okay.
Regards,
Bhindhiya Raja
Disclaimer: This email and any files transmitted with it are confidential and
intende
Hi
I would like to join the mailing list.
Regards
Bhindhiya Raja
Disclaimer: This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they are
addressed. If you are not the intended
