Revision tags: llvmorg-2.3.0 |
|
#
b0ccc8c8 |
| 22-May-2008 |
Chris Lattner <sabre@nondot.org> |
Free and vaarg are not really volatile.
llvm-svn: 51407
|
#
b76ad168 |
| 20-May-2008 |
Chris Lattner <sabre@nondot.org> |
Fix PR2346 by marking vaarg as volatile so that licm doesn't try to hoist them.
llvm-svn: 51356
|
#
d78c400b |
| 13-May-2008 |
Dan Gohman <gohman@apple.com> |
Clean up the use of static and anonymous namespaces. This turned up several things that were neither in an anonymous namespace nor static but not intended to be global.
llvm-svn: 51017
|
#
79fff7cf |
| 21-Apr-2008 |
Dan Gohman <gohman@apple.com> |
Fix the way AliasSet::print prints "may alias".
llvm-svn: 50051
|
#
2cd8e38a |
| 14-Apr-2008 |
Dan Gohman <gohman@apple.com> |
Teach AliasSetTracker about VAArgInst.
llvm-svn: 49674
|
#
80e43fa7 |
| 20-Mar-2008 |
Devang Patel <dpatel@apple.com> |
Restore isCFGOnly property of various analysis passes.
llvm-svn: 48579
|
#
718da668 |
| 19-Mar-2008 |
Devang Patel <dpatel@apple.com> |
PassInfo keep tracks whether a pass is an analysis pass or not.
llvm-svn: 48554
|
#
af75ab81 |
| 19-Mar-2008 |
Devang Patel <dpatel@apple.com> |
Do not use virtual function to identify an analysis pass.
llvm-svn: 48520
|
#
864970e9 |
| 18-Mar-2008 |
Devang Patel <dpatel@apple.com> |
Identify Analysis pass. Do not run analysis pass again if analysis info is still available. This fixes PR1441.
llvm-svn: 48476
|
Revision tags: llvmorg-2.2.0 |
|
#
f3ebc3f3 |
| 29-Dec-2007 |
Chris Lattner <sabre@nondot.org> |
Remove attribution from file headers, per discussion on llvmdev.
llvm-svn: 45418
|
#
68b6f509 |
| 01-Dec-2007 |
Duncan Sands <baldrick@free.fr> |
Integrate the readonly/readnone logic more deeply into alias analysis. This meant updating the API which now has versions of the getModRefBehavior, doesNotAccessMemory and onlyReadsMemory methods wh
Integrate the readonly/readnone logic more deeply into alias analysis. This meant updating the API which now has versions of the getModRefBehavior, doesNotAccessMemory and onlyReadsMemory methods which take a callsite parameter. These should be used unless the callsite is not known, since in general they can do a better job than the versions that take a function. Also, users should no longer call the version of getModRefBehavior that takes both a function and a callsite. To reduce the chance of misuse it is now protected.
llvm-svn: 44487
show more ...
|
#
44b8721d |
| 01-Nov-2007 |
Duncan Sands <baldrick@free.fr> |
Executive summary: getTypeSize -> getTypeStoreSize / getABITypeSize. The meaning of getTypeSize was not clear - clarifying it is important now that we have x86 long double and arbitrary precision int
Executive summary: getTypeSize -> getTypeStoreSize / getABITypeSize. The meaning of getTypeSize was not clear - clarifying it is important now that we have x86 long double and arbitrary precision integers. The issue with long double is that it requires 80 bits, and this is not a multiple of its alignment. This gives a primitive type for which getTypeSize differed from getABITypeSize. For arbitrary precision integers it is even worse: there is the minimum number of bits needed to hold the type (eg: 36 for an i36), the maximum number of bits that will be overwriten when storing the type (40 bits for i36) and the ABI size (i.e. the storage size rounded up to a multiple of the alignment; 64 bits for i36).
This patch removes getTypeSize (not really - it is still there but deprecated to allow for a gradual transition). Instead there is:
(1) getTypeSizeInBits - a number of bits that suffices to hold all values of the type. For a primitive type, this is the minimum number of bits. For an i36 this is 36 bits. For x86 long double it is 80. This corresponds to gcc's TYPE_PRECISION.
(2) getTypeStoreSizeInBits - the maximum number of bits that is written when storing the type (or read when reading it). For an i36 this is 40 bits, for an x86 long double it is 80 bits. This is the size alias analysis is interested in (getTypeStoreSize returns the number of bytes). There doesn't seem to be anything corresponding to this in gcc.
(3) getABITypeSizeInBits - this is getTypeStoreSizeInBits rounded up to a multiple of the alignment. For an i36 this is 64, for an x86 long double this is 96 or 128 depending on the OS. This is the spacing between consecutive elements when you form an array out of this type (getABITypeSize returns the number of bytes). This is TYPE_SIZE in gcc.
Since successive elements in a SequentialType (arrays, pointers and vectors) need to be aligned, the spacing between them will be given by getABITypeSize. This means that the size of an array is the length times the getABITypeSize. It also means that GEP computations need to use getABITypeSize when computing offsets. Furthermore, if an alloca allocates several elements at once then these too need to be aligned, so the size of the alloca has to be the number of elements multiplied by getABITypeSize. Logically speaking this doesn't have to be the case when allocating just one element, but it is simpler to also use getABITypeSize in this case. So alloca's and mallocs should use getABITypeSize. Finally, since gcc's only notion of size is that given by getABITypeSize, if you want to output assembler etc the same as gcc then getABITypeSize is the size you want.
Since a store will overwrite no more than getTypeStoreSize bytes, and a read will read no more than that many bytes, this is the notion of size appropriate for alias analysis calculations.
In this patch I have corrected all type size uses except some of those in ScalarReplAggregates, lib/Codegen, lib/Target (the hard cases). I will get around to auditing these too at some point, but I could do with some help.
Finally, I made one change which I think wise but others might consider pointless and suboptimal: in an unpacked struct the amount of space allocated for a field is now given by the ABI size rather than getTypeStoreSize. I did this because every other place that reserves memory for a type (eg: alloca) now uses getABITypeSize, and I didn't want to make an exception for unpacked structs, i.e. I did it to make things more uniform. This only effects structs containing long doubles and arbitrary precision integers. If someone wants to pack these types more tightly they can always use a packed struct.
llvm-svn: 43620
show more ...
|
#
c731c97f |
| 03-Oct-2007 |
Dan Gohman <gohman@apple.com> |
Use empty() member functions when that's what's being tested for instead of comparing begin() and end().
llvm-svn: 42585
|
Revision tags: llvmorg-2.1.0, llvmorg-2.0.0 |
|
#
688b2807 |
| 23-May-2007 |
Chris Lattner <sabre@nondot.org> |
when merging two alias sets together, be sure to propagate the volatility of the inner set. This fixes PR1435 and Transforms/LICM/2007-05-22-VolatileSink.ll
llvm-svn: 37305
|
#
e7da2d6a |
| 06-May-2007 |
Nick Lewycky <nicholas@mxc.ca> |
Fix typo in comment.
llvm-svn: 36873
|
#
8c78a0bf |
| 03-May-2007 |
Devang Patel <dpatel@apple.com> |
Drop 'const'
llvm-svn: 36662
|
#
e95c6ad8 |
| 02-May-2007 |
Devang Patel <dpatel@apple.com> |
Use 'static const char' instead of 'static const int'. Due to darwin gcc bug, one version of darwin linker coalesces static const int, which defauts PassID based pass identification.
llvm-svn: 36652
|
#
09f162ca |
| 01-May-2007 |
Devang Patel <dpatel@apple.com> |
Do not use typeinfo to identify pass in pass manager.
llvm-svn: 36632
|
#
f75727ab |
| 05-Feb-2007 |
Reid Spencer <rspencer@reidspencer.com> |
Make classes in anonymous namespaces use VISIBILITY_HIDDEN to help reduce LLVM's footprint and speed up linking.
llvm-svn: 33941
|
#
f3baad3e |
| 07-Dec-2006 |
Bill Wendling <isanbard@gmail.com> |
Changed llvm_ostream et all to OStream. llvm_cerr, llvm_cout, llvm_null, are now cerr, cout, and NullStream resp.
llvm-svn: 32298
|
#
597d451f |
| 28-Nov-2006 |
Bill Wendling <isanbard@gmail.com> |
Removed some of the iostream #includes. Moved towards converting to using llvm streams
llvm-svn: 31983
|
Revision tags: llvmorg-1.9.0 |
|
#
24121193 |
| 17-Sep-2006 |
Nick Lewycky <nicholas@mxc.ca> |
Explain change with a comment.
llvm-svn: 30443
|
#
c7b46536 |
| 17-Sep-2006 |
Nick Lewycky <nicholas@mxc.ca> |
Fix PR912. The input to erase() must not be a reference to the data being erased.
llvm-svn: 30442
|
#
c2d3d311 |
| 27-Aug-2006 |
Chris Lattner <sabre@nondot.org> |
eliminate RegisterOpt. It does the same thing as RegisterPass.
llvm-svn: 29925
|
#
90213c6c |
| 27-Jun-2006 |
Chris Lattner <sabre@nondot.org> |
Handle alias sets that have been unified, and thus can have other references to them. This fixes a regression in my previous checkin.
llvm-svn: 28951
|