This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/54710] moderately large tuple, with many gets, ballons compile time
- From: "cppljevans at suddenlink dot net" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 26 Sep 2012 19:01:30 +0000
- Subject: [Bug c++/54710] moderately large tuple, with many gets, ballons compile time
- Auto-submitted: auto-generated
- References: <bug-54710-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54710
--- Comment #5 from Larry Evans <cppljevans at suddenlink dot net> 2012-09-26 19:01:30 UTC ---
(In reply to comment #4)
> That:
>
> --enable-checking=assert,misc,tree,gc,rtl,runtime
>
> will enable very compile-time intensive internal checking. Use
> --enable-checking=release or at most the default checking options
> (which are "yes"). If you compare with other compilers always use
> release checking.
Thanks Richard.
I've downloaded:
ftp://gcc.gnu.org/pub/gcc/snapshots/4.8-20120923/gcc-4.8-20120923.tar.bz2
and configured with --enable-checking=release. As a result, the
gcc times to improve a lot; however, there's still the degredation
of the time w.r.t. clang and the macro, LAST_LESS approaches TUPLE_SIZE:
LAST_LESS gcc/clang times
--------- ---------------
4 0.28
16 1.15
20 1.70
Certainly 1.70 is much better than 3.34.
A new .zip file is attached. I don't know if this
indicates there's still a problem.
-regards,
Larry