public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: ljrittle@gcc.gnu.org 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 Subject: Re: bootstrap/3314: --enable-threads does not seem to be working for HP-UX 11.00 Date: Mon, 18 Feb 2002 15:01:00 -0000 [thread overview] Message-ID: <20020218230107.14158.qmail@sources.redhat.com> (raw) 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
next reply other threads:[~2002-02-18 23:01 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-02-18 15:01 ljrittle [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-05-14 8:16 Dara Hazeghi 2002-01-15 8:46 Craig Rodrigues 2002-01-14 19:16 Craig Rodrigues 2001-06-21 14:34 ljrittle 2001-06-21 1:36 harri.pasanen
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20020218230107.14158.qmail@sources.redhat.com \ --to=ljrittle@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=harri.pasanen@trema.com \ --cc=jdonner@schedsys.com \ --cc=nobody@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).