From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30440 invoked by alias); 20 Feb 2006 22:36:30 -0000 Received: (qmail 30358 invoked by uid 48); 20 Feb 2006 22:35:58 -0000 Date: Mon, 20 Feb 2006 22:36:00 -0000 Message-ID: <20060220223558.30357.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug tree-optimization/26388] Variable sized storage allocation should be promoted to stack allocation In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "falk at debian dot org" 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 X-SW-Source: 2006-02/txt/msg02353.txt.bz2 List-Id: ------- Comment #4 from falk at debian dot org 2006-02-20 22:35 ------- This would be incredibly difficult to detect reliably. But the main problem is, on most operating systems, stack space is limited, typically to something tiny compared to main memory like 8M, so this wouldn't really be a good idea. Anyway, due to the amortization, I suspect it wouldn't save all that much time. Have you tried some benchmarks? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26388