From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9922 invoked by alias); 25 May 2005 15:16:27 -0000 Mailing-List: contact java-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: java-prs-owner@gcc.gnu.org Received: (qmail 9902 invoked by uid 48); 25 May 2005 15:16:27 -0000 Date: Wed, 25 May 2005 15:16:00 -0000 Message-ID: <20050525151627.9901.qmail@sourceware.org> From: "tromey at gcc dot gnu dot org" To: java-prs@gcc.gnu.org In-Reply-To: <20040330054337.14781.rmathew@hotmail.com> References: <20040330054337.14781.rmathew@hotmail.com> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug libgcj/14781] disable bytecode verification for bootclasspath X-Bugzilla-Reason: CC X-SW-Source: 2005-q2/txt/msg00569.txt.bz2 List-Id: ------- Additional Comments From tromey at gcc dot gnu dot org 2005-05-25 15:16 ------- We now have -verify and -noverify flags. However, we still verify classes found on the bootclasspath. I've changed this PR's synopsis to reflect this. One question is whether we care about the bootclasspath feature. -- What |Removed |Added ---------------------------------------------------------------------------- Summary|Need flag to disable |disable bytecode |bytecode verification |verification for | |bootclasspath http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14781