Andreas Ericsson wrote:You can write "C" in D, and you'll get exactly the same (performance) results. After all, D and C share the same optimizer and code generator (for both implementations of D), and when the same intermediate code is presented, you'll get the same results. That's why when people benchmark D against C, they deliberately do NOT write the D version in a C'ish manner, but refactor the code into what would be a more D'ish style. There's no way to write assembler in C. I humbly suggest running a profiler over ld before spending time fixing the wrong thing <g>. I haven't looked at the ld source, but being experienced in similar projects I'd hazard a guess that there won't be a quick fix to ld's speed problems. - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
| david | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Rob Landley | What still uses the block layer? |
git: | |
| Antonio Almeida | HTB accuracy for high speed |
| Alexey Dobriyan | Re: [GIT]: Networking |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
