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

package info (click to toggle)
llvm-toolchain-14 1%3A14.0.6-16
  • links: PTS, VCS
  • area: main
  • in suites: sid
  • size: 1,496,368 kB
  • sloc: cpp: 5,593,980; ansic: 986,873; asm: 585,869; python: 184,223; objc: 72,530; lisp: 31,119; f90: 27,793; javascript: 9,780; pascal: 9,762; sh: 9,482; perl: 7,468; ml: 5,432; awk: 3,523; makefile: 2,547; xml: 953; cs: 573; fortran: 567
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);
}