> But we don't actually know what it is, and it could change withI don't think it makes sense for memory. It may may make sense for registers. But given that my kernel doesn't seem to contain any instances at all it's probably not too useful for it anyways. So I wouldn't have a problem disabling it, but it would be better if they fixed their heuristics to only apply it when it makes sense. Unfortunately it's not possible as far as I know with current gccs. I didn't think you can disable only ADC/SBB. Disabling all of CMOV would be a pity though. Also I don't think there is any way to do that except selecting a CPU architecture that doesn't support it which would have other bad side effects on the code. -Andi -
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
| Ingo Molnar | [git pull] x86 arch updates for v2.6.25 |
| Anton Salikhmetov | [PATCH -v8 2/4] Update ctime and mtime for memory-mapped files |
git: | |
| Patrick McHardy | Re: [GIT]: Networking |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Gerrit Renker | [PATCH 16/37] dccp: API to query the current TX/RX CCID |
| Andrew Morton | Re: [BUG] New Kernel Bugs |
