Displaying 5 results from an estimated 5 matches for "intentionnally".
Did you mean:
intentionally
2010 Jun 17
0
[LLVMdev] Strange pointer aliasing behaviour
...do bit-casting in C the usual way is to very
carefully use an union which informs the compiler that there will be
aliasing...
> Those programs are buggy and should be fixed.
Totally agree. Making such ugly things work means lots of optimizations
can't be performed.
I wonder if llvm intentionnally generates this spurious alias (to make
badly written code work) or is it just the optimizer not being smart
enough yet ?...
2010 Jun 17
2
[LLVMdev] Strange pointer aliasing behaviour
On Jun 17, 2010, at 12:22 AM, Eli Friedman wrote:
> On Wed, Jun 16, 2010 at 11:14 PM, Pierre C <lists at peufeu.com> wrote:
>>> There are essentially two ways to "solve" this issue: one is
>>> type-based alias analysis, i.e. assuming "double" and "int" don't
>>> alias; LLVM doesn't implement this at the moment. The other
2010 Jun 17
2
[LLVMdev] Strange pointer aliasing behaviour
...friendly as we can in helping people find and fix these issues. Tracking down a bug like that in user code is an absolute nightmare. Specifically, we should issue good diagnostics for problems of this sort, from the compiler and/or from the static analyzer, whenever possible.
> I wonder if llvm intentionnally generates this spurious alias (to make badly written code work) or is it just the optimizer not being smart enough yet ?...
I'm not 100% sure, but I suspect it's the latter.
-Jim
2005 Jun 14
4
Missing files on Windows client side.
In a directory with approximately 6000 files, several files are missing on
the Windows side.
If I check the directory on Unix (AIX) they are all there.
As far as I can see there's nothing strange with this files en I can't see
any connection between the missing files.
It looks like it's randomly.
A few examples of missing files:
FAKTREF.10062005.16 (See debug information)
2005 Jun 28
1
Fw: Missing files on Windows client side
Jeremy,
I think we found the part of source where the problem resides:
smbd/trans2.c
+1444 for (i=0;(i<maxentries) && !finished && !out_of_space;i++)
{
+1445 BOOL got_exact_match = False;
+1446
+1447 /* this is a heuristic to avoid seeking the dirptr
except when
+1448 absolutely necessary. It allows for