Hi! > NAK: this is how the pthread API works. you aren't passing a value by > reference. they used a pointer rather than "long" or something as it's > harder > to fit a pointer into an integer rather than the other way around. > > if you're getting a build time warning, try casting it to uintptr_t instead
Pretty much, you would pass a pointer to thread stack as a return value with this patch which is wrong for several reasons (and the stackframe woudn't most likely there when somebody else would touch this value). The whole macro actually seems to be broken. It assigns local variable thread_exit which is defined as volatile and it looks to me like somebody had no clue how volatie works (at least at first sight). -- Cyril Hrubis [email protected] ------------------------------------------------------------------------------ Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox _______________________________________________ Ltp-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ltp-list
