From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22826 invoked by alias); 17 Oct 2002 13:06:05 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 22811 invoked by uid 71); 17 Oct 2002 13:06:04 -0000 Date: Thu, 17 Oct 2002 06:06:00 -0000 Message-ID: <20021017130604.22807.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: Nathanael Nerode Subject: Re: c/7344: performance regression on huge case statements Reply-To: Nathanael Nerode X-SW-Source: 2002-10/txt/msg00662.txt.bz2 List-Id: The following reply was made to PR c/7344; it has been noted by GNATS. From: Nathanael Nerode To: gcc-gnats@gcc.gnu.org, rschiele@uni-mannheim.de, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org Cc: Subject: Re: c/7344: performance regression on huge case statements Date: Thu, 17 Oct 2002 08:59:26 -0400 What should we do for a test case here? I feel that it should have one, but the minimal testcase is *inherently* 239K, so I'm not quite sure what to do here. I guess ideally the testcase would generate a giant case statement, try to compile it, and kill the process if it took longer than (x) seconds. This is completely out of the normal test scheme however. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7344