similar to: How can I submit two patches for review

Hi All, Could anyone please give your suggestions on how to generate/get Code Size of each test in LLVM TEST Suite. Thanks & Regards, Ramakota Reddy. IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person,

Hi All, I want to use Optimization Level options in tailDuplicate() API from TailDuplicator.cpp file to restrict splice() function. With -Oz option this splice() API is duplicating the RET instruction in predecessor blocks. Could anyone please give your suggestions to get OPTLevel Options(which object will carry OptLevel Options in this stage?) in this level. Thanks & Regards, Ramakota

Hi All, How to get Code size and Performance numbers ? Could any one please give your suggestions. Thanks & Regards, Ramakota. IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or

Hi All, I have made some changes in AArch64LoadStoreOptimizer.cpp file and with check-llvm all tests are passing successfully. But in llvm-test suite some tests are failing, like consumer-typeset tests are failing. Now I want to debug with 'consumer-typeset' exe from SANDBOX. But it is release build. How can I debug this issue in this case and how can I get 'consumer-typeset'

Hi All, I have commit some changes successfully and unable to push those changes using 'git push'. First time I am submitting my changes. When I tried with 'git push', giving "unable to access https://git.llvm.org/git/llvm.git/ :The requested URL returned error:403" Could any one please give your suggestion to resolve this issue. Thanks & Regards, Ramakota.

Hi Ben, (+llvm-dev since the email I'm replying to wasn't sent there) 2017-11-21 17:18 GMT+01:00 Ben Hamilton via cfe-dev <cfe-dev at lists.llvm.org> : > OK. I confirmed that Stephan's process to send out cross-repo diffs from > the monorepo is not affected by my proposal. > > I'm a bit late to the party, and I might just not have comprehended this correctly.

Forgot to mention: > Also, how would arcanist pick up two callsigns here? Wouldn't it just pick the from the closest surrounding .arcconfig? The review request will belong to a single repository, as you noticed (from the closest .arcconfig to where the arc command was invoked). However, when commits land, they will be imported under either one (rL for LLVM diffs) or two (rL + rC for e.g.

On 19 August 2016 at 18:20, Justin Bogner <mail at justinbogner.com> wrote: > The one time cost of the mono-repo proposal is drastically different > than that of the multi-repo. True. But maybe not as different as from one company / project to another. I'm assuming some people will suffer a lot more than others on either choice. > I already use git, but depending on how

+llvm-dev, so we get wider input :) Given how unfortunate reviews that are started without cc'ing the right list are (basically folks need to re-send the review from scratch), I support this idea. Ben, couldn't rL still be available for all projects? (and be the main project for LLVM). On Tue, Nov 21, 2017 at 5:18 PM Ben Hamilton via cfe-dev < cfe-dev at lists.llvm.org> wrote:

On Thu, Nov 23, 2017 at 12:58 AM Ben Hamilton <benhamilton at google.com> wrote: > Absolutely — I should have mentioned that we would keep the main rL > project and continue to use it. > Your original email said "Moving forward, only LLVM commits will be identified with the prefix rL (as in https://reviews.llvm.org/rL12345) — each project will get its own unique prefix, which

On 19 August 2016 at 19:35, Justin Bogner <mail at justinbogner.com> wrote: > I think you misunderstood what I meant here. Whether "moving to git" > will affect my workflow depends very much on "how we're moving to > git". That's exactly what I understood. :) > For example, if we do a monorepo, I may now need to lay code out > differently on my

Hello, I was wondering what was the current expected practice for committing patches to LLVM now that the Git monorepo is here. I have commit access to SVN but when I try to land my patched through GitHub I get an error saying "Permission to llvm/llvm-project.git denied". Depending on the answer, the documentation might need to be slightly clarified: the getting started documents for

On Fri, Nov 2, 2018 at 2:11 PM Justin Bogner <mail at justinbogner.com> wrote: > James Y Knight <jyknight at google.com> writes: > > Thanks for writing this up. I think it's a really important point which > > deserves discussion. > > > > Ultimately, I think it is a question as to whether to prioritize the easy > > switchover for existing out of

Thanks for writing this up. I think it's a really important point which deserves discussion. Ultimately, I think it is a question as to whether to prioritize the easy switchover for existing out of tree forks, or to prioritize having the best conversion we can make. I feel very strongly that the latter should be the priority for the official repository conversion, and that, therefore, we

x=c(5, 8, 28, 29, 30) y=c(5, 8, 28, 29, 31) How can we compare these two vectors, whether each element is exactly matched with the elements in the other vector ? How can we get the non matched elements from both the vectors? Can anyone help? ________________________________ Notice: The information contained in this electronic mail message is intended only for the use of the designated recipient.

I understand that changing the starting element to “InsertedPHIs.being() + StartingPHISize” it will be finite but given that InsrtedPHIs is finite. I have a case where one element(same element is appened to InsertedPHIs) is added to InsertedPHIs every time fixupDefs is invoked. I traced the issue why this was happening. template <class RangeType> MemoryAccess

With regards Bhargav Reddy Godala Software Engineer 2 Bangalore, India E-mail: Bhargav-reddy.Godala at amd.com<mailto:Bhargav-reddy.Godala at amd.com> Ext 30678 On 23-Sep-2017, at 9:27 PM, Daniel Berlin <dberlin at dberlin.org<mailto:dberlin at dberlin.org>> wrote: On Sat, Sep 23, 2017 at 8:38 AM, Godala, Bhargav-reddy via llvm-dev <llvm-dev at

Personally I'd like a "git llvm fetch-diff D1234" subcommand, which outputs a patch in the format of "git format-patch", which, you could then pipe to "git am", say, providing whatever prefix options you like. On Fri, Feb 8, 2019 at 2:41 PM Mehdi AMINI via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Hi, > > Are you trying to apply a revision

We should only add phis that were newly inserted, not ones that were already found. There are two cases we will hvae inserted phis: Part of the recursive call, or right in this function. The easiest way to differentiate new phis from old ones is whether they have 0 operands. I expect the attached will fix it. If not, please file a bug with reproducible IR. On Sun, Sep 24, 2017 at 11:40 PM,

Hi, I am new to speex library. I am doing project in VC++. My project details are, I have to capture voice from mic and encode it then decode and play. I am capturing the voice and storing in a buffer from there i am reading frame by frame ( 160 bytes) . These bytes i am converting to short int then calling speex_encode-int(). The output buffer i am passing to doder speex_decode_int() function.