public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Christophe Lyon <christophe.lyon@linaro.org>
To: binutils <binutils@sourceware.org>
Subject: [PATCH] Add support for non-contiguous memory regions
Date: Fri, 14 Feb 2020 12:34:00 -0000	[thread overview]
Message-ID: <CAKdteOZDKNpW2iRWpJ9eykTT+Yb-n9mVDed=YO4+vZg+hKSPOA@mail.gmail.com> (raw)

Hi,

This is a follow-up to
https://sourceware.org/ml/binutils/2019-11/msg00402.html
https://sourceware.org/ml/binutils/2020-01/msg00064.html
and
https://sourceware.org/ml/binutils/2020-02/msg00037.html

Changes between v3 and v4:
* I ran the tests on more targets (those that have xxx_build_one_stub:
avr csky hppa mc68ch11 metag nios2 ppc aarch64 m68hc11 m68hc12)
* this made me update the generic test (match addresses more lazily to
cope with 64 bits outputs, ignore symbol table whose order depends on
the target), and skip it for the targets that don't support
-mlittle-endian. Is there a more generic way of doing this? (for sure,
there are other targets that don't support that option but that I
haven't tested)
* I updated xxx_build_one_stub similarly to what I needed for arm,
although I didn't write specific tests

The changes between v2 and v3:
* added some doc/NEWS
* fixed bugs detected when running the testsuite with the option
activated by default. In particular, I've noticed and documented the
incompatibility with INSERT (or rather, it's likely to cause problems,
but depends on the actual linker scripts contents), because my new
option breaks the assumption of the parsing & processing order assumed
by INSERT.
* added new option --enable-non-contiguous-regions-warnings which
activates some warnings to help understand why the behaviour changes
in some cases

There are 4 patches, to hopefully make review/comments easier; I can
squash them at commit time if this is preferable.
* patch1: is the main (code) patch
* patch2: generic test
* patch3: arm tests
* patch4: powerpc test

OK?

Thanks,

Christophe

             reply	other threads:[~2020-02-14 12:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-14 12:34 Christophe Lyon [this message]
2020-02-14 13:02 ` Tamar Christina
2020-02-14 13:54   ` Christophe Lyon
2020-02-19  7:19     ` Alan Modra
2020-02-19 12:28       ` Christophe Lyon
2020-02-19 22:23         ` Alan Modra
2020-02-20  4:37           ` Christophe Lyon
2020-02-20  8:15             ` Alan Modra
2020-02-20  9:00               ` Christophe Lyon
2020-02-28 17:31                 ` Christophe Lyon
2020-03-09 13:10                   ` Christophe Lyon
2020-03-13 14:21                     ` Nick Clifton
2020-03-13 14:46                       ` Christophe Lyon
2020-06-02 12:49                         ` Alexander Fedotov
2020-06-03 12:48                           ` Christophe Lyon

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='CAKdteOZDKNpW2iRWpJ9eykTT+Yb-n9mVDed=YO4+vZg+hKSPOA@mail.gmail.com' \
    --to=christophe.lyon@linaro.org \
    --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).