From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13826 invoked by alias); 25 Apr 2010 18:06:20 -0000 Received: (qmail 13818 invoked by uid 22791); 25 Apr 2010 18:06:19 -0000 X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from smtp-out.google.com (HELO smtp-out.google.com) (216.239.44.51) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sun, 25 Apr 2010 18:06:15 +0000 Received: from wpaz5.hot.corp.google.com (wpaz5.hot.corp.google.com [172.24.198.69]) by smtp-out.google.com with ESMTP id o3PI6DVh005545 for ; Sun, 25 Apr 2010 11:06:13 -0700 Received: from pzk30 (pzk30.prod.google.com [10.243.19.158]) by wpaz5.hot.corp.google.com with ESMTP id o3PI6CCx018372 for ; Sun, 25 Apr 2010 11:06:12 -0700 Received: by pzk30 with SMTP id 30so7050951pzk.12 for ; Sun, 25 Apr 2010 11:06:12 -0700 (PDT) Received: by 10.115.86.38 with SMTP id o38mr2955484wal.170.1272218772244; Sun, 25 Apr 2010 11:06:12 -0700 (PDT) Received: from coign.google.com (adsl-71-133-8-30.dsl.pltn13.pacbell.net [71.133.8.30]) by mx.google.com with ESMTPS id c22sm16662706wam.18.2010.04.25.11.06.09 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 25 Apr 2010 11:06:10 -0700 (PDT) To: Martin Guy Cc: "gcc\@gcc.gnu.org" Subject: Re: merging the maverick FPU patches References: From: Ian Lance Taylor Date: Sun, 25 Apr 2010 18:07:00 -0000 In-Reply-To: (Martin Guy's message of "Sun\, 25 Apr 2010 09\:40\:03 +0100") Message-ID: User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-System-Of-Record: true X-IsSubscribed: yes Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org X-SW-Source: 2010-04/txt/msg00728.txt.bz2 Martin Guy writes: > now that stage3 is over I'm thinking of updating the > MaverickCrunch FPU fixes (currently for 4.3) and merging them but > would appreciate some guidance. > > There are 26 patches in all and I can't expect anyone to understand > them because they require a good understanding of the FPU and its > hardware bugs (and there are a lot of them!) :) What's the best path? > Create a branch, work there and then merge when done? > > I have done the copyright assignment stuff but don't have an account > on gcc.gnu.org. They all affect files under config/arm/ apart from one > testsuite fix and the docs. For a backend specific patch like this, I would recommend contacting the ARM backend maintainers directly to ask how they would prefer to proceed. They can be found in the top level MAINTAINERS file: arm port Nick Clifton nickc@redhat.com arm port Richard Earnshaw richard.earnshaw@arm.com arm port Paul Brook paul@codesourcery.com Ian