search for: getparamattributes

I'm seeing a build failure... In file included from /Volumes/mrs5/net/llvm/llvm/lib/VMCore/ Attributes.cpp:14: /Volumes/mrs5/net/llvm/llvm/include/llvm/Attributes.h: In member function 'llvm::Attributes llvm::AttrListPtr::getParamAttributes(unsigned int) const': /Volumes/mrs5/net/llvm/llvm/include/llvm/Attributes.h:152: error: 'assert' was not declared in this scope make[1]: *** [/Volumes/mrs5/net/llvm/llvm-build/lib/VMCore/Debug/ Attributes.o] Error 1 ?

...Type *ParamTy = FT->getParamType(i); Type *ActTy = (*AI)->getType(); - if (!CastInst::isBitCastable(ActTy, ParamTy)) + if (!CastInst::isBitOrNoopPointerCastable(ActTy, ParamTy, DL)) return false; // Cannot transform this parameter value. if (AttrBuilder(CallerPAL.getParamAttributes(i + 1), i + 1). @@ -1551,7 +1551,7 @@ bool InstCombiner::transformConstExprCastCall(CallSite CS) { if ((*AI)->getType() == ParamTy) { Args.push_back(*AI); } else { - Args.push_back(Builder->CreateBitCast(*AI, ParamTy)); + Args.push_back(Builder->CreateBitOrPointe...

...at 4:30 PMPDT, Mike Stump wrote: > I'm seeing a build failure... > > In file included from /Volumes/mrs5/net/llvm/llvm/lib/VMCore/ > Attributes.cpp:14: > /Volumes/mrs5/net/llvm/llvm/include/llvm/Attributes.h: In member > function 'llvm::Attributes > llvm::AttrListPtr::getParamAttributes(unsigned int) const': > /Volumes/mrs5/net/llvm/llvm/include/llvm/Attributes.h:152: error: > 'assert' was not declared in this scope > make[1]: *** [/Volumes/mrs5/net/llvm/llvm-build/lib/VMCore/Debug/ > Attributes.o] Error 1 > > ? > __________________________________...

...on hiding. In particular, the choice to make AttributeSetNode an internal implementation detail of lib/IR is problematic. This type describes all of the attributes on an individual argument, return value, or function, which IPO transforms often want. Today the getFnAttributes, getRetAttributes, and getParamAttributes APIs find the relevant AttributeSetNode* and wrap it in a new, uniqued AttributeListImpl. This requires callers to keep around the index of the extracted attributes so they can look through the wrapper list. If we make AttributeSetNode public, we can simplify a lot of IPO transform code. Naming ==...

Philip, I post here because I think AlwaysInliner should inline it. I want to detect the indirect calls for Inliner, and I want to hear inputs. let me define indirect call first in my idea. In one single expression, one function may be subject to bitcast more than one time. we can detect this situation and treat it as a regular call of last function, is that okay? thanks, --lx On Mon, Jan 5,