[llvm-testresults] buildbot failure in lab.llvm.org on phase1 - sanity

[llvmlab-buildmaster at lab.llvm.org]

The Buildbot has detected a new failure on builder phase1 - sanity while building cfe.
Full details are available at:
 http://lab.llvm.org:8013/builders/phase1%20-%20sanity/builds/5637

Buildbot URL: http://lab.llvm.org:8013/

Buildslave for this Build: macpro1

Build Reason: scheduler
Build Source Stamp: 219961
Blamelist: hans,kcc

BUILD FAILED: failed

sincerely,
 -The Buildbot


================================================================================

CHANGES:
Files:
 include/clang/AST/ASTContext.h
 include/clang/Sema/Sema.h
 lib/CodeGen/CodeGenModule.cpp
 lib/Parse/ParsePragma.cpp
 lib/Sema/SemaAttr.cpp
 lib/Sema/SemaDecl.cpp
 test/CodeGen/sections.c
On: http://10.1.1.2/svn/llvm-project
For: cfe
At: Thu 16 Oct 2014 14:06:33
Changed By: hans
Comments: MS Compat: mark globals emitted in read-only sections const

They cannot be written to, so marking them const makes sense and may improve
optimisation.

As a side-effect, SectionInfos has to be moved from Sema to ASTContext.

It also fixes this problem, that occurs when compiling ATL:

  warning LNK4254: section 'ATL' (C0000040) merged into '.rdata' (40000040) with different attributes

The ATL headers are putting variables in a special section that's marked
read-only. However, Clang currently can't model that read-onlyness in the IR.
But, by making the variables const, the section does become read-only, and
the linker warning is avoided.

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




Files:
 include/clang/AST/Decl.h
 include/clang/Basic/DiagnosticFrontendKinds.td
 include/clang/Basic/DiagnosticGroups.td
 include/clang/Basic/SanitizerBlacklist.h
 lib/AST/Decl.cpp
 lib/AST/RecordLayoutBuilder.cpp
 lib/Basic/SanitizerBlacklist.cpp
 lib/CodeGen/CGClass.cpp
 lib/CodeGen/CodeGenFunction.h
 test/CodeGen/sanitize-address-field-padding.cpp
On: http://10.1.1.2/svn/llvm-project
For: cfe
At: Thu 16 Oct 2014 14:10:35
Changed By: kcc
Comments: Insert poisoned paddings between fields in C++ classes so that AddressSanitizer can find intra-object-overflow bugs

Summary:
The general approach is to add extra paddings after every field
in AST/RecordLayoutBuilder.cpp, then add code to CTORs/DTORs that poisons the paddings
(CodeGen/CGClass.cpp).

Everything is done under the flag -fsanitize-address-field-padding. 
The blacklist file (-fsanitize-blacklist) allows to avoid the transformation 
for given classes or source files. 

See also https://code.google.com/p/address-sanitizer/wiki/IntraObjectOverflow

Test Plan: run SPEC2006 and some of the Chromium tests with  -fsanitize-address-field-padding

Reviewers: samsonov, rnk, rsmith

Reviewed By: rsmith

Subscribers: majnemer, cfe-commits

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




LOGS: