File: pr51878_computeAliasing.ll

package info (click to toggle)
swiftlang 6.0.3-2
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid, trixie
  • size: 2,519,992 kB
  • sloc: cpp: 9,107,863; ansic: 2,040,022; asm: 1,135,751; python: 296,500; objc: 82,456; f90: 60,502; lisp: 34,951; pascal: 19,946; sh: 18,133; perl: 7,482; ml: 4,937; javascript: 4,117; makefile: 3,840; awk: 3,535; xml: 914; fortran: 619; cs: 573; ruby: 573
file content (33 lines) | stat: -rw-r--r-- 1,132 bytes parent folder | download | duplicates (15)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
; NOTE: Assertions have been autogenerated by utils/update_llc_test_checks.py
; RUN: llc -O1 -mtriple i686-unknown-linux-gnu -o - %s | FileCheck %s

@foo = global i16 0, align 1
@aliasFoo = alias i16, ptr @foo
@bar = global i16 0, align 1

; This used to miscompile due to not realizing that the store to @aliasFoo
; clobbered @foo (see PR51878).
;
; With some improvements to codegen it should be possible to detect that @foo
; and @aliasFoo are aliases, and that @aliasFoo isn't aliasing with @bar. So
; ideally we would end up with three movw instructions here. Running opt
; before llc on this test case would take care of that, but llc is not smart
; enough to deduce that itself yet.
define i16 @main() {
; CHECK-LABEL: main:
; CHECK:       # %bb.0: # %entry
; CHECK-NEXT:    movw $1, foo
; CHECK-NEXT:    movw $2, bar
; CHECK-NEXT:    movw $4, aliasFoo
; CHECK-NEXT:    movzwl foo, %eax
; CHECK-NEXT:    addw bar, %ax
; CHECK-NEXT:    retl
entry:
  store i16 1, ptr @foo
  store i16 2, ptr @bar
  store i16 4, ptr @aliasFoo
  %foo = load i16, ptr @foo
  %bar = load i16, ptr @bar
  %res = add i16 %foo, %bar
  ret i16 %res
}