public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Michael Matz <matz@suse.de>
To: binutils@emagii.com
Cc: binutils@sourceware.org, nickc@redhat.com
Subject: Re: [PATCH v1 0/7 SECTOR: Support aligning to flash sector boundary
Date: Fri, 10 Mar 2023 14:13:34 +0000 (UTC)	[thread overview]
Message-ID: <alpine.LSU.2.20.2303101409100.16810@wotan.suse.de> (raw)
In-Reply-To: <20230310000817.751962-1-binutils@emagii.com>

Hello,

On Fri, 10 Mar 2023, Ulf Samuelsson via Binutils wrote:

> This can be used later to align a sector to the flash boundary using the 
> 
> ALIGN_SECTOR command in an output sector.

Please consider implementing new features in terms of existing ones.  For 
instance there is already an 'ALIGN' expression, that either takes dot or 
an arbitrary expression to align, to a certain given value.  Your new 
feature is basically just a special value for such alignment, so it makes 
sense to specify _that_ instead of a new top-level expression.  So, 
consider accepting something like:

   ALIGN(TOSECTOR)
   ALIGN(expr, TOSECTOR)

so that one would write

   . = ALIGN(TOSECTOR)

as usual with alignment of dot.  The 'TOSECTOR' token would be the new 
thing and make it do what you wanted with ALIGN_SECTOR.


Ciao,
Michael.

  parent reply	other threads:[~2023-03-10 14:13 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-10  0:08 binutils
2023-03-10  0:08 ` [PATCH v1 1/7] SECTOR: NEWS binutils
2023-03-10  0:08 ` [PATCH v1 2/7] SECTOR: ld.texi binutils
2023-03-10  0:08 ` [PATCH v1 3/7] SECTOR: ldlex.l binutils
2023-03-10  0:08 ` [PATCH v1 4/7] SECTOR: ldgram.y binutils
2023-03-10  0:08 ` [PATCH v1 5/7] SECTOR: language additions binutils
2023-03-10  0:08 ` [PATCH v1 6/7] SECTOR: add testsuite binutils
2023-03-10  0:08 ` [PATCH v1 7/7] SECTOR: Makefile.* binutils
2023-03-10  3:46 ` [PATCH v1 0/7 SECTOR: Support aligning to flash sector boundary Alan Modra
2023-03-10 14:13 ` Michael Matz [this message]
2023-03-10 17:01   ` Ulf Samuelsson
2023-03-10 17:30     ` Michael Matz
2023-03-10 17:57       ` Ulf Samuelsson
2023-03-13 13:12         ` Michael Matz
2023-03-13 15:29           ` Ulf Samuelsson
2023-03-13 15:54             ` Michael Matz
2023-03-13 17:26               ` Ulf Samuelsson
2023-03-13 17:35                 ` Michael Matz

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=alpine.LSU.2.20.2303101409100.16810@wotan.suse.de \
    --to=matz@suse.de \
    --cc=binutils@emagii.com \
    --cc=binutils@sourceware.org \
    --cc=nickc@redhat.com \
    /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).