search for: takeaways

On Wed, Oct 8, 2014 at 7:20 PM, Nick Kledzik <kledzik at apple.com> wrote: > Sure, I actually have no problem with this. > > I'm going to point out that one of the naming conventions used by LLD has > serious problems: naming variables with a leading underscore puts them > *way* too close to the reserved identifier space. Folks have accidentally > ended up with

Hi all, A few days ago, there was a report of LLVM not compiling on VS 2008, because of asymmetric std::lower_bound comparators not supported there. As noted by a few people, maybe it's time to drop VS 2008 compatibility and move the requirements to VS 2010? While there, what about going further and starting using C++11? Now seems as good a time as ever; my takeaway from that few months old

No, there are lots of situations where that doesn't make sense. You don't want to have to define local copies of the functions from every package you use, for example. I think the takeaway is to learn how R scoping works, and keep things simple. That's one reason I tend to avoid "tidyverse" packages. There are a lot of really good ideas in those packages, but

It is with great sadness that I must tell everyone CMake’s Ninja generator is non-deterministic (https://public.kitware.com/Bug/view.php?id=15968 <https://public.kitware.com/Bug/view.php?id=15968>). I’m not sure if this impacts all versions of CMake, but it certainly impacts all the recent releases. You might ask why this matters? Sadly the non-determinism *does* impact determinism in the

Hi, One takeaway for me from the recent Phabricator vs Github PR discussions was that arc (arcanist) can be a pain to set up and may pose a hurdle for some contributors. I think those points could be addressed relatively easily by adding a llvm-patch script (or an even better name) that allows users to create and apply patches from reviews.llvm.org using Phabricators API. In my experience, the

> > > Performance statistics are interesting. If we assume the two populations > have a total of `m` members, then this implementation runs slightly slower > for m < 20, and much slower for 50 < m < 100. However, this implementation > works significantly *faster* for m > 200. The breakpoint is precisely when > each population has a size of 50; `qwilcox(0.5,50,50)`

Dear Duncan, THanks for the reply...! So the takeaway is that define the symbol in the same environment before using it right!? Thanking you, Yours sincerely, AKSHAY M KULKARNI ________________________________ From: Duncan Murdoch <murdoch.duncan at gmail.com> Sent: Tuesday, April 4, 2023 8:21 PM To: akshay kulkarni <akshay_e4 at hotmail.com>; Deepayan Sarkar

...kers who are excited about LLVM and helping grow the community through these educational talks! You do not need to be a long time developer to submit a proposal. General Guidelines: - It should be clear from your abstract what your topic is, who your target audience is, and what are the takeaways for attendees. The program committee does not have time to read 10 page papers for each submission. - Talks about the use of an LLVM technology should include details about how LLVM is used and not only be about the resulting application. - Tutorials on “how to use X” in LLVM (o...

Hi all, I've run into a couple bugs recently that affected stackmap liveness analysis in various ways: http://llvm.org/bugs/show_bug.cgi?id=19224 - function arguments stay live unnecessarily http://llvm.org/bugs/show_bug.cgi?id=21265 - eflags can end up as a live out http://llvm.org/bugs/show_bug.cgi?id=21266 - %rip can end up as a live out The first two have nothing to do with stackmaps

So I finally took the plunge and switched to MCJIT (wasn't too bad, as long as you remember to call InitializeNativeTargetDisassembler if you want disassembly...), and I got the functionality to a point I was happy with so I wanted to test perf of the system. I created a simple benchmark and I'd thought I'd share the results, both because I know I personally had no idea what the

On 2017-10-13 06:09 PM, Jon Gerdes via samba wrote: > There's no such thing as "best practice" - there's good and bad > practice and I hope that here (Samba ML) you will get some good advice, > in return for a good question. Thanks for this very thoughtful reply. > The environment you describe, to me, implies that it would be best if > you simply "fit

I'd rather we decided on whether to accept GitHub PRs or not first (in the other thread). I would bet that everyone who has troubles with arc / is not allowed to use arc would happily use GitHub PRs instead. Worst case scenario if the community decides that we don't want to accept GitHub PRs then this sort of script would be a useful time sink. Cheers, -Neil. On Tue, Jan 21, 2020 at

+1 to this. I will not deny that, for whatever reason, people don't seem to use Arcanist. Using PHP as the scripting language seems to be a major sticking point for people, since it is not typically preinstalled or required for normal LLVM development, in the way that Python is. I've done it, and it works for me. I think it makes more sense to try and standardize on the existing tool

The pass manager is re-created in emitObject on every call. Andy, is that needed or can we create the PM in MCJIT constructor and keep it around? Yaron 2013/11/19 Kevin Modzelewski <kmod at dropbox.com> > So I finally took the plunge and switched to MCJIT (wasn't too bad, as > long as you remember to call InitializeNativeTargetDisassembler if you want > disassembly...),

On 04/02/2015 03:29 AM, Lamar Owen wrote: > On 03/31/2015 11:11 PM, Peter wrote: >> Can you please point me to the centos-devel thread that discussed >> changing the iso naming convention from CentOS-7.1-1503-x86_64-DVD.iso >> to CentOS-7-x86_64-DVD-1503.iso? I must have missed it because I saw >> no mention of this change until today. > The first thread along these

Hello Experts, When we can expect Security Update for Bind Vulnerability on Centos 6.8/7.2? ISC BIND Lightweight Resolver Protocol Req Processing Dos Vulnerability: CVE-2016-2775 -- With Thanks & Regards: Sidharth Sharma

--On Thursday, January 10, 2019 4:17 PM -0500 Stephen John Smoogen <smooge at gmail.com> wrote: > So I think this is a side effect of a long term argument of the security > nature of /sbin/nologin > > https://serverfault.com/questions/328395/nologin-in-etc-shells-is-dangero > us-why > https://lists.fedoraproject.org/archives/list/devel at lists.fedoraproject.o >

Hello List! I have ordered an 80 GB iPod yesterday and I want my complete music library on it "for takeaway". Currently my library consists of mp3, ogg, and flac files. Has someone alread made a script to duplicate a music library consisting of various formats in mp3 ? I would appreciate if the directory hierarchy would we preserved... Thanks, Lars

...Visa letters will also be a separate application. Registration: https://goo.gl/forms/pry9xjnXz434urOo2 Call for Proposals: Your submission should be a proposal for a 25 minute talk, a 5 minute lightning talk, or a collaborative birds of a feather conversation. Submitters should consider audience takeaways as well as how this proposal will move the Gluster project forward. We'll be accepting proposals until July 31st. Accepted proposals will be notified the week of July 31st. https://goo.gl/forms/1oM0nJgp1h0Zs3Z92 -- Amye Scavarda | amye at redhat.com | Gluster Community Lead

I think what's happening is BranchFolder::MaintainLiveIns is using a forward analysis on top of these missing kill flags, and updating the BB-live-ins/live-outs with an incorrect set of registers. Then when the stackmaps liveness analysis happens, it's not doing anything wrong, but it starts with the wrong set of live registers and will propagate those to the point of the