This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
| Other format: | [Raw text] | |
Hi Vladimir, thanks for doing this.
The above said about compilation speed is true when GCC front-end is used for LLVM.
It's not clear to me which GCC front-end you mean. There is llvm-gcc (based on gcc-4.2) and the dragonegg plugin (the 2.9 version works with gcc-4.5; the development version works also with gcc-4.6). Can you please clarify.
That is probably not only tree optimizers. RTL optimizers seem not slow as well.By the way, some highly unscientific experiments I did suggest that the GCC tree optimizers are (almost) as fast as the LLVM IR optimizers while doing a better job;
while at -O3 the LLVM code generatorsI frequently see that on small benchmarks some optimizations (I mostly work on RA) look better than on bigger benchmarks. It would be interesting to run SPEC2006 for comparison because it contains even bigger benchmarks. Unfortunately, it will take 2 weeks on my machine to run SPEC2006 for the same # of option sets.
are significantly faster than the GCC code generators and do a comparable
and sometimes better job. Unfortunately I haven't had time to do a serious
study, so this might just be an accident of the benchmarks I looked at and
the options I happened to use rather than anything meaningful.
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |