From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15532 invoked by alias); 17 Jun 2004 09:09:39 -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 15525 invoked by alias); 17 Jun 2004 09:09:38 -0000 Date: Thu, 17 Jun 2004 09:09:00 -0000 Message-ID: <20040617090938.15524.qmail@sourceware.org> From: "rguenth at tat dot physik dot uni-tuebingen dot de" To: gcc-bugs@gcc.gnu.org In-Reply-To: <20040616144705.16022.rguenth@tat.physik.uni-tuebingen.de> References: <20040616144705.16022.rguenth@tat.physik.uni-tuebingen.de> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug tree-optimization/16022] Excessive memory usage of vectorizer X-Bugzilla-Reason: CC X-SW-Source: 2004-06/txt/msg02090.txt.bz2 List-Id: ------- Additional Comments From rguenth at tat dot physik dot uni-tuebingen dot de 2004-06-17 09:09 ------- Subject: Re: Excessive memory usage of vectorizer On Wed, 16 Jun 2004, pinskia at gcc dot gnu dot org wrote: > I should note that -fno-excpetions just makes there be a lot less BB's so maybe where there is a huge > amount of BB it takes a huge amount of memory which is reasonable with leafify as every thing is > inlined. Of course. But I wonder if we cannot clean that up a little and merge BB's and/or EH regions here. Maybe we simply don't detect nothrow as good as we should. Richard. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16022