search for: vociferous

...ng for GC pointers. On Feb 27, 2009, at 06:38, Mark Shannon wrote: > If I want to use the llvm.gcwrite intrinsic for my write barrier > then I need to write a GC and then implement for each and *every* > backend the gcwrite intrinsic for my write barrier. I'm not sure where such vociferous concern on this subject arises. All the extant collector plugins I'm aware of operate in conjunction with the target-independent framework and require exactly zero code within each target backend. — Gordon

Hi, I realise this might be a bit controversial ;) Suppose I am writing a VM (such as VMKit), or a VM toolkit, and I want to add a generational GC. If I want to use the llvm.gcwrite intrinsic for my write barrier then I need to write a GC and then implement for each and *every* backend the gcwrite intrinsic for my write barrier. Now, if I don't use the intrinsic, I need to write my write

...for using GC intrinsics with a copying collector. This, again, > requires that the code generator perform bookkeeping for GC pointers. Elimination of the reload penalty is impossible, unless the GC can be informed about traceable objects in registers. > > I'm not sure where such vociferous concern on this subject arises. All > the extant collector plugins I'm aware of operate in conjunction with > the target-independent framework and require exactly zero code within > each target backend. No collector plugins actually use gcread/gcwrite, since there are no gener...

...st the difference via LRT (or F test). stepAIC in the MASS package will do stepwise selection via AIC. This opens the larger can of worms of why you're doing stepwise model selection in the first place ... I was surprised to see fastbw() in the rms package, since Frank Harrell is normally a vociferous opponent of stepwise approaches, but I assume (my copy of his book is not handy) that there is some context within which it makes statistical sense. > > My challenge is further complicated because I had hoped to use fastbw() > to generate a parsimonious model, but clearly fastbw also...

...g >> collector. This, again, requires that the code generator perform >> bookkeeping for GC pointers. > > Elimination of the reload penalty is impossible, unless the GC can > be informed about traceable objects in registers. Exactly. >> I'm not sure where such vociferous concern on this subject arises. >> All the extant collector plugins I'm aware of operate in >> conjunction with the target-independent framework and require >> exactly zero code within each target backend. > > No collector plugins actually use gcread/gcwrite, since...

...this. I've stated what numerous actual employment and IP lawyers who practice in germany have told me (multiple times, now, and in the past). You want to argue that it's wrong. Fine. I honestly don't care. But you should not expect me to take your opinion over theirs, even if you argue vociferously, because they are the folks who have tried to do these things in practice. I don't even have the same lawyers as the foundation, etc, and i'm sure they've vetted these issue as well. So i'm going to say: believe what you like. But i don't think it's reasonable to expec...

hey guys I thought I was making progress on my dialplan when I realized that the class features that are available for zap channels aren't available for SIP channels. I see references in the archives to adding pattern matches in the dialplan for CLASS features which has raised a couple questions. 1. Is implementing CLASS like features via the dialplan the currently recommended way to do

Mark Shannon wrote: > Jon Harrop wrote: >> On Thursday 26 February 2009 17:25:56 Chris Lattner wrote: >>> In my ideal world, this would be: >>> >>> 1. Subsystems [with clean interfaces] for thread management, >>> finalization, object model interactions, etc. >>> 2. Within different high-level designs (e.g. copying, mark/sweep, etc) >>>

On Wed, Jul 29, 2015 at 2:15 PM, Warren Young <wyml at etr-usa.com> wrote: > Just because one particular method of prophylaxis fails to protect against all threats doesn?t mean we should stop using it, or increase its strength. Actually it does.There is no more obvious head butting than with strong passwords vs usability. Strong login passwords and usability are diametrically opposed.

On Thu, Oct 22, 2015 at 9:54 PM, Joerg Sonnenberger via llvm-dev < llvm-dev at lists.llvm.org> wrote: > On Wed, Oct 21, 2015 at 09:10:40AM -0700, Daniel Berlin wrote: > > Let's start with: In just about every country in the world, anyone > > contributing on behalf of their company are exercising their employers > > copyright (in most cases, even if they do it in

...enexperiment instead: what if RHEL 7 shipped based on launchd instead of systemd, with no differences relative to the version shipped in the contemporaneous version of Mac OS X? I?m uncertain as to whether the opposition would have been as great, but I?m dead certain the opposition would have been vociferous and strident, because Linux, though less conservative than the BSDs, is much more conservative than macOS. The systemd vs launchd vs sysvinit vs whatever-else arguments are more about human factors than about technology, even though they?re usually couched as technical battles. > When people g...

...kind of thing that will happen if people don't get behind the values of freedom and openness that we are espousing. Please let Genentech know that you find what they are doing offensive. Publicize the mechanism so that new compounds can be obtained as replacements. For the future, continued vociferous public activism is required to prevent such outrages from occurring in the future. It becomes clear that the compounds which come from common roots, fruits, and vegetables are a shared human heritage and the free and open source of the future. Tannins are another interesting case in point, becaus...

...of thing that will happen if people don''t get behind the values of freedom and openness that we are espousing. Please let Genentech know that you find what they are doing offensive. Publicize the mechanism so that new compounds can be obtained as replacements. For the future, continued vociferous public activism is required to prevent such outrages from occurring in the future. It becomes clear that the compounds which come from common roots, fruits, and vegetables are a shared human heritage and the free and open source of the future. Tannins are another interesting case in point, becaus...

...of thing that will happen if people don''t get behind the values of freedom and openness that we are espousing. Please let Genentech know that you find what they are doing offensive. Publicize the mechanism so that new compounds can be obtained as replacements. For the future, continued vociferous public activism is required to prevent such outrages from occurring in the future. It becomes clear that the compounds which come from common roots, fruits, and vegetables are a shared human heritage and the free and open source of the future. Tannins are another interesting case in point, becaus...

...nt instead: what if RHEL 7 shipped based on launchd instead of systemd, with no differences relative to the version shipped in the contemporaneous version of Mac OS X? > > I?m uncertain as to whether the opposition would have been as great, but I?m dead certain the opposition would have been vociferous and strident, because Linux, though less conservative than the BSDs, is much more conservative than macOS. > > The systemd vs launchd vs sysvinit vs whatever-else arguments are more about human factors than about technology, even though they?re usually couched as technical battles. > &gt...

...kind of thing that will happen if people don't get behind the values of freedom and openness that we are espousing. Please let Genentech know that you find what they are doing offensive. Publicize the mechanism so that new compounds can be obtained as replacements. For the future, continued vociferous public activism is required to prevent such outrages from occurring in the future. It becomes clear that the compounds which come from common roots, fruits, and vegetables are a shared human heritage and the free and open source of the future. Tannins are another interesting case in point, becaus...

...in other ways. And Apple and Microsoft have been working to kill login passwords for a while. Google and Facebook too. No one likes them. And our trust in them is diminishing. They are not long term tenable. Making longer ones compulsory already causes companies who do so grief as people complain vociferously about such policies. > I have no strong feelings on the new libpwquality rules, exactly. What I do feel strongly about is that there should be *some* reasonable minima that can?t easily be bypassed. This idea that opt in is not sufficient demonstrates how archaic and busted computer securi...

On Oct 17, 2018, at 10:03 AM, Mark Rousell <mark.rousell at signal100.com> wrote: > > launchd is not being forced on them as systemd is in practice Try doing without launchd on macOS. If you think that?s irrelevant, count the number of MacBooks at the next FreeBSD conference you attend. For an init system to gain sufficient momentum, it must be the default, with no easy way to

Hello, I believe that ZFS and it''s concepts is truly revolutionary to the point that I no longer see any OS as modern if it does not have comparable storage functionality. Therefore I think that file system/disk manager with similar qualities should be written for Linux. Does Sun have plans to dual license ZFS as GPL so it can be ported to native Linux? If not, is it legal to write

Not sure if it''s been posted yet, my email is currently down... http://weblog.infoworld.com/yager/archives/2007/10/suns_zfs_is_clo.html Interesting piece. This is the second post from Yager that shows solaris in a pretty good light. I particularly like his closing comment: "If you haven''t checked out ZFS yet, do, because it will eventually become ubiquitously implemented