From: Florian Weimer <fweimer@redhat.com>
To: Fangrui Song <i@maskray.me>
Cc: luca.boccassi@gmail.com, binutils@sourceware.org
Subject: Re: [PATCH] ld: add --package-metadata
Date: Tue, 17 May 2022 08:03:33 +0200 [thread overview]
Message-ID: <87o7zwwv9m.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <20220516164003.iivw6lthknhvce42@gmail.com> (Fangrui Song's message of "Mon, 16 May 2022 09:40:03 -0700")
* Fangrui Song:
> Both the "FDO" and the json dependency make me concerned -
> if a linker script approach works quite well, why bother with a new
> linker option with a very specific application?
The linker script does not work all that well because it requires that
the script is materialized to disk somewhere, and that path needs to
show up in the build flags. If the build flags are stored beyond the
build for future use, this makes them invalid because the path will
typically be gone by the time the stored flags are used.
Thanks,
Florian
next prev parent reply other threads:[~2022-05-17 6:03 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-15 19:18 luca.boccassi
2022-05-16 16:40 ` Fangrui Song
2022-05-17 6:03 ` Florian Weimer [this message]
2022-05-17 14:44 ` Luca Boccassi
2022-05-25 6:56 ` Fangrui Song
2022-05-25 7:53 ` Florian Weimer
2022-05-23 11:26 ` Luca Boccassi
2022-05-24 9:34 ` Jose E. Marchesi
2022-05-24 11:26 ` Luca Boccassi
2022-05-24 16:23 ` Nick Clifton
2022-05-24 18:38 ` Luca Boccassi
2022-05-25 8:45 ` Florian Weimer
2022-05-25 13:53 ` Luca Boccassi
2022-05-30 14:08 ` Florian Weimer
2022-05-24 16:28 ` Nick Clifton
2022-05-24 21:15 ` [PATCH v2] " luca.boccassi
2022-05-25 4:30 ` Alan Modra
2022-05-25 6:02 ` Alan Modra
2022-05-25 13:42 ` Luca Boccassi
2022-05-25 13:41 ` [PATCH v3] " luca.boccassi
2022-05-26 3:55 ` Alan Modra
2022-05-26 10:46 ` Luca Boccassi
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=87o7zwwv9m.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=binutils@sourceware.org \
--cc=i@maskray.me \
--cc=luca.boccassi@gmail.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).