Displaying 7 results from an estimated 7 matches for "thisismynam".
Did you mean:
thisismyname
2007 Nov 15
2
[LLVMdev] BasicAliasAnalysis and out-of-bound GEP indices
Sadly, this will break a very common idiom. In GCC, we discovered it
to be common enough that it broke a *bunch* of C code.
In particular, you will break
struct foo {
int a;
char name[0];
}
bar = malloc(sizeof (struct foo) + strlen("thisismyname") + 1);
strcpy(bar->name, "thisismyname");
It only started turning up when we started doing higher level loop
opts and used alias info in dependence testing. It would end up
reversing or interchanging loops around these things which while
legal, broke enough software that we g...
2007 Nov 15
0
[LLVMdev] BasicAliasAnalysis and out-of-bound GEP indices
...,
> Sadly, this will break a very common idiom. In GCC, we discovered it
> to be common enough that it broke a *bunch* of C code.
>
> In particular, you will break
>
> struct foo {
> int a;
> char name[0];
> }
>
> bar = malloc(sizeof (struct foo) + strlen("thisismyname") + 1);
> strcpy(bar->name, "thisismyname");
>
>
> It only started turning up when we started doing higher level loop
> opts and used alias info in dependence testing. It would end up
> reversing or interchanging loops around these things which while
> leg...
2009 Jun 11
0
S4 Package with definition of method 'names'
...ss?
The following works if directly pasted into R:
(a simple test class with 1 attribute that is returned by invoking 'names')
#class definition
setClass("test", representation = representation(name = "character"),
prototype = prototype(name = "thisIsMyName"))
#definition of names for class test
setMethod("names", "test", function(x)
{
x at name
}
)
#definition of names<- for class test
setReplaceMethod("names", "test", function(x, value)
{
x at name <- value
x
}
)
test = new...
2007 Nov 15
3
[LLVMdev] BasicAliasAnalysis and out-of-bound GEP indices
...iom. In GCC, we discovered it
> > to be common enough that it broke a *bunch* of C code.
> >
> > In particular, you will break
> >
> > struct foo {
> > int a;
> > char name[0];
> > }
> >
> > bar = malloc(sizeof (struct foo) + strlen("thisismyname") + 1);
> > strcpy(bar->name, "thisismyname");
> >
> >
> > It only started turning up when we started doing higher level loop
> > opts and used alias info in dependence testing. It would end up
> > reversing or interchanging loops around these...
2007 Nov 13
0
[LLVMdev] BasicAliasAnalysis and out-of-bound GEP indices
It's an optimization opportunity!
When behavior is undefined, we're free to interpret it to be "whatever
makes optimization easiest." If the two do actually happen to alias,
well, it's the programmer's fault anyways, because they were doing
something undefined!
--Owen
On Nov 13, 2007, at 4:13 PM, Wojciech Matyjewicz wrote:
> Hi!
>
> While investigating
2007 Nov 13
2
[LLVMdev] BasicAliasAnalysis and out-of-bound GEP indices
Hi!
While investigating into the PR1782 I spent some time analyzing
BasicAliasAnalysis.cpp. While the mentioned problem should be fixed now
(I hope), I have discovered some other possibilities for a bug to occur.
In the case of checking for aliasing of two pointer values, where at
least one of them is a GEP instruction with out-of-bound indices,
BasicAliasAnalysis can return NoAlias, even if the
2012 Mar 05
1
Twitter like route
Hi,
I have this route that let me build custom url for users like
/thisismyname, and it works fine. But when I look at the log there is
something I don''t like...
When I hit /gregory this is what is happenning:
1. Going to public_profile#public # Good
2. hitting /assets and trying to find a user with asset token # Not good
I thought my constraints would avoid this b...