[LLVMbugs] [Bug 10808] New: During testing processes clang.exe*32 occupy all CPU time and block execution
bugzilla-daemon at llvm.org
bugzilla-daemon at llvm.org
Mon Aug 29 15:40:44 PDT 2011
http://llvm.org/bugs/show_bug.cgi?id=10808
Summary: During testing processes clang.exe*32 occupy all CPU
time and block execution
Product: clang
Version: unspecified
Platform: PC
OS/Version: Windows NT
Status: NEW
Severity: normal
Priority: P
Component: -New Bugs
AssignedTo: unassignedclangbugs at nondot.org
ReportedBy: clang.builder at gmail.com
CC: llvmbugs at cs.uiuc.edu
Native mingw32 two-stage clang build has issues with both llvm and clang tests
performed on second stage.
Seems four processes clang.exe*32 occupy all CPU time and block execution.
Description of the build:
Native two-stage clang build, both stage use equal clang configuration:
--prefix=private_install_dir \
--build=i686-pc-mingw32 --host=i686-pc-mingw32 \
--target=i686-pc-mingw32 --disable-bindings \
--without-llvmgcc --without-llvmgxx \
--enable-optimized --enable-assertions
Build machine information:
Windows 7 Professional x64(English) Service Pack1
Intel Xeon CPU W3530 @ 2.80 GHz, 12GB of RAM
g++.exe (GCC) 4.5.2
GNU Binutils 2.21.53.20110804
This is perl, v5.8.8 built for msys-64int
Python 2.6.6
cmake version 2.8.4
clang revisions that was tested:
138687
138579
138443
138298
--
Configure bugmail: http://llvm.org/bugs/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
More information about the llvm-bugs
mailing list