From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <SRS0=pOUB=EN=redhat.com=fweimer@sourceware.org>
Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124])
	by sourceware.org (Postfix) with ESMTPS id 877833858D28
	for <libc-help@sourceware.org>; Mon, 28 Aug 2023 05:15:48 +0000 (GMT)
DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 877833858D28
Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=redhat.com
Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=redhat.com
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com;
	s=mimecast20190719; t=1693199748;
	h=from:from:reply-to:subject:subject:date:date:message-id:message-id:
	 to:to:cc:cc:mime-version:mime-version:content-type:content-type:
	 in-reply-to:in-reply-to:references:references;
	bh=GvJAtmh0diP5fV6vyxwbBCs9oybaDMZMRZ1CXt/5jhA=;
	b=U964PL2hsIn4GK7TaBMcdIxIKsnz12ZdzG6N14/9GGFSYjqPn8i/uXEYuhbCkpJJclmZdZ
	WVY1pXhvaq9vMpmI/PlJmgRwVS1LBGg0s0WEWiT0HwIDGNeEqNQ03Xr/LuJCLtcQDXiQxL
	+1EV7tURi4yHgKdCofzVuSexWLXB2gI=
Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com
 [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS
 (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
 us-mta-25-Xybm48urPZW3b7GfdZrZuQ-1; Mon, 28 Aug 2023 01:15:44 -0400
X-MC-Unique: Xybm48urPZW3b7GfdZrZuQ-1
Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.rdu2.redhat.com [10.11.54.6])
	(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 6A5B88D40A6;
	Mon, 28 Aug 2023 05:15:44 +0000 (UTC)
Received: from oldenburg.str.redhat.com (unknown [10.2.16.25])
	by smtp.corp.redhat.com (Postfix) with ESMTPS id C4A0C2166B25;
	Mon, 28 Aug 2023 05:15:43 +0000 (UTC)
From: Florian Weimer <fweimer@redhat.com>
To: James Le Cuirot <chewi@aura-online.co.uk>
Cc: libc-help@sourceware.org,  John Paul Adrian Glaubitz
 <glaubitz@physik.fu-berlin.de>
Subject: Re: Tuple and changes for m68k with -malign-int
References: <e9035006d50933fb02727fa373629cc821784f6c.camel@aura-online.co.uk>
Date: Mon, 28 Aug 2023 07:15:42 +0200
In-Reply-To: <e9035006d50933fb02727fa373629cc821784f6c.camel@aura-online.co.uk>
	(James Le Cuirot's message of "Sat, 26 Aug 2023 09:53:30 +0100")
Message-ID: <87bkerzr0h.fsf@oldenburg.str.redhat.com>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.2 (gnu/linux)
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 3.1 on 10.11.54.6
X-Mimecast-Spam-Score: 0
X-Mimecast-Originator: redhat.com
Content-Type: text/plain
X-Spam-Status: No, score=-4.6 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H4,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE,SPF_NONE,TXREP autolearn=ham autolearn_force=no version=3.4.6
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org
List-Id: <libc-help.sourceware.org>

* James Le Cuirot:

> We think this warrants a new tuple, and we'd like to ensure that everyone gets
> behind the same one. It is currently m68k-*-gnu. Perhaps it could be
> m68k-*-gnu32 or m68k-*-gnu32a? I considered gnu32i (for int), but the flag
> actually affects floats and doubles too. I don't really care what it is
> though, so feel free to suggest something totally different.

Would it make sense to increase alignment for double and long long to 64
bits at the same time?  Or is that not needed because m68k has DCAS of
two 32-bit words?

Thanks,
Florian