[LLVMbugs] [Bug 11002] New: warning: missing sentinel in function call [-Wsentinel] when building r140404
bugzilla-daemon at llvm.org
bugzilla-daemon at llvm.org
Fri Sep 23 14:06:45 PDT 2011
http://llvm.org/bugs/show_bug.cgi?id=11002
Summary: warning: missing sentinel in function call
[-Wsentinel] when building r140404
Product: new-bugs
Version: trunk
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P
Component: new bugs
AssignedTo: unassignedbugs at nondot.org
ReportedBy: lbalbalba at gmail.com
CC: llvmbugs at cs.uiuc.edu
When I build ('make') trunk r140404, I get the following warnings :
llvm[2]: Compiling SwapByteOrderTest.cpp for Release+Asserts build
llvm[2]: Compiling TimeValue.cpp for Release+Asserts build
llvm[2]: Compiling TypeBuilderTest.cpp for Release+Asserts build
warning: missing sentinel in function call [-Wsentinel]
/usr/local/src/llvm/include/llvm/DerivedTypes.h:240:22: note: function has been
explicitly marked sentinel here
static StructType *get(Type *elt1, ...) END_WITH_NULL;
^
warning: missing sentinel in function call [-Wsentinel]
/usr/local/src/llvm/include/llvm/DerivedTypes.h:240:22: note: function has been
explicitly marked sentinel here
warning: missing sentinel in function call [-Wsentinel]
/usr/local/src/llvm/include/llvm/DerivedTypes.h:240:22: note: function has been
explicitly marked sentinel here
warning: missing sentinel in function call [-Wsentinel]
/usr/local/src/llvm/include/llvm/DerivedTypes.h:240:22: note: function has been
explicitly marked sentinel here
warning: missing sentinel in function call [-Wsentinel]
/usr/local/src/llvm/include/llvm/DerivedTypes.h:240:22: note: function has been
explicitly marked sentinel here
warning: missing sentinel in function call [-Wsentinel]
/usr/local/src/llvm/include/llvm/DerivedTypes.h:240:22: note: function has been
explicitly marked sentinel here
6 warnings generated.
llvm[2]: Compiling ValueHandleTest.cpp for Release+Asserts build
--
Configure bugmail: http://llvm.org/bugs/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
More information about the llvm-bugs
mailing list