Changes in directory llvm/include/llvm/Transforms/Utils:
UnifyFunctionExitNodes.h updated: 1.23 -> 1.24
---
Log message:
Fix typo in comment.
---
Diffs of the changes: (+1 -1)
UnifyFunctionExitNodes.h |2 +-
1 files changed, 1 insertion(+), 1 deletion(-)
Index: llvm/include/llvm/Tran
Changes in directory llvm/include/llvm/Transforms/Utils:
UnifyFunctionExitNodes.h updated: 1.22 -> 1.23
---
Log message:
Drop 'const'
---
Diffs of the changes: (+1 -1)
UnifyFunctionExitNodes.h |2 +-
1 files changed, 1 insertion(+), 1 deletion(-)
Index: llvm/include/llvm/Transforms/U
On May 2, 2007, at 2:58 PM, Lauro Ramos Venancio wrote:
I think you should use 'static const signed char' because 'char' is
signed on X86 and unsigned on ARM.
It does not matter. All I want is unique address of the static member
to identify Pass.
-
Devang
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.
I think you should use 'static const signed char' because 'char' is signed
on X86 and unsigned on ARM.
Lau
Changes in directory llvm/include/llvm/Transforms/Utils:
UnifyFunctionExitNodes.h updated: 1.21 -> 1.22
---
Log message:
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 identi
Changes in directory llvm/include/llvm/Transforms/Utils:
UnifyFunctionExitNodes.h updated: 1.20 -> 1.21
---
Log message:
Do not use typeinfo to identify pass in pass manager.
---
Diffs of the changes: (+3 -1)
UnifyFunctionExitNodes.h |4 +++-
1 files changed, 3 insertions(+), 1 deletio
Changes in directory llvm/include/llvm/Transforms/Utils:
UnifyFunctionExitNodes.h updated: 1.19 -> 1.20
---
Log message:
Force anything that #includes llvm/Transforms/Utils/UnifyFunctionExitNodes.h
to link in the implementation. Thanks to Anton Korobeynikov for figuring out
what was going on h
