File: 2008-01-25-ByValReadNone.c

package info (click to toggle)
llvm-2.9 2.9%2Bdfsg-7
  • links: PTS, VCS
  • area: main
  • in suites: wheezy
  • size: 69,236 kB
  • sloc: cpp: 439,289; ansic: 16,211; asm: 13,295; sh: 12,912; python: 4,459; ml: 4,274; perl: 2,093; makefile: 1,808; pascal: 1,481; exp: 427; objc: 334; xml: 283; ada: 235; lisp: 187; csh: 117; f90: 36
file content (15 lines) | stat: -rw-r--r-- 726 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
// RUN: %llvmgcc -O3 -S -o - %s | not grep readonly
// RUN: %llvmgcc -O3 -S -o - %s | not grep readnone


// The struct being passed byval means that we cannot mark the
// function readnone.  Readnone would allow stores to the arg to
// be deleted in the caller.  We also don't allow readonly since
// the callee might write to the byval parameter.  The inliner
// would have to assume the worse and introduce an explicit
// temporary when inlining such a function, which is costly for
// the common case in which the byval argument is not written.
struct S { int A[1000]; };
int __attribute__ ((const)) f(struct S x) { x.A[1] = 0; return x.A[0]; }
int g(struct S x) __attribute__ ((pure));
int h(struct S x) { return g(x); }