From owner-freebsd-questions@FreeBSD.ORG Mon Sep 26 19:08:44 2011 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3392C1065670 for ; Mon, 26 Sep 2011 19:08:44 +0000 (UTC) (envelope-from ntai@smartfruit.com) Received: from hapkido.dreamhost.com (hapkido.dreamhost.com [66.33.216.122]) by mx1.freebsd.org (Postfix) with ESMTP id 15FA68FC13 for ; Mon, 26 Sep 2011 19:08:44 +0000 (UTC) Received: from homiemail-a66.g.dreamhost.com (caiajhbdcahe.dreamhost.com [208.97.132.74]) by hapkido.dreamhost.com (Postfix) with ESMTP id 0C9361862D3 for ; Mon, 26 Sep 2011 11:41:40 -0700 (PDT) Received: from homiemail-a66.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a66.g.dreamhost.com (Postfix) with ESMTP id 8D46F350078 for ; Mon, 26 Sep 2011 11:41:32 -0700 (PDT) Received: from [10.50.24.220] (gate.abinitio.com [65.170.40.132]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: smtpguy@smartfruit.com) by homiemail-a66.g.dreamhost.com (Postfix) with ESMTPSA id B456D35009C for ; Mon, 26 Sep 2011 11:41:21 -0700 (PDT) Message-ID: <4E80C751.4000504@smartfruit.com> Date: Mon, 26 Sep 2011 14:41:21 -0400 From: Naoyuki Tai User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.18) Gecko/20110613 Thunderbird/3.1.11 MIME-Version: 1.0 To: freebsd-questions@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: How should I complain about ARM compiler? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Sep 2011 19:08:44 -0000 Hello, I'm working on running a FreeBSD system on Globalscale's DreamPlug. It's an ARM processor hardware. I hit a problem which is the PR arm/154189, and it turned out that there is a bug in GCC's ARM's code generation. The GCC in arm's "world" is cross-compiled from Release 8.2 on i386, and is version 4.2.1. I looked at the GNU's bug tracking web site, and looks like the similar bug is reported but not exact. However, there is a certain chance that it is fixed in later versions of GCC than 4.2. I wanted to see whether or not fixed. So naturally, I tried to install the GCC versions from the port, but GCC 4.2 is the only one that supports ARM. None of newer versions is marked to work on ARM. I could file a PR to GNU's. If it's new or dupe or already-fixed bug, at some point, it may or may not be fixed. But, bigger problem to me is that, FreeBSD 8.2's GCC 4.2 is the only one that marked to work for ARM, either in the distribution or in the port tree. So, who should I complain to? Chances are slim that -STABLE's compiler gets updated to my liking. I have no way of knowing right now that the compilers in the ports work for me or not. My best case scenario is that, someone patches up GCC 4.2.1's arm backend in -STABLE. If this is to happen, am I filing a PR to -STABLE or under arm/ (which gets virtually no attension)? Should I ask GCC 4.5 or 4.6 to work for arm? It may or may not fix my problem, so I'm not sure I want to file PR for the GCCs in the port to support ARM. Although I was able to get around the build problem of perl5.12, (as in arm/154189), I just hit another problem with devel/icu, which I'm chasing right now, and maybe I have to file a PR. So, my confidence in GCC 4.2.1 for ARM is zero. Please someone tell me what is the right way to complain about the ARM's compiler situation. Thanks. -- Tai