From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9055 invoked by alias); 15 Mar 2013 14:05:53 -0000 Received: (qmail 9042 invoked by uid 22791); 15 Mar 2013 14:05:52 -0000 X-SWARE-Spam-Status: No, hits=-4.6 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,KHOP_THREADED,RCVD_IN_HOSTKARMA_W,RCVD_IN_HOSTKARMA_WL X-Spam-Check-By: sourceware.org Received: from relay1.mentorg.com (HELO relay1.mentorg.com) (192.94.38.131) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 15 Mar 2013 14:05:47 +0000 Received: from svr-orw-fem-01.mgc.mentorg.com ([147.34.98.93]) by relay1.mentorg.com with esmtp id 1UGVGT-00059h-NU from Yao_Qi@mentor.com for gdb-patches@sourceware.org; Fri, 15 Mar 2013 07:05:45 -0700 Received: from SVR-ORW-FEM-04.mgc.mentorg.com ([147.34.97.41]) by svr-orw-fem-01.mgc.mentorg.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Fri, 15 Mar 2013 07:05:45 -0700 Received: from qiyao.dyndns.org (147.34.91.1) by svr-orw-fem-04.mgc.mentorg.com (147.34.97.41) with Microsoft SMTP Server id 14.1.289.1; Fri, 15 Mar 2013 07:05:44 -0700 Message-ID: <51432A7B.7040003@codesourcery.com> Date: Fri, 15 Mar 2013 14:05:00 -0000 From: Yao Qi User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: Subject: Re: Compilation failure for mingw64 target (was New ARI warning Fri Mar 15 02:02:12 UTC 2013 in -D 2013-03-15-gmt) References: <20130315020212.GA23545@sourceware.org> <5142E409.5090109@codesourcery.com> <002901ce2162$414d7530$c3e85f90$@muller@ics-cnrs.unistra.fr> <51430063.2060007@codesourcery.com> In-Reply-To: <51430063.2060007@codesourcery.com> Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 8bit X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2013-03/txt/msg00665.txt.bz2 On 03/15/2013 07:05 PM, Yao Qi wrote: > This problem is addressed by using "native" endianness in CTF metadata, > so BYTE_ORDER and LITTLE_ENDIAN can be avoided. After exchanging mail with CTF folk, I am suggested that "le" or "be" should be explicitly mentioned in the trace description, instead of "native". I'll update this part soon. -- Yao (齐尧)