X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
X-Recipient: djgpp AT delorie DOT com
X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20210112;
        h=to:subject:message-id:date:from:references:in-reply-to:mime-version
         :from:to:cc:subject:date:message-id:reply-to;
        bh=7sgXLZxiLxAlthi3lCUs1msYe4FtX5IewQTG6RfxG4U=;
        b=kXXMJcALibCBFTB23tEdu2fjeLeq4whQSxfD9b0tPQ0znKEj+TWZe1LL1zvOkb48Np
         AAqUVWG+efj28jEAFVxMImXUpsed8YbsqE6jXT1mSn/y/rsxteTu4m9WMgHomMq557S2
         K6uA21O0U9pKeKc/4vwzBmE0tTRR2KOm2bV5+kSMs+ly+TlBDyI+VIY4xB0TCFegnc/e
         cZv54+Px0Zvmu7+CPSbzedhTgqgx74WF3Hw46S+JzFXysFJCXNVOZjxoaniMKbOSHqAe
         mPbd0IRDVDYkA/pmFmIrAXKmSaCruMcdQpxBPT6YwRbY0VGWYaUnGG9damyTgeoWrgsf
         uR+g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20210112;
        h=to:subject:message-id:date:from:references:in-reply-to:mime-version
         :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to;
        bh=7sgXLZxiLxAlthi3lCUs1msYe4FtX5IewQTG6RfxG4U=;
        b=C0/OMAt4NM7onJbjVZHUjItwQDAVfGcp0erP8hnQAVs6M8Cg+3XGC04vDB7m8E+Z0O
         fbAsa+PO2JhquEgyqq+h48+DIBi2TFnKK5pENudO0kj+Ka8/yGvrYnhxcTNvnMfbq2jD
         N2lcFGBmXc4XZROdywWltNgaodw1qaE69VYnjuMwkka2lVK3NVmSECIYCjkhg5I9KgHD
         G2xTx1x+g066YFdjCcdSA8p6AflvVfMgGxbREORH5lpcV2cqZ185lfJxQsPR3VIh70ZX
         R4UWBoAziHyrLQVGxNw7TpD0wI+NfsFYL3C1OIZGxw8Diy0xK2zWdwDo6IyArsyAj531
         sFZg==
X-Gm-Message-State: AO0yUKXlPHCL1H9DNnqE2wE83ztMQ9wPODtKZ+b5pUobOedfK/xF99c/
	Em9rSTIY1e917a3pPi9+HqPugp7RXKrKN7V13O73eq1a
X-Google-Smtp-Source: AK7set8HeQvLBUMGwcvYCLaUjcRMTzm4ttKUuH8tiNaw+YlIzKbUU8x4N6/dElEDuhBwR4BqW/9gffpZLbFtOnx1XV8=
X-Received: by 2002:adf:ef4d:0:b0:2bf:d1b3:cc37 with SMTP id
 c13-20020adfef4d000000b002bfd1b3cc37mr116109wrp.399.1674843637029; Fri, 27
 Jan 2023 10:20:37 -0800 (PST)
MIME-Version: 1.0
In-Reply-To: <CAA2C=vB22rof4HPV_dVPy4tVmsmeDMy4G4r2Vx-_YLwOW6C9ug@mail.gmail.com>
References: <edefcfee-d1ce-415a-8d1d-525a660fb0d5n AT googlegroups DOT com>
 <63a56722-21d6-a368-6400-907f0cf9d01c AT gmail DOT com> <CAA2C=vCduRPA7Ky-kDqs=QtO-qi=DQczM6FMHhB+=Ltof54P=Q AT mail DOT gmail DOT com>
 <c934abb6-c11e-0087-cd32-365d25d3f154 AT gmail DOT com> <CAA2C=vCHMXDD8iewRStieHyTcgjGF3=d29LmMT53vrzGYe+zMQ AT mail DOT gmail DOT com>
 <CACuL_+CZm++qhEr7PedDmQaTxjZu9d-rVSw1bgPeist7XZ+dpQ AT mail DOT gmail DOT com>
 <CAA2C=vDPwv5G9DeFKyKFqt39cDDmO4LmDtbtMyoMdRR2xeEkow AT mail DOT gmail DOT com>
 <3b8f674c-bca3-c679-952e-f8ba5af196e7 AT gmail DOT com> <CAA2C=vBptnTAy2TA-pj5JCbAUJMiXkAAoP_xYFZZJ99iB7v9mQ AT mail DOT gmail DOT com>
 <500850be-fd64-3f82-a1e1-929903084e9b AT gmail DOT com> <CAA2C=vA0zXX3Sb49WBzU5g1-8dmO5G5wrb3uT+tLRq2LB0wu5Q AT mail DOT gmail DOT com>
 <3d9271ae-266d-ee7b-853b-984857ced1c8 AT gmail DOT com> <CAA2C=vD6sZpTicPh0xuJ16r76qBZ5BZro6x=9+=Z+P-0f_eRSA AT mail DOT gmail DOT com>
 <f04cd9db-fe76-219c-bacb-47711df559e2 AT gmail DOT com> <CAA2C=vCv_bpM+iinTcreMJD_gv34Rna3jLspiLFfESFuNxOtoA AT mail DOT gmail DOT com>
 <af7fa08a-b074-0a4c-5e2f-99299940e3cc AT gmail DOT com> <CAA2C=vB22rof4HPV_dVPy4tVmsmeDMy4G4r2Vx-_YLwOW6C9ug AT mail DOT gmail DOT com>
From: "Ozkan Sezer (sezeroz AT gmail DOT com) [via djgpp AT delorie DOT com]" <djgpp AT delorie DOT com>
Date: Fri, 27 Jan 2023 21:20:36 +0300
Message-ID: <CAA2C=vBkA1BdM0EUVdO3DFa6wFaQFL5=T72pjUp11MgOM+RNng@mail.gmail.com>
Subject: Re: DXE3 with std::vector
To: djgpp AT delorie DOT com
Content-Type: text/plain; charset="UTF-8"
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

On 1/27/23, Ozkan Sezer <sezeroz AT gmail DOT com> wrote:
>>>> Thanks.  It builds fine for me with the patched dxe3gen, no warnings,
>>>> both with and without -lgcc.
>>>
>>> Well, it does not for me, which _is_ a problem. My toolchain is based on
>>> gcc-3.4.6 and binutils-2.26.1.
>>
>> If you comment out the line with "remove(TEMP_O_FILE)", then run
>> dxe3gen again, what does "objdump -h dxe_tmp.o" (or -x) show?
>
> Here you go:
> h0.txt and x0.txt are outputs of -h and -x before the patch.
> h1.txt and x1.txt are outputs of -h and -x after the patch.

And, `file` command reports differently for the two versions:

dxe_tmp-0.o: Intel 80386 COFF object file, no line number info, not
stripped, 1 section, symbol offset=0xc104, 433 symbols, 1st section
name ".text"

dxe_tmp-1.o: Intel 80386 COFF executable, no line number info, not
stripped, 3 sections, symbol offset=0xc548, 437 symbols, optional
header size 28