search for: mgrang

Displaying 9 results from an estimated 9 matches for "mgrang".

Did you mean: grang
2015 Feb 04
2
[LLVMdev] Question on Machine Combiner Pass
Ping From: Mandeep Singh Grang [mailto:mgrang at codeaurora.org] Sent: Tuesday, February 03, 2015 4:34 PM To: 'llvmdev at cs.uiuc.edu' Cc: 'ghoflehner at apple.com'; 'apazos at codeaurora.org'; mgrang at codeaurora.org Subject: Question on Machine Combiner Pass Hi, In the file lib/CodeGen/MachineCombiner.cpp I...
2016 Feb 24
1
Performance degradation on ARMv7 (cortex-a9)
...tex-a9 directly? (In which case all CPUs that used to inherit > ProcA9 now need to inherit all of the features ProcA9 used to inherit > as well as ProcA9, which is what I did in the change you mention). > > Regards, > > Bradley Smith > > *From:*Grang, Mandeep Singh [mailto:mgrang at codeaurora.org] > *Sent:* 24 February 2016 03:16 > *To:* Bradley Smith > *Cc:* llvm-dev at lists.llvm.org > *Subject:* Performance degradation on ARMv7 (cortex-a9) > > Hi Bradley, > > I was doing some performance analysis for ARMv7 (cortex-a9) and I > noticed that on...
2016 Feb 24
2
Performance degradation on ARMv7 (cortex-a9)
Hi Bradley, I was doing some performance analysis for ARMv7 (cortex-a9) and I noticed that one of my benchmarks degraded by 93%. I have tracked the regression down to the following commit by you: / //commit 7c1b77248baaeafec5d6433c3d1da9a2e2b69595// //Author: Bradley Smith <bradley.smith at arm.com>// //Date: Mon Nov 16 11:10:19 2015 +0000// // [ARM] Introduce subtarget features per
2017 Jul 17
2
moving libfuzzer to compiler-rt?
...<mailto:hans at hanshq.net> > juergen at ributzka.de <mailto:juergen at ributzka.de> > lenny at colorado.edu <mailto:lenny at colorado.edu> > mail at justinbogner.com <mailto:mail at justinbogner.com> > matze at braunis.de <mailto:matze at braunis.de> > mgrang at codeaurora.org <mailto:mgrang at codeaurora.org> > nicholas at mxc.ca <mailto:nicholas at mxc.ca> > peter at pcc.me.uk <mailto:peter at pcc.me.uk> > rafael.espindola at gmail.com <mailto:rafael.espindola at gmail.com> > richard-llvm at metafoo.co.uk <mailto...
2017 Jul 12
3
moving libfuzzer to compiler-rt?
...n at aaronballman.com > ahmed.bougacha at gmail.com > chandlerc at gmail.com > craig.topper at gmail.com > dan at su-root.co.uk > eric at efcs.ca > hans at hanshq.net > juergen at ributzka.de > lenny at colorado.edu > mail at justinbogner.com > matze at braunis.de > mgrang at codeaurora.org > nicholas at mxc.ca > peter at pcc.me.uk > rafael.espindola at gmail.com > richard-llvm at metafoo.co.uk > sanjoy at playingwithpointers.com > tzuhsiang.chien at gmail.com > vonosmas at gmail.com > yaron.keren at gmail.com > > Would you know the form...
2017 Jul 12
3
moving libfuzzer to compiler-rt?
On Wed, Jul 12, 2017 at 11:54 AM, George Karpenkov <ekarpenkov at apple.com> wrote: > > On Jul 12, 2017, at 11:34 AM, Kostya Serebryany <kcc at google.com> wrote: > > > > On Wed, Jul 12, 2017 at 11:30 AM, George Karpenkov <ekarpenkov at apple.com> > wrote: > >> >> On Jul 12, 2017, at 11:01 AM, Kostya Serebryany <kcc at google.com> wrote:
2017 Aug 31
2
[cfe-dev] Uncovering non-determinism in LLVM - An Update
On 30 August 2017 at 18:51, David Blaikie via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > > On Tue, Aug 29, 2017 at 11:45 AM Grang, Mandeep Singh via cfe-dev > <cfe-dev at lists.llvm.org> wrote: >> >> Hi All, >> >> I wanted to share a couple of updates on the effort to uncover >> non-determinism in LLVM through reverse iteration. >>
2017 Aug 28
5
[5.0.0 Release] Please write release notes
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
2018 Aug 09
3
Writing static analyzers to detect non-deterministic behavior?
Thanks for your response David. 1) I'm not sure it's do-able. I don't know of any nice way to track whether an ordered walk of an unordered container leaks out into the final output of the program. Only iterating over an unordered container is probably not a sufficient hint (it'd have a high false positive rate to warn on every instance of that) - and I don't have any