Changes in invalid-alignment.test

536ba637 - [Object] Change ELFObjectFile::getFileFormatName() to use BFD names

Thu, 12 Mar 2020 05:00:19 +0000

[Object] Change ELFObjectFile::getFileFormatName() to use BFD namesFollow-up for D74433What the function returns are almost standard BFD names, except that "ELF" isin uppercase instead of lowercase.This patch changes "ELF" to "elf" and changes ARM/AArch64 to use their BFD names.MIPS and PPC64 have endianness differences as well, but this patch does not intend to address them.Advantages:* llvm-objdump: the "file format " line matches GNU objdump on ARM/AArch64 objects* "file format " line can be extracted and fed into llvm-objcopy -O literally. (https://github.com/ClangBuiltLinux/linux/issues/779 has such a use case)Affected tools: llvm-readobj, llvm-objdump, llvm-dwarfdump, MCJIT (internal implementation detail, not exposed)Reviewed By: jhendersonDifferential Revision: https://reviews.llvm.org/D76046 List of files: /llvm-project-15.0.7/llvm/test/Object/invalid-alignment.test

e4ceb8f4 - [lib/ObjectYAML] - Make `ELFYAML::Relocation::Offset` optional.

Wed, 04 Mar 2020 13:55:15 +0000

[lib/ObjectYAML] - Make `ELFYAML::Relocation::Offset` optional.Currently `yaml2obj` require `Offset` field in a relocation description.There are many cases when `Offset` is insignificant in a context of a test case.Making `Offset` optional allows to simplify our test cases.This is what this patch does.Also, with this patch `obj2yaml` does not dump a zero offset of a relocation.Differential revision: https://reviews.llvm.org/D75608 List of files: /llvm-project-15.0.7/llvm/test/Object/invalid-alignment.test

6371180c - Allow unaligned access to ELF file data structures.

Fri, 12 Jan 2018 22:09:19 +0000

Allow unaligned access to ELF file data structures.The ELF specification says that all ELF data structures are aligned totheir natural alignments both in memory and file. That means when weaccess mmap'ed ELF files, we could assume that all data structures arealigned properly.However, in reality, we assume that the data structures are aligned onlyto two bytes because .a files only guarantee that their member files arealigned to two bytes in archive files. So the data access is alreadyunaligned.This patch relaxes the alignment requirement even more, so that weaccept unaligned access to all ELF data structures.This patch in particular makes lld bug-compatible with icc. Intel Ccompiler doesn't seem to care about data alignment and generates unalignedrelocation sections (https://bugs.llvm.org/show_bug.cgi?id=35854).I also saw another instance of compatibility issues with our internal toolwhich creates unaligned section headers.Because GNU linkers are not picky about alignment, looks like it isnot uncommon that ELF-generating tools create unaligned files.There is a performance penalty with this patch on host machines on whichunaligned access is expensive. x86 and AArch64 are fine. ARMv6 is aproblem, but I don't think using ARMv6 machines as hosts is common, so Ibelieve it's not a real problem.Differential Revision: https://reviews.llvm.org/D41978llvm-svn: 322407 List of files: /llvm-project-15.0.7/llvm/test/Object/invalid-alignment.test

a4e418f7 - Check alignment in getSectionContentsAsArray.

Thu, 30 Nov 2017 00:44:22 +0000

Check alignment in getSectionContentsAsArray.While the ArrayRef can technically have unaligned data, it would beextremely surprising if iterating over it caused undefined behaviorwhen a reference to the underlying type was bound.llvm-svn: 319392 List of files: /llvm-project-15.0.7/llvm/test/Object/invalid-alignment.test