From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32743 invoked by alias); 20 Jan 2004 11:31:43 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 32728 invoked from network); 20 Jan 2004 11:31:34 -0000 Received: from unknown (HELO smtp2.libero.it) (193.70.192.52) by sources.redhat.com with SMTP; 20 Jan 2004 11:31:34 -0000 Received: from bagio (151.41.184.52) by smtp2.libero.it (7.0.020-DD01) id 3F6F0DA902210E99; Tue, 20 Jan 2004 12:32:13 +0100 Message-ID: <2e6801c3df48$f30b4fb0$34b82997@bagio> From: "Giovanni Bajo" To: "Karel Gardas" , "GCC Mailing List" References: Subject: Re: [UPDATED] GCC 3.4.0 20040114 + GCC 3.3.2 compile-time performance comparison on MICO project sources. Date: Tue, 20 Jan 2004 11:31:00 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-SW-Source: 2004-01/txt/msg01471.txt.bz2 Karel Gardas wrote: > I would also like to post bugreport to bugzilla, but I don't know how > to attach preprocessed file there. Is it possible to add them after > clicking on ``Commit'' button? Yes. Please, create a new bug report for *each* different regression. It's easier for us to track and comment on them, since they're different bugs anyway. > Should I copy whole email table there, or is > link to gcc mailing list enough? (I'm afraid about table re-formating in html, > I don't have experience with it under Mozilla) For each bug, you can report the bugs that matter (and link to the mailing list as a base reference for the discussion). Thanks! Giovanni Bajo