1; RUN: llvm-link %s %S/Inputs/alias.ll -S -o - | FileCheck --check-prefix=C1 %s 2; RUN: llvm-link %S/Inputs/alias.ll %s -S -o - | FileCheck --check-prefix=C2 %s 3 4; FIXME: 5; The C1 direction is incorrect. 6; When moving an alias to an existing module and we want to discard the aliasee 7; (the C2 case), the IRMover knows to copy the aliasee as internal. 8; When moving a replacement to an aliasee to a module that has an alias (C1), 9; a replace all uses with blindly changes the alias. 10; The C1 case doesn't happen when using a system linker with a plugin because 11; the linker does full symbol resolution first. 12; Given that this is a problem only with llvm-link and its 1 module at a time 13; linking, it should probably learn to changes the aliases in the destination 14; before using the IRMover. 15 16@foo = weak global i32 0 17; C1-DAG: @foo = alias i32, i32* @zed 18; C2-DAG: @foo = alias i32, i32* @zed 19 20@bar = alias i32, i32* @foo 21; C1-DAG: @bar = alias i32, i32* @foo 22 23; C2-DAG: @foo.1 = internal global i32 0 24; C2-DAG: @bar = alias i32, i32* @foo.1 25 26@foo2 = weak global i32 0 27; C1-DAG: @foo2 = alias i16, bitcast (i32* @zed to i16*) 28; C2-DAG: @foo2 = alias i16, bitcast (i32* @zed to i16*) 29 30@bar2 = alias i32, i32* @foo2 31; C1-DAG: @bar2 = alias i32, bitcast (i16* @foo2 to i32*) 32 33; C2-DAG: @foo2.2 = internal global i32 0 34; C2-DAG: @bar2 = alias i32, i32* @foo2.2 35 36; C1-DAG: @zed = global i32 42 37; C2-DAG: @zed = global i32 42 38