From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 947 invoked by alias); 1 Nov 2004 16:56:03 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 924 invoked by uid 48); 1 Nov 2004 16:56:01 -0000 Date: Mon, 01 Nov 2004 16:56:00 -0000 Message-ID: <20041101165601.923.qmail@sourceware.org> From: "giovannibajo at libero dot it" To: gcc-bugs@gcc.gnu.org In-Reply-To: <20040518194300.15524.pinskia@gcc.gnu.org> References: <20040518194300.15524.pinskia@gcc.gnu.org> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug tree-optimization/15524] [4.0 Regression] jump threading on trees is slow with switch statements with large # of cases X-Bugzilla-Reason: CC X-SW-Source: 2004-11/txt/msg00171.txt.bz2 List-Id: ------- Additional Comments From giovannibajo at libero dot it 2004-11-01 16:55 ------- > The effect for the test case of this PR is huge. > The effect on everything else (for example insn-attrtab) is not > measurable. We have had many bug reports from users trying to compile interpret-like code which is machine generated and is effectively made by giant switch statements. Improving this PR will definitely make their code go faster. In fact, if we are going to have a performance testsuite for GCC (as I asked to the SC lately), I would surely propose to put such a testcase in there. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15524