search for: tellenbach

...ode with non-debug mode (in terms of instruction scheduling) and therefore *increase* scheduling potential. David ________________________________ From: vsk at apple.com <vsk at apple.com> on behalf of Vedant Kumar <vedant_kumar at apple.com> Sent: 30 September 2019 20:50 To: David Tellenbach <David.Tellenbach at arm.com> Cc: paul.robinson at sony.com <paul.robinson at sony.com>; llvm-dev at lists.llvm.org <llvm-dev at lists.llvm.org>; nd <nd at arm.com>; Tim Northover <tnorthover at apple.com>; Ahmed Bougacha <abougacha at apple.com> Subject: Re: [ll...

Hi, we at Arm have noticed that assembly can differ when compiling for AArch64 depending on whether debug information is generated or not. The issue is reproducible for the following small example compiled with `-O1` for `aarch64-arm-linux-gnu`: a() { b(a); for (;;) c("", b); } The reason for the difference is that AArch64 frame lowering emits CFI

...y paperwork and stuff. Currently we're collecting the list of summer projects here and there. It's perfectly fine to have the lists from sub-projects to be posted on their respective websites as a part of corresponding "Open Projects" pages. On Fri, Jan 24, 2020 at 2:52 PM David Tellenbach <david.tellenbach at me.com> wrote: > > Hi all, > > may I ask about the current status of this? > > The deadline for organizations to apply is February 5, 2020; has an application > already been made? > > Another thing: https://llvm.org/OpenProjects.html states that...

...ether this is acceptable. The more complete approach in your steps 2 + 3 would solve this for all targets, assuming the solution did not have to be very target-specific. This would benefit the entire community. --paulr From: llvm-dev [mailto:llvm-dev-bounces at lists.llvm.org] On Behalf Of David Tellenbach via llvm-dev Sent: Thursday, September 26, 2019 5:57 AM To: llvm-dev Cc: nd Subject: [llvm-dev] [AArch64] Generated assembly differs depending on whether debug information is generated or not Hi, we at Arm have noticed that assembly can differ when compiling for AArch64 depending on whether debug...

Dear prospective LLVM GSoC Mentors, The organization application period for GSoC 2020 will open on January, 14. This means that we're having some time to prepare the list of project ideas for the next year. When proposing the project please keep in mind the following criteria: 1. The project should serve both LLVM as a project and provide the relevant LLVM knowledge to the student. 2. 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

...ink it makes more sense to try and standardize on the existing tool rather than building our own. If that means writing three docs with steps for Win, Linux, and Mac, so be it, it will cost less to maintain than something custom written against the Phab APIs. On Mon, Jan 20, 2020 at 10:09 PM David Tellenbach via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Hi, > > although I think making the arcanist workflow more accessible is an > excellent idea I'm not entirely sure if providing a custom script is the > best solution (yet). > > A lower hanging fruit would be to hav...

I'm not sure the idea that enabling pull requests will make it easier for new contributors is fully thought out. Just because more people might be familiar with GitHub, doesn't mean it is superior. I've found the workflow on Phabricator to be really easy. I think many people agree that Phabricator is really good, I don't think we would want to get rid of Phabricator and while its

On Mon, Nov 18, 2019 at 11:32 AM David Tellenbach via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Hi all, > > +1 from my side for using "faster" or "more direct" communication channels > such > as Discord (no strong opinion on the choice of any particular tool here) > for > informal chats and di...

...moving to GitHub PRs, mainly because it is > a de-facto standard in the industry and many people are already > familiar with it. LLVM's idiosyncratic and essentially undocumented > tool is not, whatever minor advantages it might have in certain > technical respects. > > David Tellenbach wrote: > > > One thing I always liked at the Phabricator workflow is that it is > > based on diffs only. > > And other people on the thread find this an annoyance. > > Being unable to chain related reviews is about the only case where > GitHub would appear to be at a s...

On Thu, Nov 7, 2019 at 3:09 AM Roman Lebedev via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Strong -1 personally. Likewise, for many of the same reasons detailed below. ~Aaron > * What is the endgoal? To fully kill phab and move to github pullrequests? > it might be best to discuss *that* first. (did i miss an RFC?) > * Separation of attention - does everyone who

Hello everyone, *Short version:*I've set up an LLVM Discord server for real time chat (similar to IRC) and an LLVM Discourse server for forums (similar to email lists): https://discord.gg/xS7Z362 https://llvm.discourse.group/ Please join and use these new services. They are only partially set up and still very new, so don't hesitate to improve them and/or reach out to this thread with