I've read various things about RTS functions with respect to interruptibility, including the information on the following page:
I'm interested to know which functions can be interrupted, especially functions like memcpy and strasg. The previous link reads that strasgi can be interrupted, but the sources bundled in the C6000 Code Generation Tools installer (version 7.3.7) explicitly use the DINT and RINT instructions in that function.
Is the information on this page (still) correct?
Welcome to the TI E2E forum. I hope you will find many good answers here and in the TI.com documents and in the TI Wiki Pages. Be sure to search those for helpful information and to browse for the questions others may have asked on similar topics.
Since you are new, I will be glad to put in a request to get this thread moved to the right forum. This is the C64x Single Core DSP Forum for device questions. You will get answers to Compiler tools questions in the TI C/C++ Compiler Forum under the Development Tools group.
The RTS utilities are included as source code in your installation in the same folder as the library .lib files. You can look through there for the facts on which functions are interruptible and the exact conditions under which they are interruptible.
Search for answers, Ask a question, click Verify when complete, Help others, Learn more.
Please see http://processors.wiki.ti.com/index.php/Reentrant; it's not complete, but it's a start.
Generally speaking, if the interrupt service routine does nothing more than access its data buffer (and perhaps a flag or two) via a volatile-qualified type, it doesn't matter whether it interrupted an RTS function.
The cited article on reentrancy should not have said that malloc is usually safe to re-invoke while it is executing. You need to be sure that it has been carefully coded with that environment in mind. The problem is that it could have been in the middle of moving free-block links around so that the heap structure is temporarily in an inconsistent state, and the reentrant instance will make further changes that interfere with correct completion of the interrupted instance when it resumes. My own implementation of malloc has provisions to ensure reentrancy, but not all do.
Thanks for the answers so far.
My primary concern is not the reentrancy of functions in the RTS. I'm worried about not hitting my minimum required interrupt latency when any thread is calling functions from the RTS. The RTS is not compiled with the -miN compiler flag and it contains assembler code, so I must audit it to get any guarantees.
Please see this wiki page. -George
TI C/C++ Compiler Forum ModeratorPlease click Verify Answer on the best reply to your question.The Compiler Wiki answers most common questions.Track an issue with SDOWP. Enter your bug id in the "Find Record ID" box.
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with respect to these materials. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.