search for: bool

...e seeing a bootstrap failure on x86_64-apple-darwin15 in current trunk? [ 95%] Linking CXX executable ../../bin/llvm-objdump Undefined symbols for architecture x86_64: "_xar_serialize", referenced from: DumpBitcodeSection(llvm::object::MachOObjectFile*, char const*, unsigned int, bool, bool, bool, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >) in MachODump.cpp.o "_xar_file_first", referenced from: DumpBitcodeSection(llvm::object::MachOObjectFile*, char const*, unsigned int, bool, bool, bool, std::__1::ba...

...wrote: > Kevin Enderby added those symbol uses in r270491. It has a cmake > feature test, and all the uses of those symbols appear bracketed in > HAVE_LIBXAR, so I don't know what went wrong for you. The trigger for this build failure is the usage of -DLLVM_BUILD_EXTERNAL_COMPILER_RT:BOOL=ON. If I drop that cmake option, the linkage failure for llvm-objdump disappears. > > On Tue, May 24, 2016 at 8:07 AM, Jack Howarth via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> Is anyone else seeing a bootstrap failure on x86_64-apple-darwin15 in >> current trun...

...bol uses in r270491. It has a cmake >>> feature test, and all the uses of those symbols appear bracketed in >>> HAVE_LIBXAR, so I don't know what went wrong for you. >> >> The trigger for this build failure is the usage of >> -DLLVM_BUILD_EXTERNAL_COMPILER_RT:BOOL=ON. If I drop that cmake >> option, the linkage failure for llvm-objdump disappears. > > Wrong cmake option. I meant to say that -DLLVM_LINK_LLVM_DYLIB:BOOL=ON > is the trigger of the build failure. Sorry for the noise there. Filed as https://llvm.org/bugs/show_bug.cgi?id=27855 &gt...

...6_64-apple-darwin15 in > current trunk? > > [ 95%] Linking CXX executable ../../bin/llvm-objdump > Undefined symbols for architecture x86_64: > "_xar_serialize", referenced from: > DumpBitcodeSection(llvm::object::MachOObjectFile*, char const*, > unsigned int, bool, bool, bool, std::__1::basic_string<char, > std::__1::char_traits<char>, std::__1::allocator<char> >) in > MachODump.cpp.o > "_xar_file_first", referenced from: > DumpBitcodeSection(llvm::object::MachOObjectFile*, char const*, > unsigned int, bool,...

...erby added those symbol uses in r270491. It has a cmake >> feature test, and all the uses of those symbols appear bracketed in >> HAVE_LIBXAR, so I don't know what went wrong for you. > > The trigger for this build failure is the usage of > -DLLVM_BUILD_EXTERNAL_COMPILER_RT:BOOL=ON. If I drop that cmake > option, the linkage failure for llvm-objdump disappears. Wrong cmake option. I meant to say that -DLLVM_LINK_LLVM_DYLIB:BOOL=ON is the trigger of the build failure. Sorry for the noise there. > >> >> On Tue, May 24, 2016 at 8:07 AM, Jack Howarth via ll...

...ack, >>> >>> What version of CMake are you using? >>> >>> -Chris >> >> Chris, >> I am using cmake 3.5.2. My read of this problem is as follows. >> While libLLVM.dylib is being linked against -lxar when >> -DLLVM_LINK_LLVM_DYLIB:BOOL=ON is passed to cmake, the libLLVM.dylib >> is created with -Wl,-dead_strip such that any symbols from libxar not >> explicitly used with in the object files of libLLVM.dylib are stripped >> out. This means that those additional symbols used by llvm-objdump >> aren't acc...

...include via: > > #ifdef HAVE_LIBXAR > extern "C" { > #include <xar/xar.h> > } > #endif > > I think we may need some help from Chris to track this down. I’ll bug him in a bit to see if he can help us on this. While the build here with -DLLVM_LINK_LLVM_DYLIB:BOOL=ON passed on the cmake options produces HAVE_LIBXAR:INTERNAL=1 in CMakeCache.txt, I don't see anything in the cmakefiles for tools/llvm-objdump to provide the necessary linkage on the system libxar shared library. Appending the missing linkage for -lxar onto build/stage1tools/llvm-objdump/CMake...

...24, 2016 at 2:28 PM, Chris Bieneman <beanz at apple.com> wrote: > Jack, > > What version of CMake are you using? > > -Chris Chris, I am using cmake 3.5.2. My read of this problem is as follows. While libLLVM.dylib is being linked against -lxar when -DLLVM_LINK_LLVM_DYLIB:BOOL=ON is passed to cmake, the libLLVM.dylib is created with -Wl,-dead_strip such that any symbols from libxar not explicitly used with in the object files of libLLVM.dylib are stripped out. This means that those additional symbols used by llvm-objdump aren't accessible from libLLVM.dylib's lin...

...It has a cmake >>>> feature test, and all the uses of those symbols appear bracketed in >>>> HAVE_LIBXAR, so I don't know what went wrong for you. >>> >>> The trigger for this build failure is the usage of >>> -DLLVM_BUILD_EXTERNAL_COMPILER_RT:BOOL=ON. If I drop that cmake >>> option, the linkage failure for llvm-objdump disappears. >> >> Wrong cmake option. I meant to say that -DLLVM_LINK_LLVM_DYLIB:BOOL=ON >> is the trigger of the build failure. Sorry for the noise there. > > Filed as https://llvm.org/bugs...

...llvm-dev/llvm/include/llvm/Support/CommandLine.h:292: undefined reference to `llvm::cl::opt<std::string, false, llvm::cl::parser<std::string> >::setInitialValue(std::string const&)' /home/ryjiao/Downloads/llvm-dev/llvm/tools/opt/Debug+Asserts/opt.o: In function `llvm::cl::opt<bool, false, llvm::cl::parser<bool> >::opt<char [30], llvm::cl::desc>(char const (&) [30], llvm::cl::desc const&)': /home/ryjiao/Downloads/llvm-dev/llvm/include/llvm/Support/CommandLine.h:1185: undefined reference to `llvm::cl::opt<bool, false, llvm::cl::parser<bool>...

...z at apple.com> wrote: >> Jack, >> >> What version of CMake are you using? >> >> -Chris > > Chris, > I am using cmake 3.5.2. My read of this problem is as follows. > While libLLVM.dylib is being linked against -lxar when > -DLLVM_LINK_LLVM_DYLIB:BOOL=ON is passed to cmake, the libLLVM.dylib > is created with -Wl,-dead_strip such that any symbols from libxar not > explicitly used with in the object files of libLLVM.dylib are stripped > out. This means that those additional symbols used by llvm-objdump > aren't accessible from lib...

Joe Perches (25): arm: Use bool function return values of true/false not 1/0 arm64: Use bool function return values of true/false not 1/0 hexagon: Use bool function return values of true/false not 1/0 ia64: Use bool function return values of true/false not 1/0 mips: Use bool function return values of true/false not 1/0...

Joe Perches (25): arm: Use bool function return values of true/false not 1/0 arm64: Use bool function return values of true/false not 1/0 hexagon: Use bool function return values of true/false not 1/0 ia64: Use bool function return values of true/false not 1/0 mips: Use bool function return values of true/false not 1/0...

Joe Perches (25): arm: Use bool function return values of true/false not 1/0 arm64: Use bool function return values of true/false not 1/0 hexagon: Use bool function return values of true/false not 1/0 ia64: Use bool function return values of true/false not 1/0 mips: Use bool function return values of true/false not 1/0...

...LIBXAR >> extern "C" { >> #include <xar/xar.h> >> } >> #endif >> >> I think we may need some help from Chris to track this down. I’ll bug him in a bit to see if he can help us on this. > > While the build here with -DLLVM_LINK_LLVM_DYLIB:BOOL=ON passed on > the cmake options produces HAVE_LIBXAR:INTERNAL=1 in CMakeCache.txt, I > don't see anything in the cmakefiles for tools/llvm-objdump to provide > the necessary linkage on the system libxar shared library. Appending > the missing linkage for -lxar onto > build/stage...

...e/llvm/Support/CommandLine.h:292: > undefined reference to `llvm::cl::opt<std::string, false, > llvm::cl::parser<std::string> >::setInitialValue(std::string const&)' > /home/ryjiao/Downloads/llvm-dev/llvm/tools/opt/Debug+Asserts/opt.o: In > function `llvm::cl::opt<bool, false, llvm::cl::parser<bool> >::opt<char > [30], llvm::cl::desc>(char const (&) [30], llvm::cl::desc const&)': > /home/ryjiao/Downloads/llvm-dev/llvm/include/llvm/Support/CommandLine.h:1185: > undefined reference to `llvm::cl::opt<bool, false, llvm::cl::pars...

...tLib::Real, QuantLib::Size, QuantLib::Size) const': C:\Lib\QuantLib/ql/pricingengines/mcsimulation.hpp:163:9: error: no match for 'operator!=' in 'requiredSamples != QuantL ib::Null<long long unsigned int>()' C:\Lib\QuantLib/ql/time/period.hpp:165:17: note: candidates are: bool QuantLib::operator!=(const QuantLib::Period&, cons t QuantLib::Period&) C:\Lib\QuantLib/ql/time/date.hpp:304:17: note: bool QuantLib::operator!=(const QuantLib::Date&, const Qu antLib::Date&) C:\Lib\QuantLib/ql/currency.hpp:159:17: note: bool QuantLib...

...t; diff --git a/drivers/gpu/drm/nouveau/nouveau_acpi.c b/drivers/gpu/drm/nouveau/nouveau_acpi.c > index df9f73e..e469df7 100644 > --- a/drivers/gpu/drm/nouveau/nouveau_acpi.c > +++ b/drivers/gpu/drm/nouveau/nouveau_acpi.c > @@ -46,6 +46,7 @@ static struct nouveau_dsm_priv { > bool dsm_detected; > bool optimus_detected; > bool optimus_flags_detected; > + bool optimus_skip_dsm; > acpi_handle dhandle; > acpi_handle rom_handle; > } nouveau_dsm_priv; > @@ -212,8 +213,26 @@ static const struct vga_switcheroo_handler nouve...

.... Not sure why they should be different. Thanks, Andy using System.Runtime.InteropServices; [ComVisible(true), ComImport, Guid("4F063B3A-B397-4c22-AFF4-2F8DB96D292A"), InterfaceType(ComInterfaceType.InterfaceIsIUnknown)] public interface ITheoraEncodeSettings { [PreserveSig] bool canModifySettings(); [PreserveSig] ulong targetBitrate(); [PreserveSig] ulong keyFrameDataBitrate(); [PreserveSig] byte quality(); [PreserveSig] long sharpness(); [PreserveSig] long noiseSensitivity(); [PreserveSig] ulong keyframeFreq(); [PreserveSig] bool isFixedKeyfram...

Hi, Here are two patches to fix an issue reported on kernel bugzilla (infinite loop due to unchecked function) and a more important fix to fix hanging Optimus machines when runtime PM is enabled (with pm/pci patches). An older (obsolete) patch for the first issue was tested by the reporter: https://bugzilla.kernel.org/show_bug.cgi?id=104791#c11 (it is replaced by "check for function 0x1B