search for: tihnking

Sorry for the delays, just haven't been able to get back around to this. My silence isn't about not caring. On Fri, Jul 19, 2013 at 5:13 PM, Quentin Colombet <qcolombet at apple.com>wrote: > Like I summed up in my previous email (see below), there are two > orthogonal approaches to this problem. > I have chosen the second one (extend the reporting already used for inline

...ck when >> analyses call back into it in order to get other analyses. >> > > I would really rather avoid this, as currently the analysis manager's > logic here is very simple, and in many cases we only need the analyses to > *compute* our result, not to embed it. I'm tihnking of stuff like > Dominators is used to build LoopInfo, but there isn't a stale handle there. > > > > There is another aspect of course in that if something is preserving > LoopInfo, it really should be preserving Dominators too... > -------------- next part -------------- An...

Hi Chandler, > Le 19 juil. 2013 à 17:48, Chandler Carruth <chandlerc at google.com> a écrit : > > Sorry for the delays, just haven't been able to get back around to this. My silence isn't about not caring. > >> On Fri, Jul 19, 2013 at 5:13 PM, Quentin Colombet <qcolombet at apple.com> wrote: >> Like I summed up in my previous email (see below), there

I have just rebuilt my * box back to last weeks 06-20 CVS build beacuse after getting the latest I could not hear ANY voice prompts. I have a T1 card and a dual proc box that has been running just fine up till this weekend. I tihnk some of the format changes affected my install. Jun 27 16:12:38 DEBUG[262161]: File chan_sip.c, Line 612 (create_addr): Setting NAT on RTP to 0 Jun 27 16:12:38

With D21921 and a couple other pending patches, we now have the full LTO pipeline converted to the new PM. I was trying it out on test-suite and SPEC2006. Yay! This email is about one issue that I ran into testing the pipeline on test-suite. The issue arose in the wild as an interaction between lcssa and gvn. But the issue is extremely general. What happened is that BasicAA uses

...it in order to get other analyses. >>>> >>> >>> I would really rather avoid this, as currently the analysis manager's >>> logic here is very simple, and in many cases we only need the analyses to >>> *compute* our result, not to embed it. I'm tihnking of stuff like >>> Dominators is used to build LoopInfo, but there isn't a stale handle there. >>> >>> >>> >>> There is another aspect of course in that if something is preserving >>> LoopInfo, it really should be preserving Dominators too......

On 2/28/20 12:19 AM, Chris Lattner wrote: > Hi Nicholas, > > You might want to check out MLIR: its pass manager is already automatically and implicitly multithreaded. > > -Chris Chris, I was aware that LLVM was moving to MLIR at some point due to this. I've curious as to how MLIR deals with IPO as that's the problem I was running into. Even if you have pipelines what

...> I would really rather avoid this, as currently the analysis > > > > > manager's > > > > > logic here is very simple, and in many cases we only need the > > > > > analyses to *compute* our result, not to embed it. I'm > > > > > tihnking > > > > > of > > > > > stuff like Dominators is used to build LoopInfo, but there > > > > > isn't > > > > > a > > > > > stale handle there. > > > > > > > > > > > > > > >...

...it in order to get other analyses. >>>> >>> >>> I would really rather avoid this, as currently the analysis manager's >>> logic here is very simple, and in many cases we only need the analyses to >>> *compute* our result, not to embed it. I'm tihnking of stuff like >>> Dominators is used to build LoopInfo, but there isn't a stale handle there. >>> >>> >>> >>> There is another aspect of course in that if something is preserving >>> LoopInfo, it really should be preserving Dominators too......

Hi Am 09.01.23 um 15:15 schrieb Alex Deucher: > On Mon, Jan 9, 2023 at 9:06 AM Thomas Zimmermann <tzimmermann at suse.de> wrote: >> >> Commit 4a16dd9d18a0 ("drm/nouveau/kms: switch to drm fbdev helpers") >> converted nouveau to generic fbdev emulation. Also remove the internal >> implementation from the driver. No functional changes. > > Looking

I'm a neewbie in Linux, so please bear with me. I have a school assignment to make communication between 10 SIP softphones (kphone). So far I got trouble installing Asterisk. The information in asterisk web site seems to be a bit outdated because it's mentioned only kernel 2.4. Since Mandrake cooker (10.2beta3) witch I'm using is using kernel 2.6.10, I wander if I have a chance to

On Tue, Mar 22, 2016 at 1:41 PM, Mehdi Amini <mehdi.amini at apple.com> wrote: > Sorry I should have been more clear (writing to many email in parallel) > > You're right. I was adding a +1 to you here. > > Especially I wrote "unless there is an acknowledgement that typeless > pointers won't be there before a couple of years" with the PassManager in >

Thanks. *Phillip, *As Hal said I do not think (1) is a very large item. Please let me know if I am mistaken. *David *I think (1) is more inline with typeless pointer work than (2). Contributing to typeless pointer work will be great, but given its unknown time frame we cannot stop fixing existing problems. Of course, we should follow an approach consistent with the long-term solution. On Tue,

On 03/22/2016 02:44 PM, Ehsan Amiri wrote: > Thanks. > > *Phillip, *As Hal said I do not think (1) is a very large item. Please > let me know if I am mistaken. I have no specific reason to believe it will be a large amount of work, but prior experience tells me changes to canonical form have a tendency of exposing unexpected issues. To be clear, I am supportive of you implementing

On 03/22/2016 06:50 PM, Ehsan Amiri wrote: > > > On Tue, Mar 22, 2016 at 6:42 PM, Philip Reames > <listmail at philipreames.com <mailto:listmail at philipreames.com>> wrote: > > > > On 03/22/2016 02:44 PM, Ehsan Amiri wrote: >> Thanks. >> >> *Phillip, *As Hal said I do not think (1) is a very large item. >> Please let me

Hi, As no new suggestions came in, I would like to share my plans to move forward. — Feedbacks are very welcome! -- Like I summed up in my previous email (see below), there are two orthogonal approaches to this problem. I have chosen the second one (extend the reporting already used for inline asm). Regarding the first approach (front-end querying the back-end to build up diagnostic), it needs

I''ve put together two patches. The first introduces a new dom0_op, set_max_vcpus, which with an associated variable and a check in the VCPUOP handler fixes [1]bug 288. Also included is a new VCPUOP, VCPUOP_create, which handles all of the vcpu creation tasks and leaves initialization and unpausing to VCPUOP_initialize. The separation allows for build-time allocation of vcpus which

Hi Everyone, Numerous people have been bringing up challenges with consensus driven decision making in the LLVM community. After considering this and seeing the frustrations it is causing many people, I think we should make a formal process change to help improve decision making going forward. Here is the outline of the draft proposal

Hi, Thanks all for the insight comments. Let me sum up at a high level what proposals we actually have (sorry if I misinterpreted or missed something, do not hesitate to correct me): 1. Make LLVM defines some APIs that exposes some internal information so that a front-end can use them to build-up some diagnostics. 2. Make LLVM builds up a diagnostic and let a front-end maps this diagnostic to

On Mon, Jan 9, 2023 at 9:06 AM Thomas Zimmermann <tzimmermann at suse.de> wrote: > > Commit 4a16dd9d18a0 ("drm/nouveau/kms: switch to drm fbdev helpers") > converted nouveau to generic fbdev emulation. Also remove the internal > implementation from the driver. No functional changes. Looking at 4a16dd9d18a0, it appears to have removed this file already. I guess it