search for: allthreads

...l. > So far, I have refrained from proposing a keyword for cross thread scope in the text format, because (a) there never was one and (b) it is not strictly needed since it is the default anyway. I am fine either way, but we will first have to decide what the new keyword should be. I find "allthreads" to be a decent counterpart for "singlethread" ... "crossthread" is not good enough since intermediate scopes have multiple threads too. This actually raises another question. In principle, the “most visible” scope ought to be something like “system” or “device”, meaning...

> On Nov 18, 2014, at 2:35 PM, Chandler Carruth <chandlerc at google.com> wrote: > > > On Fri, Nov 14, 2014 at 1:09 PM, Sahasrabuddhe, Sameer <sameer.sahasrabuddhe at amd.com <mailto:sameer.sahasrabuddhe at amd.com>> wrote: > 1. Update the synchronization scope field in atomic instructions from a > single bit to a wider field, say 32-bit unsigned integer.

...om proposing a keyword for cross > thread scope in the text format, because (a) there never was one > and (b) it is not strictly needed since it is the default anyway. > I am fine either way, but we will first have to decide what the > new keyword should be. I find "allthreads" to be a decent > counterpart for "singlethread" ... "crossthread" is not good > enough since intermediate scopes have multiple threads too. > > This actually raises another question. In principle, the “most > visible” scope ought to be somet...

I've not had a good chance to look at the patches in detail, but just to clarify one point: I don't really care whether we number things going up or down from single threaded to "every thread". I just think it makes sense to expose them in the in-memory IR interface as an enum with a particular ordering so that code can use the obvious sorts of tests for comparing two orderings

...-based scope effectively. If we can find > a reasonably clean way of doing it, it seems like the best approach at > this point: > > - It ensures we have no bitcode stability problems. > - It makes it easy to define a small number of IR-specified values > like system/crossthread/allthreads/whatever and singlethread, and > doing so isn't ever awkward due to any kind of baked-in ordering. > - In practice in the real world, every target is probably going to > just take this and map it to an enum that clearly spells out the rank > for their target, so I suspect it won&...

The vendor wanted to come in and replace an HDD in the 2nd X4500, as it was "constantly busy", and since our x4500 has always died miserably in the past when a HDD dies, they wanted to replace it before the HDD actually died. The usual was done, HDD replaced, resilvering started and ran for about 50 minutes. Then the system hung, same as always, all ZFS related commands would just