[clang] [llvm] [clang-tools-extra] [llvm-objcopy] Add --gap-fill and --pad-to options (PR #65815)

Fangrui Song via llvm-commits llvm-commits at lists.llvm.org
Wed Dec 6 22:00:39 PST 2023


================
@@ -738,6 +739,36 @@ objcopy::parseObjcopyOptions(ArrayRef<const char *> RawArgsArr,
   if (auto Arg = InputArgs.getLastArg(OBJCOPY_extract_partition))
     Config.ExtractPartition = Arg->getValue();
 
+  if (const auto *A = InputArgs.getLastArg(OBJCOPY_gap_fill)) {
+    if (Config.OutputFormat != FileFormat::Binary)
+      return createStringError(
+          errc::invalid_argument,
+          "'--gap-fill' is only supported for binary output");
+    ErrorOr<uint64_t> Val = getAsInteger<uint64_t>(A->getValue());
+    if (!Val)
+      return createStringError(Val.getError(), "--gap-fill: bad number: %s",
+                               A->getValue());
+    uint8_t ByteVal = Val.get();
+    if (ByteVal != Val.get())
+      if (Error E = reportWarning(llvm::createStringError(
----------------
MaskRay wrote:

I see that objcopy uses a warning, but an error seems more appropriate and the difference between warning/error should not matter for the user.

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


More information about the llvm-commits mailing list