From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26463 invoked by alias); 31 Jul 2002 01:31:45 -0000 Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org Received: (qmail 26453 invoked from network); 31 Jul 2002 01:31:44 -0000 Received: from unknown (HELO hiauly1.hia.nrc.ca) (132.246.100.193) by sources.redhat.com with SMTP; 31 Jul 2002 01:31:44 -0000 Received: from hiauly1.hia.nrc.ca (localhost [127.0.0.1]) by hiauly1.hia.nrc.ca (8.12.0.Beta16/8.12.0.Beta16) with ESMTP id g6V1Vg00021310; Tue, 30 Jul 2002 21:31:43 -0400 (EDT) Received: (from dave@localhost) by hiauly1.hia.nrc.ca (8.12.0.Beta16/8.12.0.Beta16) id g6V1VfNE021308; Tue, 30 Jul 2002 21:31:41 -0400 (EDT) Message-Id: <200207310131.g6V1VfNE021308@hiauly1.hia.nrc.ca> Subject: Re: RFC: New approach to --with-cpu To: gcc-patches@gcc.gnu.org Date: Tue, 30 Jul 2002 18:54:00 -0000 From: "John David Anglin" Cc: drow@mvista.com MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-SW-Source: 2002-07/txt/msg01845.txt.bz2 >From a PA standpoint, the main objection that I have to this approach is that there seems to be a slight loss of flexibility. You use "with_cpu" to set the default scheduling model. However, I was also planning to set the default arch based on the target machine when a linker bug in handling PA2.0 code is fixed. I view these options as independent although the configure defaults would both be based on the target triplet. Thus, it would be necessary to introduce a new configure option to handle the arch default. In the future, I can see other default code generation options being set-table. I must admit that I don't really like the multilib concept and find it a rather idea to build libraries for all scheduling models, archs, etc. Thus, I don't find this justification attractive. Dave -- J. David Anglin dave.anglin@nrc.ca National Research Council of Canada (613) 990-0752 (FAX: 952-6605)