search for: setgr

...@SouthernOhioComputerServices.com> Subject: Re: fink rsync --daemon failure On Wednesday, Feb 19, 2003, at 08:14 US/Eastern, George D.Plymale wrote: > It would seem that OS X does indeed have a problem zeroing > the supplimental groups. Configure is only testing for the > existance of setgroups(). What does the setgroups(2) > manpage on OS X say? The call is setgroups(0, NULL). > > If you built rsync yourself you could work around the problem > by editing config.h and changing > #define HAVE_SETGROUPS 1 > to > #define HAVE_SETGROUPS 0 > and rebuilding. >...

...nse, as I can now stop trying figure out how I am introducing this error, and more importantly now will be able to go back to DwarfEHPrepare, and understand it better knowing one of its purposes. However the result of my tests indicates that the underlying register used by the exception/unwind (get/setGR(built in reg. index 1)), mechanism is shared for other uses. If this is true, what criteria is used to identify whether this register is going to be used. I can image future efforts directed toward changing or adding to the exception mechanism needing to know what to avoid before the passes that ac...

Hi Garrison, > I accidentally ran into a JIT scenario where a call instruction, executing an external non-generated C function, > executed between a llvm.eh.exception and a llvm.eh.selector instruction would clobber the register > (register index __builtin_eh_return_data_regno(1)), used by the return value of llvm.eh.selector. The behavior > of the call depends on the function

I accidentally ran into a JIT scenario where a call instruction, executing an external non-generated C function, executed between a llvm.eh.exception and a llvm.eh.selector instruction would clobber the register (register index __builtin_eh_return_data_regno(1)), used by the return value of llvm.eh.selector. The behavior of the call depends on the function called even though none of the