From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6160 invoked by alias); 10 Dec 2012 16:25:50 -0000 Received: (qmail 6137 invoked by uid 22791); 10 Dec 2012 16:25:47 -0000 X-SWARE-Spam-Status: No, hits=-2.1 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,RCVD_IN_DNSWL_LOW,TW_BF X-Spam-Check-By: sourceware.org Received: from youngberry.canonical.com (HELO youngberry.canonical.com) (91.189.89.112) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 10 Dec 2012 16:25:39 +0000 Received: from dslb-088-073-119-085.pools.arcor-ip.net ([88.73.119.85] helo=[192.168.42.216]) by youngberry.canonical.com with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1Ti6Ak-0002Kw-AJ; Mon, 10 Dec 2012 16:25:38 +0000 Message-ID: <50C60CFF.50408@ubuntu.com> Date: Mon, 10 Dec 2012 16:25:00 -0000 From: Matthias Klose User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: Anthony Green CC: GCJ-patches , Marcus Shawcroft , Richard Earnshaw Subject: please merge libffi trunk into GCC Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact java-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: java-patches-owner@gcc.gnu.org X-SW-Source: 2012-q4/txt/msg00048.txt.bz2 Hi, please could you merge libffi into GCC trunk for one more time? Motivation is to get the aarch64 port into GCC 4.8. I assume such a merge would require approval by the java maintainers. As an alternative, could the aarch64 port go to the trunk even without a libffi merge? I would like to see the aarch64 port in the gcc-4.7 aarch64 branch too. Thanks, Matthias