From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca (simark.ca [158.69.221.121]) by sourceware.org (Postfix) with ESMTPS id 9AB703959C92 for ; Tue, 10 Mar 2020 15:45:55 +0000 (GMT) Received: from [172.16.0.95] (192-222-181-218.qc.cable.ebox.net [192.222.181.218]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by simark.ca (Postfix) with ESMTPSA id F10971E4A5; Tue, 10 Mar 2020 11:45:54 -0400 (EDT) Subject: Re: [PATCH] gdb: recognize 64 bits Windows executables as Cygwin osabi To: Eli Zaretskii , Jon Turney Cc: gdb-patches@sourceware.org References: <20200307041742.31158-1-simon.marchi@efficios.com> <83zhcsa8my.fsf@gnu.org> <4bd435cd-b06d-e0fc-70a9-9a8a18d73987@efficios.com> <835zfg9hz5.fsf@gnu.org> <85cd5fc2-8fa7-3612-b974-b3a3261bbb29@dronecode.org.uk> <83pndk9r5v.fsf@gnu.org> From: Simon Marchi Message-ID: <97ad4d74-4c9b-8630-f573-ca6d476dfe21@simark.ca> Date: Tue, 10 Mar 2020 11:45:54 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.4.1 MIME-Version: 1.0 In-Reply-To: <83pndk9r5v.fsf@gnu.org> Content-Type: text/plain; charset=utf-8 Content-Language: tl Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00, SPF_HELO_PASS, SPF_PASS autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: gdb-patches@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Mar 2020 15:45:58 -0000 On 2020-03-10 11:16 a.m., Eli Zaretskii wrote: >> From: Jon Turney >> Date: Sun, 8 Mar 2020 14:05:10 +0000 >> >>>> So what we can do is add an "MS-Windows" osabi and make "Cygwin" and >>>> "MS-Windows" functionally equivalent. Any "pei-i386" or "pei-x86-64" >>>> executable would be detected as "MS-Windows". >> >> I believe this suggestion for x86_64 is wrong, in the other direction: >> x86_64 Cygwin is LP64, but Windows is LLP64 (Se also table in [1]) > > If the LP64 thing is part of what defines the OS ABI, then yes, Cygwin > should have a separate value. If I understand correctly, that's one practical reason for introducing the separate "Windows" OS ABI? Simon