[PATCH] D60270: [llvm-objcopy] Add support for Intel HEX input/output format

Jordan Rupprecht via Phabricator via llvm-commits llvm-commits at lists.llvm.org
Tue May 28 14:23:44 PDT 2019

rupprecht accepted this revision.
rupprecht marked an inline comment as done.
rupprecht added a comment.
This revision is now accepted and ready to land.

I ran a few internal tests and this produces identical ihex output for every file I checked! \ o /

Comment at: test/tools/llvm-objcopy/ELF/ihex-writer.test:20
+# RUN: yaml2obj %p/Inputs/ihex-elf-sections2.yaml -o %t-sec2
+# RUN: llvm-objcopy -O ihex --only-section=.text1 %t-sec2 %t-sec2.hex
+# RUN: cat %t-sec2.hex | FileCheck %s --check-prefix=SIGN_EXTENDED
evgeny777 wrote:
> rupprecht wrote:
> > When I run GNU objcopy on this test case, I get an error: `address 0xffffffff80001000 out of range for Intel Hex file`. Maybe we shouldn't be supporting it? Are we able to handle it correctly somehow even though GNU objcopy can't?
> Probably the problem is in the version of objcopy you're using. On my machine 2.30 fails, but works fine
Yep, that was it, I'm no longer seeing it with GNU objcopy from trunk.



More information about the llvm-commits mailing list