search for: abstact

...ing only happens when two instructions have the "same" memory > reference info. You just need to make sure that the non-temporal > flag is significant. It's not fundamentally different from the > volatile flag in this respect. Ok, this sounds right, but this look wrong: /// Abstact virtual class for operations for memory operations class MemSDNode : public SDNode { [...] bool isVolatile() const { return (SubclassData >> 5) & 1; } Shouldn't that be MMO->isVolatile()? -Dave

On Feb 11, 2010, at 12:07 PM, David Greene wrote: > On Thursday 11 February 2010 14:02:13 Dan Gohman wrote: > >>>> Putting a bit (or multiple bits) in MachineMemOperand for this >>>> would also make sense. >>> >>> Is there any chance a MachineMemOperand will be shared by multiple >>> instructions? >> >> Yes. > > Then

...ctions have the "same" memory >> reference info. You just need to make sure that the non-temporal >> flag is significant. It's not fundamentally different from the >> volatile flag in this respect. > > Ok, this sounds right, but this look wrong: > > /// Abstact virtual class for operations for memory operations > class MemSDNode : public SDNode { > [...] > bool isVolatile() const { return (SubclassData >> 5) & 1; } > > Shouldn't that be MMO->isVolatile()? It's not a bug; the code could be written either way. There...

Can Luke Tierney's recent S-new post on scoping be included in the R FAQ? I'm just going through my package and eliminating a few instances of "eval" as I hadn't realized the dangers. I noticed that one way I've used eval is for prompting, as in n <- eval(parse(prompt="Enter the number of singular values to use: ")) I presume this is not too dangerous, but

Hello, Rather new to RoR, so I''m not sure about the terminology and such :-/ . My question is: how could I know the model which is associated to a controller? For example: - controller class is TestController, which is a subclass of ApplicationController - associated model class is Test How could I write some code in a method of ApplicationController to dermine the current

While I think total compatibility is not possible or even very important I have become aware recently of some fairly low level incompatibilities that have rather serious consequences for interchange between systems. Some of these are possibly well known, but I put them on on record here just in case. (I do not expect any action on these, of course, but people may want to note them, and correct

While I think total compatibility is not possible or even very important I have become aware recently of some fairly low level incompatibilities that have rather serious consequences for interchange between systems. Some of these are possibly well known, but I put them on on record here just in case. (I do not expect any action on these, of course, but people may want to note them, and correct

...e migrations and the "active_record.schema_format = :ruby" option we don''t have to specify the model in the database, but more important: setting up and modifying the database schema can now be database agnostic, distributable and versionable. Migrations allow us a higer level of abstaction. Yet we can (IMHO) still go higher on the ladder of abstraction, closer to the mythical "Don''t Repeat Yourself" goal, and closer to the "Don''t Spread Yourself" goal i just came up with. This because at the current level of abstraction (using migrations) we...

...st of operands. Opcode may be INTRINSIC_VOID, diff --git a/include/llvm/CodeGen/SelectionDAGNodes.h b/include/llvm/CodeGen/SelectionDAGNodes.h index 072b6af..eac3eec 100644 --- a/include/llvm/CodeGen/SelectionDAGNodes.h +++ b/include/llvm/CodeGen/SelectionDAGNodes.h @@ -974,6 +974,7 @@ public: /// Abstact virtual class for operations for memory operations class MemSDNode : public SDNode { private: + // MemoryVT - VT of in-memory value. EVT MemoryVT; @@ -1013,9 +1014,11 @@ public: bool isNonTemporal() const { return (SubclassData >> 6) & 1; } bool isInvariant() const { retur...