> > BTW, I've never recommended to call pthread_setfp_np before or after
> > pthread_create() (in init_module()). I've recommended: "Try to put
> > your pthread_setfp_np call as the first statement in your RTthread."
Aha, I see. I misunderstood you. My glasses must be dirty. :)
> POSIX requires that a newly created thread start running at once, so
> creat
> set_fp
> is not good since the thread may have already executed fp operations.
> As Pavel says, the correct method is
>
> thread_code{
> set_fp /*before we do any fp ops */
> ...
> }
>
> and then in the init code
> creat_thread
>
> The alternative method, which is more POSIX-ly correct is to use
> pthread_attr_setfp
I composed an email when this thread started, to ask why fp stuff wasn't
setup as a pthread_attr_*. Then I figured there must be _some_ good
reason, and decided not to bother the busy fsmlabs crew with dumb
questions. Ha. Anyway, I feel much 'cleaner' using pthread_attr_setfp than
I did the old way.
-Chuck
-- [rtl] ---
To unsubscribe:
echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR
echo "unsubscribe rtl <Your_email>" | mail [EMAIL PROTECTED]
---
For more information on Real-Time Linux see:
http://www.rtlinux.org/rtlinux/
