search for: proded

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

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

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

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 regis...

...e yield_count and > + * return directly if the holder_cpu is running. > + * IOW. do NOT code like below. > + * yield_count = be32_to_cpu(lppaca_of(holder_cpu).yield_count); > + * if ((yield_count & 1) == 0) > + * return; > + * > + * a PROD hcall marks the target_cpu proded, which cause the next cede > + * or confer called on the target_cpu invalid. > + */ > + plpar_hcall_norets(H_PROD, > + get_hard_smp_processor_id(holder_cpu)); > +} > +EXPORT_SYMBOL_GPL(__spin_wake_cpu); > + > #ifndef CONFIG_QUEUED_SPINLOCKS > void __spin_yield(arch_s...

...e yield_count and > + * return directly if the holder_cpu is running. > + * IOW. do NOT code like below. > + * yield_count = be32_to_cpu(lppaca_of(holder_cpu).yield_count); > + * if ((yield_count & 1) == 0) > + * return; > + * > + * a PROD hcall marks the target_cpu proded, which cause the next cede > + * or confer called on the target_cpu invalid. > + */ > + plpar_hcall_norets(H_PROD, > + get_hard_smp_processor_id(holder_cpu)); > +} > +EXPORT_SYMBOL_GPL(__spin_wake_cpu); > + > #ifndef CONFIG_QUEUED_SPINLOCKS > void __spin_yield(arch_s...

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 now we maintain a

This looks like a good extension to the type system. One thing that I expected to work (when I first tried using opaque types) was for the optimization passes and verification to operate correctly when using opaque types, while the type could be made concrete later on - after optimization. This turned out to be impossible, and in combination with the lack of naming for opaque types, I

...we might lose a wake if we check the yield_count and + * return directly if the holder_cpu is running. + * IOW. do NOT code like below. + * yield_count = be32_to_cpu(lppaca_of(holder_cpu).yield_count); + * if ((yield_count & 1) == 0) + * return; + * + * a PROD hcall marks the target_cpu proded, which cause the next cede + * or confer called on the target_cpu invalid. + */ + plpar_hcall_norets(H_PROD, + get_hard_smp_processor_id(holder_cpu)); +} +EXPORT_SYMBOL_GPL(__spin_wake_cpu); + #ifndef CONFIG_QUEUED_SPINLOCKS void __spin_yield(arch_spinlock_t *lock) { -- 2.4.11

With the named/unnamed/anonymous distinctions there seems to be two things going on: 1. Giving an ID to a struct type. 2. Naming a type for readability. Would the new system force anonymous structs to be printed inline at every occurrence? The code might become hard to read with large anonymous types. Would it make sense to have both ID and Name? If a type has a name it could be printed using

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

...in to phono in. I can use headphones plugged into the UFO202 to listen to audio playing on the computer, but I cannot for the life of me figure out how to feed audio into the UFO202 (via its line in RCA jacks) and have it come out speakers or phones connected to the computer. I've poked and proded at alsamixer, the mate sound tool, and pavucontrol. No useful results. Pavucontrol, in its input section, does show the device listed, and it shows activity on its level mater when there is audio input via the line in jacks on the UFO202. Disconnect the line input and the activity ceases. (Mate s...

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