From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13789 invoked by alias); 7 Nov 2002 00:00:29 -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 13782 invoked from network); 7 Nov 2002 00:00:28 -0000 Received: from unknown (HELO localhost.localdomain) (66.60.148.227) by sources.redhat.com with SMTP; 7 Nov 2002 00:00:28 -0000 Received: from warlock.codesourcery.com (localhost.localdomain [127.0.0.1]) by localhost.localdomain (8.11.6/8.11.6) with ESMTP id gA6Nvvd10429; Wed, 6 Nov 2002 15:57:57 -0800 Date: Wed, 06 Nov 2002 16:00:00 -0000 From: Mark Mitchell To: Zack Weinberg , "gcc-patches@gcc.gnu.org" Subject: Re: [basic-improvements] [RFD] VxWorks thread support, part two Message-ID: <33040000.1036627076@warlock.codesourcery.com> In-Reply-To: <20021105060359.GB10353@egil.codesourcery.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-SW-Source: 2002-11/txt/msg00375.txt.bz2 > In the near future these hooks are going to be included with VxWorks. > However, it also makes sense to distribute the code for them with GCC, > and describe how to use them in GCC's installation instructions. I > would like some suggestions for where to put the code. It doesn't > seem right to put it in gcc/config as it won't be built with the > compiler. contrib? Yes, that sounds right. -- Mark Mitchell mark@codesourcery.com CodeSourcery, LLC http://www.codesourcery.com