search for: proding

Several people have been proding me to write up my thoughts on how to fix the IR type system for LLVM 3.0. Here are some (fairly stream of conscious) thoughts on the matter: http://nondot.org/sabre/LLVMNotes/TypeSystemRewrite.txt Comments welcome! -Chris

Hey Chris, On Sat, Feb 26, 2011 at 1:25 PM, Chris Lattner <clattner at apple.com> wrote: > Several people have been proding me to write up my thoughts on how to fix the IR  type system for LLVM 3.0.  Here are some (fairly stream of conscious) thoughts on the matter: > http://nondot.org/sabre/LLVMNotes/TypeSystemRewrite.txt Awesome! This is definitely long overdue... Proposal seems very reasonable to me, I think the...

On 26 February 2011 21:25, Chris Lattner <clattner at apple.com> wrote: > Several people have been proding me to write up my thoughts on how to fix the IR  type system for LLVM 3.0.  Here are some (fairly stream of conscious) thoughts on the matter: > http://nondot.org/sabre/LLVMNotes/TypeSystemRewrite.txt Hi Chris, I don't see such a bad problem with PATypeHolder, but I get what you say about...

On Sat, Feb 26, 2011 at 10:25 PM, Chris Lattner <clattner at apple.com> wrote: > Several people have been proding me to write up my thoughts on how to fix the IR  type system for LLVM 3.0.  Here are some (fairly stream of conscious) thoughts on the matter: > http://nondot.org/sabre/LLVMNotes/TypeSystemRewrite.txt > > Comments welcome! So struct types would unique by name. How important would it be fo...

I'm just passing this patch on to the list as I know Brian is busy and I had proded him to file the bug report. http://llvm.org/bugs/show_bug.cgi?id=14721 "binutils on OpenBSD is quite old, which causes the build on mips64el to fail on MipsJITInfo.cpp - it complains of illegal operands. The attachment patches it so that it will build. All the patch does is replace the register aliases

On Mon, Dec 05, 2016 at 10:19:23AM -0500, Pan Xinhui wrote: > Add two corresponding helper functions to support pv-qspinlock. > > For normal use, __spin_yield_cpu will confer current vcpu slices to the > target vcpu(say, a lock holder). If target vcpu is not specified or it > is in running state, such conferging to lpar happens or not depends. > > Because hcall itself will

On Mon, Dec 05, 2016 at 10:19:23AM -0500, Pan Xinhui wrote: > Add two corresponding helper functions to support pv-qspinlock. > > For normal use, __spin_yield_cpu will confer current vcpu slices to the > target vcpu(say, a lock holder). If target vcpu is not specified or it > is in running state, such conferging to lpar happens or not depends. > > Because hcall itself will

On 11-02-26 4:25 PM, Chris Lattner wrote: > Several people have been proding me to write up my thoughts on how to fix the IR type system for LLVM 3.0. Here are some (fairly stream of conscious) thoughts on the matter: > http://nondot.org/sabre/LLVMNotes/TypeSystemRewrite.txt Thanks! > Comments welcome! Having fewer types makes the job of the passes easier. Right...

...nts and return values Basically, I'd like to be able to construct valid programs involving named types (without a defined structure), optimize/verify them, and then provide a structure for the type later on. Andrew On 02/26/2011 04:25 PM, Chris Lattner wrote: > Several people have been proding me to write up my thoughts on how to fix the IR type system for LLVM 3.0. Here are some (fairly stream of conscious) thoughts on the matter: > http://nondot.org/sabre/LLVMNotes/TypeSystemRewrite.txt > > Comments welcome! > > -Chris > _____________________________________________...

Add two corresponding helper functions to support pv-qspinlock. For normal use, __spin_yield_cpu will confer current vcpu slices to the target vcpu(say, a lock holder). If target vcpu is not specified or it is in running state, such conferging to lpar happens or not depends. Because hcall itself will introduce latency and a little overhead. And we do NOT want to suffer any latency on some cases,

...semantics. - Jan ----- Original Message ---- > From: Chris Lattner <clattner at apple.com> > To: llvmdev Mailing List <llvmdev at cs.uiuc.edu> > Sent: Sat, February 26, 2011 4:25:32 PM > Subject: [LLVMdev] LLVM IR Type System Rewrite > > Several people have been proding me to write up my thoughts on how to fix the >IR type system for LLVM 3.0. Here are some (fairly stream of conscious) >thoughts on the matter: > http://nondot.org/sabre/LLVMNotes/TypeSystemRewrite.txt > > Comments welcome! > > -Chris > ______________________________...

All, just having spotted the backport of Linux commit 03bbcb2e I notice a certain discrepancy with the Xen commit having the same purpose as well as with the actual specification updates: The Linux solution keys off of device IDs 3403 and 3406, as listed in the specification update, but this way fails to cover the X58 chipset, which has - under different numbers (62 and 69) - the same errata

I'm using Centos-7 on my PC, with ASUS motherboard. internal audio has always worked fine EXCEPT that I can never get audio input (for recording) to work. I want to feed audio from a phono turntable and from a cassette deck. I use a phono preamp for the turntable, or directly connect the tape deck. but either nothing, or low level with horrible distortion. so, I gave up (after years of

Hi All, this is the fairlock patchset. You can apply them and build successfully. patches are based on linux-next qspinlock can avoid waiter starved issue. It has about the same speed in single-thread and it can be much faster in high contention situations especially when the spinlock is embedded within the data structure to be protected. v7 -> v8: add one patch to drop a function call

Hi All, this is the fairlock patchset. You can apply them and build successfully. patches are based on linux-next qspinlock can avoid waiter starved issue. It has about the same speed in single-thread and it can be much faster in high contention situations especially when the spinlock is embedded within the data structure to be protected. v7 -> v8: add one patch to drop a function call

Hi All, this is the fairlock patchset. You can apply them and build successfully. patches are based on linux-next qspinlock can avoid waiter starved issue. It has about the same speed in single-thread and it can be much faster in high contention situations especially when the spinlock is embedded within the data structure to be protected. v8 -> v9: mv qspinlocm config entry to

Hi All, this is the fairlock patchset. You can apply them and build successfully. patches are based on linux-next qspinlock can avoid waiter starved issue. It has about the same speed in single-thread and it can be much faster in high contention situations especially when the spinlock is embedded within the data structure to be protected. v8 -> v9: mv qspinlocm config entry to

hi, ive had some trouble trying to install RoR on tiger. during my google search i came across many different installs.. some using apache, lighttpd, or webricks for the web server,,,,,some are using sqlite, or mysql....now ive tried all and it came to a point where im sure i had multiple libraries etc...installed and everything was not working right compared to my ubuntu install of Ror. so