From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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 247203858D39 for ; Tue, 2 May 2023 06:03:34 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 247203858D39 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=1683007412; 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=IpwJ9lubv5+hE962TiiAp/24G0j32jq07Zlb7AwLFW0=; b=RtTu83pCKdGTdAmsEk73rkRB7qMvZwj6Z5prxPTv2+5TrMZNZBZXj/hAwyY7kenvf82sL2 DwIU/xr6Zri8m6D3F0Ot5j9ypvdjut1uYUFV5OVc/+UItorXuyuD2feHzdjzK7JnTKfuva /lWU9yukjcQgwoFzXzYi7DZLXhZGn4U= Received: from mimecast-mx02.redhat.com (mx3-rdu2.redhat.com [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-459-J1UdrFiXNkyA5fq8yJB8Bg-1; Tue, 02 May 2023 02:03:28 -0400 X-MC-Unique: J1UdrFiXNkyA5fq8yJB8Bg-1 Received: from smtp.corp.redhat.com (int-mx10.intmail.prod.int.rdu2.redhat.com [10.11.54.10]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 5B5151C05EB1; Tue, 2 May 2023 06:03:27 +0000 (UTC) Received: from oldenburg.str.redhat.com (unknown [10.2.16.10]) by smtp.corp.redhat.com (Postfix) with ESMTPS id A1F37483EC4; Tue, 2 May 2023 06:03:26 +0000 (UTC) From: Florian Weimer To: Indu Bhagat Cc: binutils@sourceware.org Subject: Re: Missing alignment in SFrame spec References: <87ildgbf9g.fsf@oldenburg.str.redhat.com> <2485551a-9608-e4ff-8d4c-bd7974c6c695@oracle.com> Date: Tue, 02 May 2023 08:03:25 +0200 In-Reply-To: <2485551a-9608-e4ff-8d4c-bd7974c6c695@oracle.com> (Indu Bhagat's message of "Mon, 1 May 2023 17:24:49 -0700") Message-ID: <87ildbuv6a.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.10 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain X-Spam-Status: No, score=-5.0 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_H2,SPF_HELO_NONE,SPF_NONE,TXREP,T_SCC_BODY_TEXT_LINE 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: * Indu Bhagat: > On 4/28/23 01:08, Florian Weimer wrote: >> The SFrame specification does not say anything explict about alignment. >> It uses ATTRIBUTE_PACKED, which strongly suggests alignment 1, but >> looking at the structures themselves, I think what you actually want is >> 4-byte alignment. >> Thanks, >> Florian >> > > Hi Florian, > > SFrame stack trace format is an unaligned on-disk format. IIUC, you > suggest 4 byte alignment for all structs in SFrame format? > > Yes, current SFrame FDE and SFrame FRE are 1-byte aligned. > > I had reasoned about unaligned accesses previously when a bug showed up. Well, GAS seems to generate 8-byte-aligned .sframe sections (at least in the 2.40-7.fc39 Fedora package). So all this is a bit inconsistent. Thanks, Florian