From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26790 invoked by alias); 7 Oct 2003 18:16:41 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 26782 invoked from network); 7 Oct 2003 18:16:40 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sources.redhat.com with SMTP; 7 Oct 2003 18:16:40 -0000 Received: from drow by nevyn.them.org with local (Exim 4.22 #1 (Debian)) id 1A6wNz-0006Ly-AX; Tue, 07 Oct 2003 14:16:39 -0400 Date: Tue, 07 Oct 2003 18:16:00 -0000 From: Daniel Jacobowitz To: Tal Agmon Cc: gcc@gcc.gnu.org Subject: Re: Joining GCC for version 3.4 Message-ID: <20031007181639.GA20632@nevyn.them.org> Mail-Followup-To: Tal Agmon , gcc@gcc.gnu.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.1i X-SW-Source: 2003-10/txt/msg00212.txt.bz2 On Tue, Oct 07, 2003 at 07:06:23PM +0300, Tal Agmon wrote: > Hi, > > My team is in a process of contributing a new architecture to GCC. Can > someone please tell me what is the last date for adding a it to 3.4 > version? > > Regards, > > Tal Agmon > National Semiconductor It's probably too late. Of course, if the port doesn't require any changes outside a new config/ directory then the release manager's more likely to make an exception. Take a look at the gcc.gnu.org web site, where there is a future development timeline. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer