From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14957 invoked by alias); 5 Aug 2012 12:34:11 -0000 Received: (qmail 14898 invoked by uid 22791); 5 Aug 2012 12:34:10 -0000 X-SWARE-Spam-Status: No, hits=-4.3 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00,KHOP_THREADED X-Spam-Check-By: sourceware.org Received: from localhost (HELO gcc.gnu.org) (127.0.0.1) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sun, 05 Aug 2012 12:33:57 +0000 From: "steven at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c/54179] please split insn-emit.c ! Date: Sun, 05 Aug 2012 12:34:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: steven at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2012-08/txt/msg00246.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54179 --- Comment #9 from Steven Bosscher 2012-08-05 12:33:56 UTC --- (In reply to comment #7) > cc1 is writing about one line every 2 minutes to its assembler output file: If you've really configured with --enable-stage1-checking=all, you've enabled some checks that can cause this kind of slowdown. One of these checks is an internal memory integrity check on the garbage collector. I suspect that what you're seeing, is a garbage collection attempt between every insn emitted. That would mark-and-sweeps all memory between each assembler output line. All forms of --enable-checking=all are really for debugging purposes only, and even then only for cases where GDB doesn't help (Heisenbug-like issues, strange memory corruption problems, etc.). GCC 4.7.1 is a release compiler, you shouldn't have to configure with any checking flags enabled (configure will default to --enable-checking=release). In other words, if this problem is what I suspect, then this bug is one of those "Doctor it hurts if I ..." problems. ;-) Can you please try without -enable-stage1-checking=all?