[llvm] Add llvm-extract-bundle-entry to extend llvm-objcopy (PR #169386)

[James Henderson via llvm-commits]

================
@@ -0,0 +1,64 @@
+llvm-extract-bundle-entry - extract an offload bundle entry
+===========================================================
+
+.. program:: llvm-extract-bundle-entry
+
+SYNOPSIS
+--------
+
+:program:`llvm-extract-bundle-entry` [*options*] URI
+
+DESCRIPTION
+-----------
+
+:program:`llvm-extract-offload-entry` is a tool thet takes a URI argument, and 
+generates a code object file by extracting an offload bundle entry specified
+by the URI given.
+
+The URI syntax is defined as:
+ 
+code_object_uri ::== file_uri | memory_uri
+file_uri        ::== file:// extract_file [ range_specifier ]
+memory_uri      ::== memory:// process_id range_specifier
+range_specifier ::== [ # | ? ] offset= number & size= number
+extract_file    ::== URI_ENCODED_OS_FILE_PATH
+process_id      ::== DECIMAL_NUMBER
+number          ::== HEX_NUMBER | DECIMAL_NUMBER | OCTAL_NUMBER
+ 
+The output is always written to a file, whose name is generated from the URI input given.
+
+
+OPTIONS
+----------------------------------
+
+The following options are either agnostic of the file format, or apply to
+multiple file formats.
+
+.. option:: --help, -h
+
+ Print a summary of command line options.
+
+.. option::  -o <file>
+
+ Write output to <file>. Multiple input files cannot be used in combination
+ with -o.
+
+.. option:: --version, -V
+
+ Display the version of the :program:`llvm-extract-bundle-entry` executable.
+
+EXIT STATUS
+-----------
+
+:program:`llvm-extract-bundle-entry` exits with a non-zero exit code if there is an error.
+Otherwise, it exits with code 0.
+
+BUGS
+----
+
+To report bugs, please visit <https://github.com/llvm/llvm-project/labels/tools:llvm-objcopy%2Fextract-offload-entry>.
----------------
jh7370 wrote:

If memory serves me rightly, the existing label is for llvm-objcopy and llvm-strip combined. If you do create a label, I don't think it makes sense to include the llvm-objcopy reference, for two reasons: 1) the implementation of llvm-extract-bundle-entry as an llvm-objcopy extension is largely an implementation detail that users may not know about, and 2) we don't want llvm-objcopy bugs reported to the wrong label.

https://github.com/llvm/llvm-project/pull/169386