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 1E5283858D20 for ; Tue, 30 May 2023 10:51:01 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 1E5283858D20 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=1685443860; 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: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=3+99Ko2wq2vdR1+qBWVrMbVvTYC4xTXbyJOkhri2/n4=; b=SY4XhEj7yHW9TlhSbvZkDDhD+yOy4rgDQaT4SMw93eo/C+EgcwyL0Vj8jF4cXtOg6VID9m eUznc3pUd1umHgUfDTwumQbfCZ1v9LHfQSBOaFieuqmmrmj02IarLYnErXiiSncZJJamyp cgVzI0eTEMj8P9vDzCDKwVxJowiyj1g= Received: from mail-wr1-f72.google.com (mail-wr1-f72.google.com [209.85.221.72]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-573-m01Dd1R-MmqqNwVWUGZC7w-1; Tue, 30 May 2023 06:50:59 -0400 X-MC-Unique: m01Dd1R-MmqqNwVWUGZC7w-1 Received: by mail-wr1-f72.google.com with SMTP id ffacd0b85a97d-30ae8776c12so1105001f8f.1 for ; Tue, 30 May 2023 03:50:58 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1685443857; x=1688035857; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=3+99Ko2wq2vdR1+qBWVrMbVvTYC4xTXbyJOkhri2/n4=; b=L8cSOATEyB6IMkRqMcxY4C8Y0Z+SAD7qqsAlbyM4ZJnQs+c3UZKXPmBun+QcXH/EwN 8LDY0h4eiTgvQjfFqPpFEi/y7TOmLJc4vbtaBEHTn8cibPGdW93urmZCY92DmFP4XSSO ZYDFG1FwBGcH8lFwUayOW4v5saMXAutU1bVb9a16HvHJ3ITcS0YqbKYq9Eu50CFJqkMA 7v+yAspP6i4JGGWw84H2H+4/aCfqRbbqYx38q2WtAAM7kotzalMPr7jofzJvveV7ug29 Ph9uNvJGBiXEnYlX+qbopNZX/jpXy4KIQTerHi0+D74t2498ewd7zwQT8LDAQk4ldiHo kD+g== X-Gm-Message-State: AC+VfDx71WnfrLeblcJtklrK5HPdeHj1lNhXB5JEEqP85kT/kZC5gfTO i9pWwD5KupIyJj1JmM4nJDG24gbITyTpgB24puEjQdX4HHYihCTE3Wjy05K9j+9RhW+RSJaafVI rpulAKsGA+oXu5HfG7EPtuz3Dgg== X-Received: by 2002:adf:e7c5:0:b0:309:33c4:52df with SMTP id e5-20020adfe7c5000000b0030933c452dfmr1780637wrn.30.1685443857369; Tue, 30 May 2023 03:50:57 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ6Jzweq/fN0W6+QDhZB62F4b6AvVkSUSmlkLNo3GyVHufwGU0LmCwlr7E/lrc5jMAjipfZy2w== X-Received: by 2002:adf:e7c5:0:b0:309:33c4:52df with SMTP id e5-20020adfe7c5000000b0030933c452dfmr1780617wrn.30.1685443857145; Tue, 30 May 2023 03:50:57 -0700 (PDT) Received: from [192.168.1.7] ([80.168.198.238]) by smtp.gmail.com with ESMTPSA id x13-20020a5d54cd000000b003063db8f45bsm2892812wrv.23.2023.05.30.03.50.56 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 30 May 2023 03:50:56 -0700 (PDT) Message-ID: Date: Tue, 30 May 2023 11:50:56 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.10.0 Subject: Re: RFC: Objdump: Dumping PE specific headers To: Fangrui Song Cc: Jan Beulich , binutils@sourceware.org References: <871qj41iw5.fsf@redhat.com> From: Nick Clifton In-Reply-To: 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.0 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,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: Hi Fangrui, > objdump -p a.exe also dumps the PE header (enabled by default without > selecting a PE triple in --enable-targets=), but in a different > format. True. > I wonder whether the -P header output can be made similar to the > existing output... Either that, or just omitted since it seems wasteful to dump the same information twice. But of course the information would only be shown twice if both the -p and -P options were used. Hmmm. Conformity is probably better. OK - I will try to make the output similar. Cheers Nick