Michael Kruse 58fa3bb63a Do not store scalar accesses in InstructionToAccess ...

At code generation, scalar reads are generated before the other
statement's instructions, respectively scalar writes after them, in
contrast to array accesses which are "executed" with the instructions
they are linked to. Therefore it makes sense to not map the scalar
accesses to a place of execution. Follow-up patches will also remove
some of the directs links from a scalar access to a single instruction,
such that only having array accesses in InstructionToAccess ensures
consistency.

Differential Revision: http://reviews.llvm.org/D13676

llvm-svn: 256298

2015-12-22 23:25:11 +00:00

clang

Disable include sorting by default for Chromium style.

2015-12-22 22:42:56 +00:00

clang-tools-extra

[clang-tidy] Added documentation for modernize-redundant-void-arg

2015-12-22 18:13:00 +00:00

compiler-rt

[cfi] Fix handling of uninstrumented libraries.

2015-12-22 21:40:09 +00:00

debuginfo-tests

…

libclc

AMDGPU: Add aliases for all VI targets

2015-12-15 18:37:04 +00:00

libcxx

Fix type in tuple test. Sorry for the noise

2015-12-18 01:04:36 +00:00

libcxxabi

Fix ARM __cxa_end_cleanup() and gc-sections.

2015-12-22 14:38:30 +00:00

libunwind

…

lld

Split Undefined and UndefinedElf.

2015-12-22 23:00:50 +00:00

lldb

Allow test decorators to use lists (and not_in(list)) for arches

2015-12-22 21:01:21 +00:00

llgo

…

llvm

[unittest] Use Support/thread.h instead of <thread> (second try)

2015-12-22 23:12:41 +00:00

openmp

Prevent monitor thread creation when KMP_BLOCKTIME="infinite"

2015-12-18 23:20:36 +00:00

polly

Do not store scalar accesses in InstructionToAccess

2015-12-22 23:25:11 +00:00

Description

No description provided

intelllvmoneapisycl

5.5 GiB

Languages

LLVM 41.5%

C++ 31.7%

C 13%

Assembly 9.1%

MLIR 1.5%

Other 2.8%