search for: rytarowski

I'm sorry, but I don't think LLDB has any release notes. On Sat, Aug 26, 2017 at 9:49 PM, Kamil Rytarowski <n54 at gmx.com> wrote: > LLDB: > > Switched the NetBSD platform to new remote tracing capable framework. > > Preliminary support for tracing NetBSD(/amd64) processes and core files > with a single thread. > > On 25.08.2017 02:44, Hans Wennborg via llvm-dev wrote: >...

Thanks! r311738. On Thu, Aug 24, 2017 at 4:51 PM, Adam Nemet <anemet at apple.com> wrote: > Hi Hans, > > Opt-viewer is now installed rather than being an internal-only tool so here it goes: > > A new tool opt-viewer.py has been added to visualize optimization remarks in HTML. The tool processes the YAML files produced by clang with the -fsave-optimization-record option. >

Hello, I was looking at sys::getDefaultTargetTriple() (file: lib/Support/Unix/Host.inc ) and there is something unclear to me. std::string sys::getDefaultTargetTriple() { StringRef TargetTripleString(LLVM_DEFAULT_TARGET_TRIPLE); std::pair<StringRef, StringRef> ArchSplit = TargetTripleString.split('-'); // Normalize the arch, since the target triple may not actually

Dear everyone, The release schedule has snuck up on me again, and it's time to wrap up the release. We won't make it to the final tag on the 21st as per the schedule, but I would like to get all outstanding blockers fixed and rc3 tagged by Friday. Hopefully this would be the last rc and we could go to final soon after. If you're involved in a release-blocking bug (see

On 19.02.2018 16:57, Hans Wennborg via lldb-dev wrote: > I would also like to get the release notes ready this week. If you've > been meaning to write something but didn't get around to it yet, now > is the time. > Notes regarding the X86(_64) backend: Preliminary support for Sanitizers and sibling features on NetBSD (ASan, UBsan, TSan, MSan, SafeStack, libFuzzer). Feel free

On 03.03.2018 13:10, David CARLIER via llvm-dev wrote: > Hi dear FreeBSD support, > > The turn of MemorySanitizer to get early support into FreeBSD. > > Kind regards. > I recommend to fix the failures in existing tests. Next enable MSan for sanitizer-common tests and fix the breaking tests on FreeBSD. How about TSan? -------------- next part -------------- A non-text

Hi dear FreeBSD support, The turn of MemorySanitizer to get early support into FreeBSD. Kind regards. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180303/253c2a4f/attachment.html>

Hello everyone, According to the release schedule, we're supposed to be tagging 'final' on Wednesday. Unfortunately, I suspect we will be a little late. There are currently 32 open release blockers: https://bugs.llvm.org/buglist.cgi?f1=blocked&o1=equals&v1=33849&query_format=advanced&resolution=--- Some of those have traction, but many don't. Some just need

...then uses libFuzzer to solve it. The next Zurich LLVM Social will [take place](https://www.meetup.com/llvm-compiler-and-code-generation-socials-zurich/events/245320826/) this Thursday 11th at 7pm. It will feature talks on timing side-channels in modern CPUs and PySpark at bare-metal speed. Kamil Rytarowski has posted an [update on NetBSD Memory Sanitizer progress](https://blog.netbsd.org/tnf/entry/the_llvm_memory_sanitizer_support). ## On the mailing lists * The [Meltdown and Spectre attacks](https://meltdownattack.com/) have of course been big news in the last week. LLVM patches to mitigate Spect...