llvm-project/llvm
Ulrich Weigand 994f49ed79 [PowerPC] Fix processing of ha16/lo16 fixups
The current PowerPC MC back end distinguishes between fixup_ppc_ha16
and fixup_ppc_lo16, which are determined by the instruction the fixup
applies to, and uses this distinction to decide whether a fixup ought
to resolve to the high or the low part of a symbol address.

This isn't quite correct, however.  It is valid -if unusual- assembler
to use, e.g.
  li 1, symbol@ha
or
  lis 1, symbol@l
Whether the high or the low part of the address is used depends solely
on the @ suffix, not on the instruction.

In addition, both
  li 1, symbol
and
  lis 1, symbol
are valid, assuming the symbol address fits into 16 bits; again, both
will then refer to the actual symbol value (so li will load the value
itself, while lis will load the value shifted by 16).


To fix this, two places need to be adapted.  If the fixup cannot be
resolved at assembler time, a relocation needs to be emitted via
PPCELFObjectWriter::getRelocType.  This routine already looks at
the VK_ type to determine the relocation.  The only problem is that
will reject any _LO modifier in a ha16 fixup and vice versa.  This
is simply incorrect; any of those modifiers ought to be accepted
for either fixup type.

If the fixup *can* be resolved at assembler time, adjustFixupValue
currently selects the high bits of the symbol value if the fixup
type is ha16.  Again, this is incorrect; see the above example
  lis 1, symbol

Now, in theory we'd have to respect a VK_ modifier here.  However,
in fact common code never even attempts to resolve symbol references
using any nontrivial VK_ modifier at assembler time; it will always
fall back to emitting a reloc and letting the linker handle it.

If this ever changes, presumably there'd have to be a target callback
to resolve VK_ modifiers.  We'd then have to handle @ha etc. there.

llvm-svn: 182091
2013-05-17 12:36:29 +00:00
..
autoconf We're in 3.4 land now. 2013-05-07 20:31:28 +00:00
bindings We're in 3.4 land now. 2013-05-07 20:31:28 +00:00
cmake [SystemZ] Add configure bits 2013-05-06 16:22:34 +00:00
docs Add Jade to the list of external projects using LLVM in the release notes. 2013-05-15 14:05:01 +00:00
examples ExceptionDemo: Corresponding to r181820, SectionMemoryManager should belong to RTDyldMemoryManager. 2013-05-14 23:05:00 +00:00
include Fix a typo (ouput => output) 2013-05-17 12:31:43 +00:00
lib [PowerPC] Fix processing of ha16/lo16 fixups 2013-05-17 12:36:29 +00:00
projects [SystemZ] Add to --enable-targets=all 2013-05-06 16:23:07 +00:00
runtime Remove GCDAProfiling.c. This copy is old, the copy in compiler-rt is newer and 2013-03-07 02:03:08 +00:00
test [PowerPC] Fix processing of ha16/lo16 fixups 2013-05-17 12:36:29 +00:00
tools Minor changes to the MCJITTest unittests to use the correct API for finalizing 2013-05-17 10:01:46 +00:00
unittests Minor changes to the MCJITTest unittests to use the correct API for finalizing 2013-05-17 10:01:46 +00:00
utils Add TargetRegisterInfo::getCoveringLanes(). 2013-05-16 18:03:08 +00:00
.arcconfig
.gitignore
CMakeLists.txt Change version to 3.4 in the cmake build too. 2013-05-07 20:44:22 +00:00
CODE_OWNERS.TXT Add myself as SystemZ code owner 2013-05-08 14:41:29 +00:00
CREDITS.TXT Test commit. 2013-05-09 12:32:36 +00:00
LICENSE.TXT Add LICENSE.TXT covering contributions made by ARM. 2013-01-07 10:04:49 +00:00
LLVMBuild.txt
Makefile Improved svn repo searching for 'make update' 2013-01-28 03:19:57 +00:00
Makefile.common
Makefile.config.in Add basic zlib support to LLVM. This would allow to use compression/uncompression in selected LLVM tools. 2013-04-23 08:28:39 +00:00
Makefile.rules Revert previous patch, it's actually on under Wall. 2013-05-14 21:52:01 +00:00
README.txt test 2013-04-17 05:34:03 +00:00
configure We're in 3.4 land now. 2013-05-07 20:31:28 +00:00
llvm.spec.in

README.txt

Low Level Virtual Machine (LLVM)
================================

This directory and its subdirectories contain source code for the Low Level
Virtual Machine, a toolkit for the construction of highly optimized compilers,
optimizers, and runtime environments.

LLVM is open source software. You may freely distribute it under the terms of
the license agreement found in LICENSE.txt.

Please see the documentation provided in docs/ for further
assistance with LLVM, and in particular docs/GettingStarted.rst for getting
started with LLVM and docs/README.txt for an overview of LLVM's
documentation setup.

If you're writing a package for LLVM, see docs/Packaging.rst for our
suggestions.