From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14222 invoked by alias); 18 Feb 2002 23:01:10 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 14162 invoked by uid 61); 18 Feb 2002 23:01:07 -0000 Date: Mon, 18 Feb 2002 15:01:00 -0000 Message-ID: <20020218230107.14158.qmail@sources.redhat.com> To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, harri.pasanen@trema.com, jdonner@schedsys.com, ljrittle@gcc.gnu.org, nobody@gcc.gnu.org From: ljrittle@gcc.gnu.org Reply-To: ljrittle@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, harri.pasanen@trema.com, jdonner@schedsys.com, ljrittle@gcc.gnu.org, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org X-Mailer: gnatsweb 2.9.3 Subject: Re: bootstrap/3314: --enable-threads does not seem to be working for HP-UX 11.00 X-SW-Source: 2002-02/txt/msg00449.txt.bz2 List-Id: Synopsis: --enable-threads does not seem to be working for HP-UX 11.00 Responsible-Changed-From-To: ljrittle->unassigned Responsible-Changed-By: ljrittle Responsible-Changed-When: Mon Feb 18 15:01:05 2002 Responsible-Changed-Why: Just marking that I am no longer working on this problem (sorry to have kept it assigned to myself for so long with no final progress). In general, a complete fix requires moving all control from gcc/config.gcc to gcc/configure.in . It would be better to provide all legal values (and a hint for the default for the target) for --enable-threads in gcc/config.gcc and centralize the seclection of the thread model after config.gcc is parsed. You will note that the control logic is currently spread to the following locations: - before config.gcc is parsed (in configure) - per-host in config.gcc with much duplication and many annoying subtle differences - after config.gcc is parsed (back in configure) When the user specifies a value for --enable-threads that is not legal for the target or specifies --enable-threads without a value and the target default is single; the "early configure" should abort with a clear message. A patch was posted that handles the second issue without moving all the control logic as should (IMHO) be done. It moved most control logic related to thread model selection within configure to after config.gcc was parsed without touching config.gcc. This less than ideal improvement was never fully accepted or rejected. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=3314