Nios® V/II Embedded Design Suite (EDS)
Support for Embedded Development Tools, Processors (SoCs and Nios® V/II processor), Embedded Development Suites (EDSs), Boot and Configuration, Operating Systems, C and C++
Announcements
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.
12748 Discussions

microC/OS-II and 'thread safe c library' option

Altera_Forum
Honored Contributor II
‎01-24-2007 02:42 PM
1,257 Views

Marking the 'thread safe c library' in ´RTOS Options´ when using microC/OS-II affects the performance.  

 

How does marking ´thread safe c library´ affect my system? 

Is there a reason for using it if DO NOT care about portability and OS independability? (as mentioned in the NiosII sw manual) 

 

/S
0 Kudos

Link Copied

1 Reply
Altera_Forum
Honored Contributor II
‎02-08-2007 10:59 AM
545 Views

This is the answer I got from Altera: 

Since "thread safe c library" will handle the synchronization of multi tasks to protect the shared resource, the performance will be lower than non thread safe c library. 

If you do not need any operation to protect the shared resource or there isn't any shared resource existed in your application, you do not need to choose thread safe c library option. 

 

My next question is: 

But if I use the mutexes or semaphores provided by microC/OS-II for protecting shared resources, then why should I use ´thread safe C library´? 

 

Anyone got a comment? 

/S
0 Kudos
Copy link
Reply

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.