From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id iIt9LA+NjmfPnxUAWB0awg (envelope-from ) for ; Mon, 20 Jan 2025 12:51:11 -0500 Received: by simark.ca (Postfix, from userid 112) id 79E471E100; Mon, 20 Jan 2025 12:51:11 -0500 (EST) X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-13) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-5.3 required=5.0 tests=ARC_SIGNED,ARC_VALID,BAYES_00, MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED autolearn=ham autolearn_force=no version=4.0.0 Received: from server2.sourceware.org (server2.sourceware.org [8.43.85.97]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id 6C4841E05C for ; Mon, 20 Jan 2025 12:51:08 -0500 (EST) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id A16D9385842A for ; Mon, 20 Jan 2025 17:51:07 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org A16D9385842A Received: from angie.orcam.me.uk (angie.orcam.me.uk [IPv6:2001:4190:8020::34]) by sourceware.org (Postfix) with ESMTP id C6A483858D39; Mon, 20 Jan 2025 17:50:32 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org C6A483858D39 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=orcam.me.uk Authentication-Results: sourceware.org; spf=none smtp.mailfrom=orcam.me.uk ARC-Filter: OpenARC Filter v1.0.0 sourceware.org C6A483858D39 Authentication-Results: server2.sourceware.org; arc=none smtp.remote-ip=2001:4190:8020::34 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1737395432; cv=none; b=oshGaK5NeNpuBm/lSaxIW8f1sBpZS+HMw0ePX/DX8YaxsvEO1RWX/+jGW8IKYfaFQ93+GJQYiuU8kSkN7uTAVwzVK0UyGsLYvOgURCLfstCZWI9NkbWO+lJ6O/fTZXqtpSzv/CskfotNzpP0wUJ+RkjxHQSwTrcvpHSrc1mFnDI= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1737395432; c=relaxed/simple; bh=CpmKG+uG4IRP0KcqOP1Z1cgSXht7GAZhTxc83tGcXcI=; h=Date:From:To:Subject:Message-ID:MIME-Version; b=YYqQGV6qQzKTi0x8RsEw/TuPT7i8ItRqLL+nk8197zxwE8LE2+R+t+1nZ5iL7sfq7cGT3oH3NneWkxMytQ1p9w/pfqkKPUFyf42qM5GpJDSV+NwjR4qaT4ji3jIDJgqGTg0mRDz7AZ1b1BWJ3rOFq3VN9KVpgibQly9VrNMOPO0= ARC-Authentication-Results: i=1; server2.sourceware.org DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C6A483858D39 Received: by angie.orcam.me.uk (Postfix, from userid 500) id 2AC7492009C; Mon, 20 Jan 2025 18:50:32 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by angie.orcam.me.uk (Postfix) with ESMTP id 25E4C92009B; Mon, 20 Jan 2025 17:50:32 +0000 (GMT) Date: Mon, 20 Jan 2025 17:50:32 +0000 (GMT) From: "Maciej W. Rozycki" To: Ivan Kokshaysky , Nick Clifton cc: binutils@sourceware.org, gdb-patches@sourceware.org Subject: Re: [PATCH v2] alpha, ld: remove -taso option In-Reply-To: Message-ID: References: User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-BeenThere: gdb-patches@sourceware.org X-Mailman-Version: 2.1.30 Precedence: list List-Id: Gdb-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: gdb-patches-bounces~public-inbox=simark.ca@sourceware.org On Sat, 18 Jan 2025, Ivan Kokshaysky wrote: > The -taso switch was quite useful 25 years ago for porting 32-bit > code with broken integer-pointer casting. Not anymore. The EF_ALPHA_32BIT > Linux support is going to be dropped in kernel v6.14 [1], NetBSD and OpenBSD > never had it, so there is no point in keeping the -taso option around. > > Also remove alpha special case that uses -taso from gdb.base/dump.exp > in gdb testsuite. > > [1] https://lore.kernel.org/all/87jzb2tdb7.fsf_-_@email.froward.int.ebiederm.org > > Signed-off-by: Ivan Kokshaysky > --- > Changes in v2, suggested by Maciej W. Rozycki: > - leave the translations alone; > - remove OPTION_TASO from ld/ldlex.h; > - add entries to ld/NEWS and binutils/NEWS. I forgot we have per-tool-directory NEWS, so thanks for updating ld/NEWS and I think we don't want a duplicate entry in binutils/NEWS, which is for the other tools. No need to send v3 I suppose, this can be fixed up at patch installation time. Your change looks good to me and I've run it through binutils regression testing, so as long as Nick is fine with it and someone on the GDB side acks the GDB test update I can install it for you once binutils 2.44 have been released in ~fortnight time. Maciej