search for: reame

...and assert builds of llvm. The culprit is IndVarSimplify that comes up with different behavior on the same input: in the assertion build, it does do an extra 'INDVARS: Rewriting loop exit condition' After digging around, it seems that following change is the culprit: ----- Author: Philip Reames <listmail at philipreames.com> 2019-08-01 03:16:08 Committer: Philip Reames <listmail at philipreames.com> 2019-08-01 03:16:08 Fix a release-only build warning triggered by rL367485 llvm-svn: 367499 [..] +#ifndef NDEBUG + // Used below for a consistency check only...

I'd missed the fact that j wasn't just being decremented. This isn't as easy as I said. Philip On 03/03/2016 02:36 PM, Philip Reames via llvm-dev wrote: > SCEV should be able to easily prove that j is positive here. I'm not > sure where the right place to use that information would be in this > case. Sanjoy, can you comment? > > Philip > > On 03/03/2016 02:06 PM, Haicheng Wu wrote: >> >>...

...esn't really know what's he's talking about.) On 01/08/2015 11:45 AM, Hal Finkel wrote: > ----- Original Message ----- >> From: "Arch Robison" <arch.robison at intel.com> >> To: "Hal Finkel" <hfinkel at anl.gov> >> Cc: "Philip Reames" <listmail at philipreames.com>, llvmdev at cs.uiuc.edu >> Sent: Thursday, January 8, 2015 1:26:41 PM >> Subject: RE: [LLVMdev] Floating-point range checks >> >>> Checks against 1.0 are also common. Why not just add a FP range >>> class, like our cons...

...lient code guard against such cases and make alternative arrangements to avoid an assertion or miscompile. Bardia Mahjour Compiler Optimizations IBM Toronto Software Lab From: Jimmy Zhongduo Lin <jimmy.zhongduo.lin at huawei.com> To: Bardia Mahjour <bmahjour at ca.ibm.com>, Philip Reames <listmail at philipreames.com>, "llvm-dev at lists.llvm.org" <llvm-dev at lists.llvm.org> Date: 2020/04/16 04:34 PM Subject: [EXTERNAL] RE: [llvm-dev] Scalar Evolution Expressions Involving Sibling Loops Hi Bardia, I am encountering a s...

...-dominating loops can get canceled out. Having said that it may still be a reasonable middle-ground solution. Philip, do you have any thoughts on that? Bardia Mahjour From: Jimmy Zhongduo Lin <jimmy.zhongduo.lin at huawei.com> To: Bardia Mahjour <bmahjour at ca.ibm.com> Cc: Philip Reames <listmail at philipreames.com>, "llvm-dev at lists.llvm.org" <llvm-dev at lists.llvm.org> Date: 2020/04/16 08:39 PM Subject: [EXTERNAL] RE: [llvm-dev] Scalar Evolution Expressions Involving Sibling Loops Hi Bardia, This is actually a long known pro...

...y more work for smaller gain. I like the idea of creating an FPRange class. We could start with a simple one and extend it as experience warrants. - Arch -----Original Message----- From: Hal Finkel [mailto:hfinkel at anl.gov] Sent: Thursday, January 8, 2015 1:03 PM To: Robison, Arch Cc: Philip Reames; llvmdev at cs.uiuc.edu Subject: Re: [LLVMdev] Floating-point range checks ----- Original Message ----- > From: "Arch Robison" <arch.robison at intel.com> > To: "Philip Reames" <listmail at philipreames.com>, llvmdev at cs.uiuc.edu > Sent: Thursday, Januar...

Just to be clear, you mean the release notes for 3.7 not 3.6 right? On 03/04/2015 02:15 PM, Hans Wennborg wrote: > This is great. Can you add it to the release notes? > > On Fri, Feb 27, 2015 at 3:34 PM, Philip Reames > <listmail at philipreames.com> wrote: >> The first version of this document is now live: >> http://llvm.org/docs/Frontend/PerformanceTips.html >> >> Please feel free to add to it directly. Alternatively, feel free to reply >> to this thread with text descr...

> On Jan 22, 2020, at 19:49, Philip Reames <listmail at philipreames.com> wrote: > > In short, I hit a major stumbling block. I hadn't account for the fact that some atomic stores dependent on element type (float vs int for instance) for legality. I think this qualifies as a target/infrastructure bug. It should always be...

SGTM On 02/17/2018 03:52 PM, Nuno Lopes wrote: > I can step in, if that's ok with you. > Nuno > > -----Original Message----- From: Philip Reames > Sent: Saturday, February 17, 2018 1:04 AM > To: Davide Italiano ; Nuno Lopes > Cc: llvm-dev > Subject: Re: [llvm-dev] Missing attribute inference cases > > Sure, but is anyone willing to mentor?  I don't have time.  I can > advise, but only infrequently. > > Philip...

...njdk.java.net/display/HotSpot/EscapeAnalysis http://docs.oracle.com/javase/7/docs/technotes/guides/vm/performance-enhancements-7.html http://dl.acm.org/citation.cfm?doid=320384.320386 Nuno -----Original Message----- From: Scott Egerton via llvm-dev Sent: Saturday, May 28, 2016 5:10 PM To: Philip Reames Cc: llvm-dev Subject: [llvm-dev] [GSoC 2016] Capture Tracking Improvements - BackgroundInformation Hi Phillip, I've been looking into the Capture Tracking Improvements and I was wondering if there was any research/documentation that you know of that I could use as background reading? Many...

...dev at lists.llvm.org> wrote: >> Maybe we could list some of these as a GSoC project? >> Seems like a self-contained task that can be simple as desired and as hard >> as the student wants it to be. >> >> Nuno >> >> -----Original Message----- From: Philip Reames via llvm-dev >> Sent: Friday, February 16, 2018 6:48 PM >> To: llvm-dev >> Subject: Re: [llvm-dev] Missing attribute inference cases >> >> >> >> On 02/16/2018 10:29 AM, Philip Reames via llvm-dev wrote: >> >> >> This email is just to summ...

Per my previous email, I have just signed off on Artur's original patch. Philip On 03/02/2016 11:21 AM, Philip Reames via llvm-dev wrote: > Elena, > > I'd like to propose that we move forward withArtur's original patch > <http://reviews.llvm.org/D17270> and separate the discussion of how we > might change our intrinsic naming scheme. Artur's patch is addressing > a correctn...

...e and space. My guess is that most of the cases of practical interest are eliminating domain checks and optimizations that need to know that Nan/Inf are not in play. - Arch -----Original Message----- From: Hal Finkel [mailto:hfinkel at anl.gov] Sent: Thursday, January 8, 2015 3:24 PM To: Philip Reames Cc: llvmdev at cs.uiuc.edu; Robison, Arch Subject: Re: [LLVMdev] Floating-point range checks ----- Original Message ----- > From: "Philip Reames" <listmail at philipreames.com> > To: "Hal Finkel" <hfinkel at anl.gov>, "Arch Robison" > <arch.r...

On 02/24/2014 11:27 AM, Andrew Trick wrote: > > On Feb 24, 2014, at 11:17 AM, Philip Reames <listmail at philipreames.com > <mailto:listmail at philipreames.com>> wrote: > >> >> On 02/24/2014 12:45 AM, Andrew Trick wrote: >>> >>> On Feb 21, 2014, at 10:37 AM, Philip Reames >>> <listmail at philipreames.com <mailto:listmail...

I can step in, if that's ok with you. Nuno -----Original Message----- From: Philip Reames Sent: Saturday, February 17, 2018 1:04 AM To: Davide Italiano ; Nuno Lopes Cc: llvm-dev Subject: Re: [llvm-dev] Missing attribute inference cases Sure, but is anyone willing to mentor? I don't have time. I can advise, but only infrequently. Philip On 02/16/2018 03:47 PM, Davide Italiano...

...rtainly have the 32-bit space aliasing (likely disjoint parts of) the 64-bit space, and the exact mapping of 32-to-64 might vary across OSes. --paulr From: llvm-dev [mailto:llvm-dev-bounces at lists.llvm.org] On Behalf Of Reid Kleckner via llvm-dev Sent: Wednesday, July 31, 2019 1:44 PM To: Philip Reames Cc: llvm-dev; John Reagan Subject: Re: [llvm-dev] [RFC] Changing X86 data layout for address spaces On Wed, Jul 31, 2019 at 10:29 AM Philip Reames via llvm-dev <llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org>> wrote: Looks like I made my point in an accidentally really...

> On Mar 1, 2015, at 7:53 AM, Björn Steinbrink <bsteinbr at gmail.com> wrote: > > On 2015.02.28 18:17:27 -0800, Philip Reames wrote: >>> On Feb 28, 2015, at 3:01 PM, Björn Steinbrink <bsteinbr at gmail.com> wrote: >>> 2015-02-28 23:50 GMT+01:00 Philip Reames <listmail at philipreames.com>: >>>>>> On Feb 28, 2015, at 2:30 PM, Björn Steinbrink <bsteinbr at gmail.com> wr...

...’t really like for reasons mentioned earlier in this thread, and that I don’t feel you addressed here”. Why can’t `synchscope` take a string literal? — Mehdi > > > From: Zhuravlyov, Konstantin > Sent: Wednesday, August 17, 2016 4:29:30 PM > To: Sameer Sahasrabuddhe; Philip Reames > Cc: Mehdi Amini; Liu, Yaxun (Sam); Ke Bai; Mekhanoshin, Stanislav; Sumner, Brian; llvm-dev at lists.llvm.org; Tye, Tony > Subject: RE: [llvm-dev] Memory scope proposal > > Hi, > > I have updated the review here: > https://reviews.llvm.org/D21723 <https://reviews.llvm....

...arbitrary address space for intrinsics Date: Mon, 22 Feb 2016 08:39:38 +0000 From: Elena Demikhovsky <elena.demikhovsky at intel.com> Reply-To: reviews+D17497+public+90f3d1b9468ba8ca at reviews.llvm.org To: elena.demikhovsky at intel.com, apilipenko at azulsystems.com, listmail at philipreames.com, ayal.zaks at intel.com, Matthew.Arsenault at amd.com, pjcoup at gmail.com CC: llvm-commits at lists.llvm.org delena created this revision. delena added reviewers: apilipenko, reames, Ayal, arsenm, pjcoup. delena added a subscriber: llvm-commits. delena set the repository for this revisio...

On Fri, Jul 31, 2015 at 3:53 PM, Philip Reames <listmail at philipreames.com> wrote: > > Quoting from the google doc: "If we don’t know definition of some > function, we assume that it will not call @llvm.invariant.group.barrier(). > " > This part really really bugs me. We generally try to assume minimal > kn...