From: <zac.walker@linaro.org>
To: "'Alan Modra'" <amodra@gmail.com>
Cc: <binutils@sourceware.org>
Subject: RE: [PATCH] GAS fix section alignment for aarch64-pe
Date: Tue, 8 Nov 2022 19:40:28 +0100 [thread overview]
Message-ID: <00e301d8f3a1$9318f440$b94adcc0$@linaro.org> (raw)
In-Reply-To: <Y2mNfaH3Y2mB3nS5@squeak.grove.modra.org>
Hi Alan, Thanks for the feedback.
You are correct - looks like I was over-focused on getting the write method working for various failing tests. Your example is
useful to show missing noops. From what I can see the changes to md_section_align seem necessary for COFF but unrelated to the write
issue. (Assuming the fix is HANDLE_ALIGN specific.)
I will re-work the patch and do more testing. Might take a few days.
Also, I will double check my email settings. Every email client I have tried (except git send-email) seems to break formatting one
way or another.
Cheers,
Zac
-----Original Message-----
From: Alan Modra <amodra@gmail.com>
Sent: 07 November 2022 23:58
To: Zac Walker <zac.walker@linaro.org>
Cc: binutils@sourceware.org
Subject: Re: [PATCH] GAS fix section alignment for aarch64-pe
On Mon, Nov 07, 2022 at 06:53:35PM +0100, Zac Walker via Binutils wrote:
> For the aarch64-pe target, section alignment for various values of
> '.align' causes writing of coff files to fail.
> This patch performs aligning in md_section_align as opposed to the
> original approach in aarch64_handle_align. The change is specific to
> the aarch64-pe target.
This can't be correct since HANDLE_ALIGN and md_section_align perform quite different functions. I don't think you should be
changing aarch64_handle_align. For example:
.text
.p2align 4
nop
.p2align 3
nop
The second p2align needs to continue emitting nops.
(Also, please fix your email client to *not* format lines. Wrapping lines and changing white space breaks patches.)
--
Alan Modra
Australia Development Lab, IBM
prev parent reply other threads:[~2022-11-08 18:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-07 17:53 Zac Walker
2022-11-07 22:58 ` Alan Modra
2022-11-08 18:40 ` zac.walker [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='00e301d8f3a1$9318f440$b94adcc0$@linaro.org' \
--to=zac.walker@linaro.org \
--cc=amodra@gmail.com \
--cc=binutils@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).