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.133.124]) by sourceware.org (Postfix) with ESMTPS id B538F3857357 for ; Tue, 15 Aug 2023 14:15:06 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org B538F3857357 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=1692108906; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=AYhQXdD+mrPx8hSfW+FkRm58PvmOX+8ou1vPBllJlhA=; b=U9Wg3QIjw19MjiRCmGA7KCkImFnMBP53w2C6OXzfhZjU5SZpZHDaX4cLOMiMe/8cT0OFWv tGjiwiKFqtVBjAP+fqWj4/55N2FyvxDhRVV9HDvl/11PLpdtre/Re1Q036oRZ5dQ+ILGzg Kf1na/zBBljZLnwjBwhSVXooi9J7AiU= Received: from mail-qk1-f199.google.com (mail-qk1-f199.google.com [209.85.222.199]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-510-u7ls-Q5zNH6IRGcHezUmgA-1; Tue, 15 Aug 2023 10:15:05 -0400 X-MC-Unique: u7ls-Q5zNH6IRGcHezUmgA-1 Received: by mail-qk1-f199.google.com with SMTP id af79cd13be357-76d35f344b0so585937785a.0 for ; Tue, 15 Aug 2023 07:15:04 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1692108904; x=1692713704; h=content-transfer-encoding:in-reply-to:subject:from:references:to :content-language:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=AYhQXdD+mrPx8hSfW+FkRm58PvmOX+8ou1vPBllJlhA=; b=YRf44n2LSE7WQ+B7YUhtssSEmhYdGcZ/3mmXHgvC/XzTrqf2Rf6C5Aa8suginIIutN +JR0WCyFc5qhutGxWKD3TJNkkBmtAOjr7M/2M1PMWG11YcWEWrXZunDcxs/+C09U0YJ1 e3MDtYRXPhsa1Wsjpzk2bUKhuQYjr+8St9uodDj76K7sDzIJHuq08qTeJEFlaPiXIe6G 7IKCXMYHOPv98yK6Y4GyBhcCbxQYNOn0zQzKIa+q3FmMHuwebRjra4d++Xd0yd0v6Vgk XFGkRbO9nOho+4A+gJDgGDInvRoko0P5ekqqvri2tS6dDIgMKm1RWO0X7zJWA61d6CKm aViw== X-Gm-Message-State: AOJu0YwHUrDF4XdYMQF6tDNxEEk4elWMawJNc0T96MJU2FLrlWZuHdNj 65tTG7smbhBiqTAc2Pi3BAPo5YDmCKQ6mQJRR0tPLarPLynvl+vF1tLo+1eP2Larvqi479ibPWD oTOU9p7mV17o+PkxQS6BHdn1e1A== X-Received: by 2002:a05:620a:2996:b0:76c:b3cb:a7f0 with SMTP id r22-20020a05620a299600b0076cb3cba7f0mr17256797qkp.20.1692108903872; Tue, 15 Aug 2023 07:15:03 -0700 (PDT) X-Google-Smtp-Source: AGHT+IHoOZQh2Scm8vpGRYvySOBW+k90nZWbNsh6Ej77HP5OtJnXG7QNOMaTKrunVh7PKyiTrZWW8A== X-Received: by 2002:a05:620a:2996:b0:76c:b3cb:a7f0 with SMTP id r22-20020a05620a299600b0076cb3cba7f0mr17256776qkp.20.1692108903612; Tue, 15 Aug 2023 07:15:03 -0700 (PDT) Received: from [192.168.1.11] ([79.123.74.8]) by smtp.gmail.com with ESMTPSA id oo24-20020a05620a531800b00767f14f5856sm3774354qkn.117.2023.08.15.07.15.02 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 15 Aug 2023 07:15:03 -0700 (PDT) Message-ID: Date: Tue, 15 Aug 2023 15:15:01 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.13.0 To: ASSI , binutils@sourceware.org References: <87a5v24s61.fsf@Rainer.invalid> From: Nick Clifton Subject: Re: Replacement for "objdump -d -l"? In-Reply-To: <87a5v24s61.fsf@Rainer.invalid> X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Language: en-GB Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-3.6 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,NICE_REPLY_A,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: Hi ASSI, > Lastly, it seem brittle to parse the output as clearly it is meant to be > human readable and might change in future versions Correct. > (aside from the fact > there doesn't seem to be a documentation of the current format for > crying out loud). Because the output format has evolved rather than being specified by a standard. But to be fair, the output format does not change that much, and it could be documented if there really was a need. > I'd be much more content with a format that was > designed to be machine readable and fully documented (again llvm has an > objdump that produces YAML). Is there something like that in binutils I > can use? No, but it would be nice to have. A fixed, extensible, machine readable output format would be much appreciated as a new feature for objdump. All it really needs is someone with the time, knowledge and motivation to write it. Cheers Nick