File: 2008-07-30-redef-of-bitcasted-decl.c

package info (click to toggle)
llvm-toolchain-7 1%3A7.0.1-8
  • links: PTS, VCS
  • area: main
  • in suites: buster
  • size: 733,456 kB
  • sloc: cpp: 3,776,651; ansic: 633,271; asm: 350,301; python: 142,716; objc: 107,612; sh: 22,626; lisp: 11,056; perl: 7,999; pascal: 6,742; ml: 5,537; awk: 3,536; makefile: 2,557; cs: 2,027; xml: 841; ruby: 156
file content (28 lines) | stat: -rw-r--r-- 761 bytes parent folder | download | duplicates (26)
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
// RUN: %clang_cc1 -emit-llvm -o - %s
// <rdar://problem/6108358>

/* For posterity, the issue here begins initial "char []" decl for
 * s. This is a tentative definition and so a global was being
 * emitted, however the mapping in GlobalDeclMap referred to a bitcast
 * of this global.
 *
 * The problem was that later when the correct definition for s is
 * emitted we were doing a RAUW on the old global which was destroying
 * the bitcast in the GlobalDeclMap (since it cannot be replaced
 * properly), leaving a dangling pointer.
 *
 * The purpose of bar is just to trigger a use of the old decl
 * sometime after the dangling pointer has been introduced.
 */

char s[];

static void bar(void *db) {
  eek(s);
}

char s[5] = "hi";

int foo() {
  bar(0);
}