search for: takeaway

...s around method names and local variable names are widely ignored. For example, the IRBuilder uses leading capitals for methods. Clang CodeGen does as well. Clang CodeGen also uses lots of local variables with leading lower-case letters, which is against the variable naming guidelines. I think the takeaway from that is that lots of people don't actually understand or agree with the LLVM naming standards in this area. I don't think we should do a mass rename in LLD if we aren't willing to do a mass rename across Clang internals, and so far no one has indicated a desire to do that. If we l...

...n 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 discussion was that once 3.3 is released, it would be reasonable to start using features supported by VS2010 / gcc-4.4 / clang-3.1. That would be now, are there any objections left? -- Ahmed On Sat, Jul 6, 2013 at 1:02 AM, Tim Northover <t.p.northover at gmail.com>...

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 "tidy evaluation" is far too complicated and hard to understand, and I think it confuses people,...

...the final builds. I haven’t fully dug into the extent of the differences, but I was seeing non-reproducibility in LTO builds. Whatever Ninja is doing differently causes LTO to make different optimization decisions. I have verified that this does not impact CMake’s makefile generator. The important takeaway from this is that if you are building for a purpose where non-determinism can impact your results, don’t use Ninja. For most engineering tasks building and testing locally Ninja, as always, works great. For incremental bots testing correctness, no problem. Any bots testing performance need to move...

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

...a tradeoff here between memory usage and time of execution. I am not a heavy user of the U test but I think the typical use case does not involve several hundreds of tests in a session so execution time (my 2 cents) is less important. But if R crashes one execution is already problematic. But the takeaway is probably: we should implement both approaches in the code and leave it to the user which one she prefers. If time is important and memory not an issue and if m, n are low go for the "traditional approach". Otherwise, use my formula? PS (@Aidan): I have applied for an bugzilla account...

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

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

...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 specifically but just end up affecting it; the last two will crash the stackmaps code. I think my takeaway is that at this late point in the pipeline, the stackmaps liveness code has to be the main consumer of this information, otherwise these kinds of bugs/behavior would have been noticed. So fixing them might mostly be in the interest of the stackmaps code, and I'm wondering if even if we do clas...

...head. I'm not sure how easy it would be, but it seems like there could be single-module variants of these apis that could cut down on the overhead, since it looks like MCJIT knows what modules need to be finalized but doesn't pass this information to the dyld / memory manager. My overall takeaway from these numbers is pretty good: they're good enough for where my JIT is right now, and it seems like there's some relatively-straightforward work that can be done to make them better. I'm curious what other people think. Kevin -------------- next part -------------- An HTML attachm...

...kpasswd._udp.DOMAIN.CA Then again, I'm only dealing with a single DC, so my entries are aimed strictly at clients, and this list seems to work. I might need to add these entries if I set my Samba server to use the main DNS server (dnsmasq) as well. Thanks for all the advice. I guess my big takeaway from this is that I should, in fact, make my Samba server use the main DNS server, so that everything is in-line. --Pat

...ations, so a script would definitely simplify > things for me. Unfortunately, I don't currently have the time to invest in > it myself. > > On Tue, 21 Jan 2020 at 02:16, Florian Hahn via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> 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 b...

...initely think > about providing a custom script, I just think it's not the first logical > step. > > Thanks, > David > > > On 21. Jan 2020, at 03:15, Florian Hahn via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > > > > 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...

...easy it would be, but it seems like there could be single-module variants > of these apis that could cut down on the overhead, since it looks like > MCJIT knows what modules need to be finalized but doesn't pass this > information to the dyld / memory manager. > > > My overall takeaway from these numbers is pretty good: they're good enough > for where my JIT is right now, and it seems like there's some > relatively-straightforward work that can be done to make them better. I'm > curious what other people think. > > Kevin > > _____________________...

...e whole thing in detail. > The key post in the thread, in my opinion, is at > http://lists.centos.org/pipermail/centos-devel/2014-June/010944.html I still don't see anything in that post about changing the iso name as mentioned above. Do feel free to point out specifics to me. > My takeaway is that the ISO name for 7.1406 was an aberration, and that > this is the new paradigm going forward. But I'll also reserve the right > to be wrong. My point is that there was a claim by the board that this particular change was discussed extensively on the -devel list. If it was then...

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

...econd thread goes over me being an idiot in multiple places... Thanks. I independently discovered the fedora-devel thread when I dug into Bugzilla for the setup package, limiting to bugs mentioning /etc/shells, and found this bug: https://bugzilla.redhat.com/show_bug.cgi?id=1378893 I think the takeaway is that /sbin/nologin should NOT be in /etc/shells. So that means vsftpd should NOT use the pam shells plugin to decide which accounts are system accounts in order to block them. It already has its own ftpusers file for that purpose. Is that sufficient? But how would it know when a new system a...

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

....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 specifically but just end > up affecting it; the last two will crash the stackmaps code. I think my > takeaway is that at this late point in the pipeline, the stackmaps liveness > code has to be the main consumer of this information, otherwise these kinds > of bugs/behavior would have been noticed. So fixing them might mostly be > in the interest of the stackmaps code, and I'm wondering if eve...