Displaying 7 results from an estimated 7 matches for "testobj".
2009 Dec 14
4
[LLVMdev] inttoptr weirdness
...ng the appropriate byte offsets, and then
casting back to pointers).
However, I've found some oddities. While I have no problems
generating IR, when I run it through the optimizer (opt -O3), it
generates what appears to be totally wrong code.
Here's my test case:
I have a global called *testObj*. It would look like this in C:
struct TestObjClass
{
int32 dummy1, dummy2;
int32* m_array;
}
extern TestObjClass* testObj;
and I'm trying to access:
testObj->m_array[1] = 10
Theoretically, this should be a load to get the pointer to testObj
(since it's a global), I should add...
2006 Apr 17
1
slot named C
"C" appears to be an illegal name for a slot in an S4 class (example
below). If this is a known limitation, and not a bug, it would be nice
if it were caught by setClass.
Paul Gilbert
> setClass("testobj", representation ( C = "numeric"))
[1] "testobj"
> new("testobj", C= 2)
Error in methodsPackageMetaName("C", name) :
'The name of the object (e.g,. a class or generic function) to
find in the meta-data' must be a single string (got a...
2009 Dec 14
0
[LLVMdev] inttoptr weirdness
...> casting back to pointers).
>
> However, I've found some oddities. While I have no problems
> generating IR, when I run it through the optimizer (opt -O3), it
> generates what appears to be totally wrong code.
>
> Here's my test case:
>
> I have a global called *testObj*. It would look like this in C:
>
> struct TestObjClass
> {
> int32 dummy1, dummy2;
> int32* m_array;
> }
>
> extern TestObjClass* testObj;
>
> and I'm trying to access:
>
> testObj->m_array[1] = 10
>
> Theoretically, this should be a load to get...
2006 Mar 01
2
Class & Method, S3 / S4
...n like:
Creating the Class:
<CODE>-----------------------------------
setClass("connect",
representation(test="function"))
)
setMethod("test", "connect",
function(value){
value /2
}
)
</CODE>-----------------------------------
testObj = new ("connect")
testObj at test(44)
That should return 22. However, unfortunately it does not work. How can I
solve this problem. I read several instructions, but how does R work???.
Does anybody have a very simple example like above.
I highly appreciate any help.
Thanks a lot.
Nik
2009 Dec 14
2
[LLVMdev] inttoptr weirdness
On Dec 14, 2009, at 2:21 PM, Jeffrey Yasskin wrote:
>>
>> @"compile-test::*testObj*" = external constant i8* ;
>> <i8**> [#uses=1]
>>
>> define void @"compile-test::__toplevel-main"() {
>> entry:
>> store i8* null, i8** @"compile-test::*testObj*"
>
> I'm surprised this store got optimized...
2009 Dec 15
0
[LLVMdev] inttoptr weirdness
On Dec 14, 2009, at 3:50 PMPST, Chris Lattner wrote:
> On Dec 14, 2009, at 2:21 PM, Jeffrey Yasskin wrote:
>>>
>>> @"compile-test::*testObj*" = external constant i8* ;
>>> <i8**> [#uses=1]
>>>
>>> define void @"compile-test::__toplevel-main"() {
>>> entry:
>>> store i8* null, i8** @"compile-test::*testObj*"
>>
>> I'm surprised...
2012 Apr 20
44
Ceph on btrfs 3.4rc
After running ceph on XFS for some time, I decided to try btrfs again.
Performance with the current "for-linux-min" branch and big metadata
is much better. The only problem (?) I''m still seeing is a warning
that seems to occur from time to time:
[87703.784552] ------------[ cut here ]------------
[87703.789759] WARNING: at fs/btrfs/inode.c:2103