search for: googlesource

Hi all, I'm trying to compile chrome using clang 8, apart from changing few switches I didn't go that far. In particular the error is due to a missing plugin: find-bad-constructs. With clang 6 I didn't have that specific problem. Can anyone help with this? Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL:

...n that project; they are already maintaining a couple of forks of BitstreamReader [1] so it would appear that the only change necessary on their side would be to also fork the interfaces. If you are aware of any other significant users, please speak up! Thanks, -- -- Peter [1] https://chromium.googlesource.com/native_client/pnacl-llvm/+/master/ include/llvm/Bitcode/NaCl/NaClBitstreamReader.h https://chromium.googlesource.com/native_client/pnacl-subzero/+/master/pnacl-llvm/include/llvm/Bitcode/NaCl/NaClBitstreamReader.h -------------- next part -------------- An HTML attachment was scrubbed... URL: &l...

> The main advantage of the clang-built Android ARM(32-bit) hammerhead kernel for my Nexus 5 has been the better battery usage when compared to that of gcc-built kernel, with the same kernel config and hardware(my Nexus 5 Android Smartphone). Details of the same can be found below. To be fair, the GCC version which comes with the android ndk has not been updated for four years, while the clang

...ple of forks of BitstreamReader [1] so it > would appear that the only change necessary on their side would be to also > fork the interfaces. > > If you are aware of any other significant users, please speak up! > > Thanks, > -- > -- > Peter > > [1] https://chromium.googlesource.com/native_client/pnacl- > llvm/+/master/include/llvm/Bitcode/NaCl/NaClBitstreamReader.h > https://chromium.googlesource.com/native_client/pnacl-subzero/+/master/ > pnacl-llvm/include/llvm/Bitcode/NaCl/NaClBitstreamReader.h > -- -- Peter -------------- next part -------------- An H...

...k from within > > a virtual machine launched by Chrome OS. > > > > Tested inside crosvm, the Chrome OS virtual machine monitor. Crosvm's > > implementation of the virtio TPM device can be found in these two source > > files: > > > > - https://chromium.googlesource.com/chromiumos/platform/crosvm/+/18ce5713e6cb99c40aafec52b67c28ba12a44f31/devices/src/virtio/tpm.rs > > - https://chromium.googlesource.com/chromiumos/platform/crosvm/+/18ce5713e6cb99c40aafec52b67c28ba12a44f31/tpm2/src/lib.rs > > These files/links do not make sense for kernel testing....

...gt; appear that the only change necessary on their side would be to also fork >> the interfaces. >> >> If you are aware of any other significant users, please speak up! >> >> Thanks, >> -- >> -- >> Peter >> >> [1] >> https://chromium.googlesource.com/native_client/pnacl-llvm/+/master/include/llvm/Bitcode/NaCl/NaClBitstreamReader.h >> https://chromium.googlesource.com/native_client/pnacl-subzero/+/master/pnacl-llvm/include/llvm/Bitcode/NaCl/NaClBitstreamReader.h > > > > > -- > -- > Peter

...e or target-side. I'd like to contribute that back to llvm ideally. What do you guys have so far? I have a prototype in golang that just spins up an instance of llvm-symbolizer currently. It isn't fully functional at the moment and it has some fuchsia specific stuff as well: https://fuchsia.googlesource.com/tools/+/master/symbolize/ but it should usable soon. The full spec we'd like to implement can be read here: https://fuchsia.googlesource.com/zircon/+/master/docs/symbolizer_markup.md > Best, > Jake > On Fri, May 4, 2018 at 2:00 PM Walter Lee via llvm-dev < llvm-dev at lists.ll...

...tl/gnu-libstdc++/4.9/libs/arm64-v8a/include \ -I ndk/sources/cxx-stl/system/include \ -L ./cuda/targets/aarch64-linux-androideabi/lib \ -lcudart -lcudart_static -ldl -lrt -pthread \ -o axpy axpy.cu clang version I am using is Android (4667116 based on r326829) clang version 7.0.1 ( https://android.googlesource.com/toolchain/clang 76e4d638afc560ad21845fad570888bef8c18045) ( https://android.googlesource.com/toolchain/llvm 67f3e6a51d93777841e0fb6d07f71fdf343df239) (based on LLVM 7.0.1svn) Target: aarch64--linux-android Thread model: posix I dont have any issues build this file for native platform (ubuntu1...

Hi, I'm now adding fingerprint format method to golang crypt library. Here is the change set for it: https://go-review.googlesource.com/#/c/32814/ I'd like to make sure why the trailing "=" is removed from the result of base64. Does anybody know? Thank you! Ryuzo Yamamoto

...ess it's either a bug with re-assembling the larger metadata header or the buffer the player is passing to the sniffer for file identification is too small. There is a 16 MB limit for metadata in the Android ogg/opus parser. Your cover images aren't that large are they? https://android.googlesource.com/platform/frameworks/av/+/a1a005fc01118685c92e723c8dcf7afeffc9d59c/media/extractors/ogg/OggExtractor.cpp#707 -r

Hello, I think we should build and release a new 3.18 kernel for the VirtSIG / Xen users.. It seems upstream 3.18.y tree has a release with the Dirty Cow security fix included, 3.18.44: https://kernel.googlesource.com/pub/scm/linux/kernel/git/sashal/linux-stable/+log/linux-3.18.y-queue (also includes a Xen SMAP/PVOPS fix). Thanks, -- Pasi

Hi, I'm still Yves. This other fix <https://chromium-review.googlesource.com/c/chromium/src/+/1061499/> never made it to opus repository. It seems safe and sane enough to be applied to opus master branch. What do you think? -- Warm regards, Yves -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.xiph.org/pipermail/opus...

...e or target-side. I'd like to contribute that back to llvm ideally. What do you guys have so far? I have a prototype in golang that just spins up an instance of llvm-symbolizer currently. It isn't fully functional at the moment and it has some fuchsia specific stuff as well: https://fuchsia.googlesource.com/tools/+/master/symbolize/ but it should usable soon. The full spec we'd like to implement can be read here: https://fuchsia.googlesource.com/zircon/+/master/docs/symbolizer_markup.md Best, Jake On Fri, May 4, 2018 at 2:00 PM Walter Lee via llvm-dev < llvm-dev at lists.llvm.org> wrot...

...the stakeholders, a standalone (eg: no sanitizer_common dependency) version of Scudo appeared to be the solution that would allow us to move forward. This meant rewriting parts of sanitizer_common that are currently used by Scudo (thus: some code duplication). An early plan was to move to our own googlesource repository (or the like), but Chandler suggested we stay in compiler-rt, as a separate directory that could be a slice of the new git monorepo. This appeared to be acceptable to everybody involved (Chandler, Kostya S., Petr, Roland, Julia), and is now the plan of record. Once the standalone version...

...> \ > -I ndk/sources/cxx-stl/system/include \ > -L ./cuda/targets/aarch64-linux-androideabi/lib \ > -lcudart -lcudart_static -ldl -lrt -pthread \ > -o axpy axpy.cu > > clang version I am using is > Android (4667116 based on r326829) clang version 7.0.1 ( > https://android.googlesource.com/toolchain/clang > 76e4d638afc560ad21845fad570888bef8c18045) ( > https://android.googlesource.com/toolchain/llvm > 67f3e6a51d93777841e0fb6d07f71fdf343df239) (based on LLVM 7.0.1svn) > Target: aarch64--linux-android > Thread model: posix > > > I dont have any issues build...

...s crashed this morning while running 4.6.6-1 and 4.9.39-29 Xen-001: This crashed shortly after being upgraded to 4.6.6-2 and 4.9.34-29 Both are on different hardware platforms, and have had a long history of being stable until these upgrades. It sounds potentially related to https://kernel.googlesource.com/pub/scm/linux/kernel/git/tiwai/sound-unstabl e/+/9ce119f318ba1a07c29149301f1544b6c4bea52a%5E%21/ but I've confirmed this patch is in the above kernels. Any suggestions / thoughts? Cheers, Nathan -------------- next part -------------- An HTML attachment was scrubbed... URL: &lt...

On Mon, Jan 16, 2017 at 12:31 PM, Sean Silva via llvm-dev <llvm-dev at lists.llvm.org> wrote: > Do we have any open projects on LLD? > > I know we usually try to avoid any big "projects" and mainly add/fix things > in response to user needs, but just wondering if somebody has any ideas. > I'm not particularly active in lld anymore, but the last big item I'd

...version downgrade, right? >>> >> > Yes, we use a separately-maintained LLVM 3.2 BticodeWriter to generate the > downgraded form. We also have 2 other BitcodeWriters based on roughly LLVM > 2.9 (but not exactly 2.9, so I would steer you away from those). > https://android.googlesource.com/platform/frameworks/compile/slang/+/refs/heads/master/BitWriter_3_2/ > is a link to the actual primary writer we use. > > >> >>> >>> Does this took work on LLVM 3.9svn? >>> >> > It currently only works up to LLVM r256229. We will most likely be...

On 31 May 2016 at 21:28, Mehdi Amini <mehdi.amini at apple.com> wrote: > Ideally, I'd prefer the cross-repository to be handled with an extra layer, in a way similar as described in: https://gerrit-review.googlesource.com/Documentation/user-submodules.htm (somehow conceptually similar to Android manifests XML files). > It would be easy to have tooling/scripts for llvm that would easily say "checkout llvm+clang+compiler-rt+libcxx+clang-extra here", or "update all llvm subproject under this root&...

...ld be the one to do the bitcode version downgrade, right? > > Yes, we use a separately-maintained LLVM 3.2 BticodeWriter to generate the downgraded form. We also have 2 other BitcodeWriters based on roughly LLVM 2.9 (but not exactly 2.9, so I would steer you away from those). https://android.googlesource.com/platform/frameworks/compile/slang/+/refs/heads/master/BitWriter_3_2/ <https://android.googlesource.com/platform/frameworks/compile/slang/+/refs/heads/master/BitWriter_3_2/> is a link to the actual primary writer we use. > > > > Does this took work on LLVM 3.9svn? > &gt...