From: binutils@emagii.com
To: binutils@sourceware.org
Cc: nickc@redhat.com
Subject: [RFC v0 0/1] Add support for CRC64 generation in linker
Date: Thu, 16 Feb 2023 14:19:04 +0100 [thread overview]
Message-ID: <20230216131905.1012-1-binutils@emagii.com> (raw)
Here is the first draft of introducing CRC64 generation in the linker
So far it
* reserves room for the CRC (8 bytes)
* Declares a symbol ___CRC64___ for the address of the CRC.
* Allows specifying the polynom (ECMA, ISO or your own)
* Allows for inversion in the CRC calculation (CRC64-WE)
* Allows specifying the area that should be checked.
* Declares the symbol "___CRC64_START__" for the beginning
* Declares the symbol "___CRC64_END__" for the end (not included)
* Creates a 2kB table which speeds up the CRC calculation
* Can insert the 2kB table into the .text section
It does not yet calculate the CRC of the specified area.
I need to figure out how to access the section(s) covered
for calculating the CRC (between ___CRC64_START___ and ___CRC64_END___)
and then insert the calculated CRC at ___CRC64___ before
the output is generated.
[PATCH v0 1/1] [RFC] Add support for CRC64 generation in linker
next reply other threads:[~2023-02-16 13:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-16 13:19 binutils [this message]
2023-02-16 13:19 ` [PATCH v0 1/1] [RFC] " binutils
2023-02-16 13:21 ` [RFC v0 0/1] " Ulf Samuelsson
2023-02-16 20:40 binutils
2023-02-16 21:30 ` Fangrui Song
[not found] ` <DS7PR12MB57657A0E46493FAAA203AF77CBA09@DS7PR12MB5765.namprd12.prod.outlook.com>
2023-02-16 22:37 ` Ulf Samuelsson
2023-02-17 11:11 ` Nick Clifton
2023-02-17 12:03 ` Ulf Samuelsson
2023-03-06 7:50 ` Fangrui Song
[not found] ` <DS7PR12MB57654E11983392D5DCBF1D85CBB69@DS7PR12MB5765.namprd12.prod.outlook.com>
2023-03-06 10:00 ` Ulf Samuelsson
2023-02-17 7:53 ` Ulf Samuelsson
2023-02-17 10:55 ` Nick Clifton
[not found] ` <DS7PR12MB5765096101240054A648F8C9CBA09@DS7PR12MB5765.namprd12.prod.outlook.com>
2023-02-17 10:46 ` Nick Clifton
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=20230216131905.1012-1-binutils@emagii.com \
--to=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).