From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25111 invoked by alias); 15 May 2012 18:38:12 -0000 Received: (qmail 24856 invoked by uid 22791); 15 May 2012 18:38:10 -0000 X-SWARE-Spam-Status: No, hits=-5.6 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,KHOP_RCVD_TRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE X-Spam-Check-By: sourceware.org Received: from mail-wi0-f177.google.com (HELO mail-wi0-f177.google.com) (209.85.212.177) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 15 May 2012 18:37:57 +0000 Received: by wibhm14 with SMTP id hm14so3954509wib.12 for ; Tue, 15 May 2012 11:37:55 -0700 (PDT) MIME-Version: 1.0 Received: by 10.180.109.229 with SMTP id hv5mr37720863wib.0.1337107075483; Tue, 15 May 2012 11:37:55 -0700 (PDT) Received: by 10.180.8.134 with HTTP; Tue, 15 May 2012 11:37:55 -0700 (PDT) In-Reply-To: <4FB2525C.1050309@redhat.com> References: <1298845471.12108.12.camel@jsm2> <1299515895.3262.1.camel@jsm2> <4D7F247D.6070303@redhat.com> <1300201861.20997.3.camel@jsm2> <1324419607.8652.84.camel@jsm2> <1324423375.8652.94.camel@jsm2> <4EF36049.3050802@ipdatasys.com> <1324575421.2430.42.camel@jsm2> <1325800936.20629.53.camel@jsm2> <4F0C4DFE.4050801@redhat.com> <1330300482.15684.10.camel@jsm2> <1331564819.2407.61.camel@jsm2> <1333370230.16991.34.camel@jsm2> <1335197942.13205.295.camel@jsm2> <1337003987.27195.60.camel@jsm2> <4FB2525C.1050309@redhat.com> Date: Tue, 15 May 2012 18:38:00 -0000 Message-ID: Subject: Re: 68hc11/12/s12x/xgate patch From: Fred Cooke To: nick clifton Cc: "binutils@sourceware.org" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes Mailing-List: contact binutils-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: binutils-owner@sourceware.org X-SW-Source: 2012-05/txt/msg00200.txt.bz2 Hi Nick, It's really exciting to see James' general fixes and additions to some of the S12 architecture code make it into the source. Thank you for finally getting around to doing that, I know quite a few people will appreciate it. What's less exciting, or perhaps, somewhat disturbing, is that you included the XGATE portion of James' work, which you have previously described as "A magnet for bugs". I agree with your initial prognosis and, quite frankly, I'm not comfortable using the official sources to build binaries for my users. Our application isn't a typical software system, in fact, quite the opposite. Thousands of dollars of hardware are at stake with each installation, and a failure from a new S12 binutils bug could potentially lead to loss of life. Currently our system has a clean reputation that I'm unenthusiastic about compromising, especially in a life threatening way. References: http://cygwin.com/ml/binutils/2012-01/msg00057.html http://cygwin.com/ml/binutils/2012-01/msg00087.html http://cygwin.com/ml/binutils/2012-01/msg00089.html Due to the current state of the S12 code, as of today, I'll now have to build and distribute binaries based on a fork or older version. It's unfortunate that this extra work load has not subsided as it appeared it was soon going to. I look forward to a time when I can have faith in the vanilla S12 binutils again and shall be personally taking measures to make that happen as soon as possible. Regards, Fred. On Tue, May 15, 2012 at 2:55 PM, nick clifton wrote: > > Hi James, > >> just wondered if you had found time to review the patch I submitted. >> (Patch is in http://sourceware.org/ml/binutils/2012-03/msg00123.html ) > > > Sorry it has taken me so long to review this patch, and thanks for the pi= ng. > > I have now gone over the patch. =A0There were a few formatting issues, bu= t these were minor. =A0The main thing (to me) is that it works and it does = not break any other ports. =A0So I have checked it in. > > This does mean that we now have two different ways of supporting the XGAT= E processor. =A0I feel that the best way to resolve this is to see how thes= e two ports fare in the long term. =A0If one of them turns out to be too bu= ggy or unmaintained then it will be dropped. > > Cheers > =A0Nick > >