This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c/12322] New: Significant slowdown when compiling computed-goto code in Parrot
- From: "ahaas at airmail dot net" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 17 Sep 2003 23:33:50 -0000
- Subject: [Bug c/12322] New: Significant slowdown when compiling computed-goto code in Parrot
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12322
Summary: Significant slowdown when compiling computed-goto code
in Parrot
Product: gcc
Version: 3.4
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: c
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: ahaas at airmail dot net
CC: gcc-bugs at gcc dot gnu dot org
GCC host triplet: i586-pc-linux-gnu
The GCC-3.4 development snapshots take 5x or 6x as long to compile the
computed-goto heavy 'core_ops_cg.c' in Parrot. GCC-3.3 compiles this file in
about five or six minutes on my slow machine - GCC-3.4 takes 30 or more minutes.
The memory usage appears to be roughly the same as that of GCC-3.3 as indicated
by top.
Parrot is the engine on what will be Perl 6. The 'core_ops_cg.c' file is
generated automatically by the Parrot build process and is about 280K in size.
Parrot can be downloaded from
http://www.parrotcode.org