From: Duncan Sands <baldrick@free.fr>
To: gcc@gcc.gnu.org
Subject: Re: Comparison of GCC-4.6.1 and LLVM-2.9 on x86/x86-64 targets
Date: Wed, 07 Sep 2011 15:29:00 -0000 [thread overview]
Message-ID: <4E678DB1.4000303@free.fr> (raw)
In-Reply-To: <4E678A9B.3040303@redhat.com>
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. 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 generators
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.
Ciao, Duncan.
next prev parent reply other threads:[~2011-09-07 15:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-07 15:16 Vladimir Makarov
2011-09-07 15:29 ` Duncan Sands [this message]
2011-09-07 16:59 ` Vladimir Makarov
2011-09-07 15:55 ` Xinliang David Li
2011-09-07 16:24 ` Vladimir Makarov
2011-09-08 8:23 ` Richard Guenther
2011-09-08 9:22 ` Duncan Sands
2011-09-09 14:02 ` Vladimir Makarov
2011-09-07 17:01 ` Duncan Sands
2011-09-08 8:47 ` Jakub Jelinek
2011-09-09 14:26 ` Vladimir Makarov
2011-09-09 14:36 ` Jakub Jelinek
2011-09-09 23:30 ` Lawrence Crowl
2011-09-10 13:22 ` Gabriel Dos Reis
2011-09-12 16:40 ` Vladimir Makarov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E678DB1.4000303@free.fr \
--to=baldrick@free.fr \
--cc=gcc@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).