similar to: [6.0.0 Release] TIme to wrap it up

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

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

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

Hello everyone, The release branch for 6.0.0 was created from trunk at r321711 around 3pm GMT today, and the trunk version was subsequently incremented to 7.0.0. (Hopefully the git mirror will have the branch soon too.) Note that this time we're doing an early "slow start" of the release process. I'm still on vacation and there is no release candidate scheduled until 17

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

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

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>

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. >

Hi Hans, > To get a change committed to the branch, first commit it to trunk as > usual, and then request it to be merged --- ideally by filing a > blocker bug on PR35804, or by cc'ing me on the commit email. > What about adding a project to the list of projects ported to LLVM 6.0 in `docs/ReleaseNotes.rst`? I have a project that I've just ported to LLVM 6.0 that I'd like

Hi Dan, You can commit it to ReleaseNotes.rst on the branch directly, or send me a patch or just some text and I'll do it for you. Thanks, Hans On Mon, Jan 8, 2018 at 8:31 AM, Dan Liew <dan at su-root.co.uk> wrote: > Hi Hans, > >> To get a change committed to the branch, first commit it to trunk as >> usual, and then request it to be merged --- ideally by filing a

Hello everyone, Source, docs and binaries for LLVM-6.0.0-rc2 are now available at http://prereleases.llvm.org/6.0.0/#rc2 I'll add more binaries as they become available. Please report any problems you find, ideally as bugs marked as blockers of http://llvm.org/PR35804 Thanks, Hans

Hi everyone, The source, docs and binaries for LLVM-6.0.0-rc3 are now available at http://prereleases.llvm.org/6.0.0/#rc3 More binaries will be added as they become available. Please report any problems you find as bugs marked blocking http://llvm.org/PR35804 If this looks good, the final tag will go in real soon now. Thanks, Hans

So I have Need For Speed Porsche Unleased and I have ubuntu 6.06 LTS and I have wine 0.9.90-ubuntu2 which I installed using the package manager . So I simply use wine and I get to play NFS on ubuntu simple right. I install NFS and everything goes fine. I then go to wincfg and add NFS and change it to run in 98. Error one I run the shortcut on my desktop in a terminal and I get this

On 2/7/2017 20:02, Kostya Serebryany wrote: > ... > > My understanding is that BNDCU is the cheapest possible instruction, > just like XOR or ADD, > so the overhead should be relatively small. > Still my guesstimate would be >= 5% since stores are very numerous. > And such overhead will be on top of whatever overhead SafeStack has. > Do you have any measurements to

Hi, Tests in compiler-rt run under both iOS simulators and Android devices, which requires “wrapping” the run line with the “adb” command for Android, and adding a prefix / setting some environment variables for simulators/ In case of Android this is done by changing the compilation command to produce a wrapper which already calls “adb”, and in case of iOS simulators by explicitly adding the

On 4 Nov 2014, at 00:36, Kostya Serebryany <kcc at google.com> wrote: > You at least increase the memory footprint by doubling the stack sizes. Not quite. The space overhead is constant for each stack frame - you just need to keep track of the top of two stacks, rather than one. The important overhead is that you reduce locality of reference. You will need a minimum of two cache

Hi Kostya, >On Wed, Nov 12, 2014 at 2:50 AM, Volodymyr Kuznetsov <vova.kuznetsov at epfl.ch >> wrote: > >> Dear LLVM developers, >> >> We've applied the feedback we received on Phabricator on the SafeStack >> patches, >> > >Did you investigate the possibility of moving the transformation from >codegen to the LLVM level, i.e. the same level

Hello George, I would be very much interested in a (generic) solution that would allow running tests on a remote host/device. My intended use case for this is lldb+android, and I am mostly interested in googletest-style tests. In fact, I proposed something vaguely similar to this (but limited to gtest) last year <http://lists.llvm.org/pipermail/llvm-dev/2017-May/113370.html>. However, due

Hi Pavel, I was thinking about a generic proposal for a while, but then I’ve realized that a much simpler heuristic suffices for all of my needs: - Prepend all commands which should execute on the device with %run, which runs a wrapper python script - Inside that script use a simple regexp to find all paths - sync all paths to the device - run the executable on the device - sync all paths

+nlewycky On Mon, Nov 17, 2014 at 9:36 AM, Volodymyr Kuznetsov <vova.kuznetsov at epfl.ch > wrote: > Hi Kostya, > > On Sat, Nov 15, 2014 at 1:53 PM, Volodymyr Kuznetsov < > vova.kuznetsov at epfl.ch> wrote: > > Do you think moving the pass to lib/Transform/Instrumentation but > > scheduling it during code generation would make sense ? If so, we'll >