Mathieu Desnoyers wrote:That in itself is pretty significant. If that value would otherwise be constant folded or strength-reduced away, you're putting a big limitation on what the compiler can do. The mere fact that its necessary to do something to preserve many values shows how much the compiler transforms the code away from what's in the source, and specifically referencing otherwise unused intermediates inhibits that. In other words, if you weren't preventing optimisations, you wouldn't need to preserve values as much, because the optimiser wouldn't be getting rid of them. If you need to preserve lots of values, you're necessarily preventing the optimiser from doing its job. J --
| Alan Cox | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Jan Engelhardt | intel iommu (Re: -mm merge plans for 2.6.23) |
| Adrian Bunk | Re: LSM conversion to static interface |
| Greg Kroah-Hartman | [PATCH 004/196] Chinese: add translation of SubmittingPatches |
git: | |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Andrew Morton | Re: [BUG] New Kernel Bugs |
| Winkler, Tomas | RE: iwlwifi: fix build bug in "iwlwifi: fix LED stall" |
