date:20170316

[llvm-bugs] [Bug 32313] lib/xray/tests/unit/xray_fdr_log_printer_tool.cc should include

2017-03-16 Thread via llvm-bugs

https://bugs.llvm.org/show_bug.cgi?id=32313

Dean Michael Berris  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|ASSIGNED|RESOLVED

--- Comment #2 from Dean Michael Berris  ---
Should be fixed in r298037 (https://reviews.llvm.org/rL298037)

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

[llvm-bugs] [Bug 32322] New: Apply to 4.0 release branch

2017-03-16 Thread via llvm-bugs

http://bugs.llvm.org/show_bug.cgi?id=32322

Bug ID: 32322
   Summary: Apply to 4.0 release branch
   Product: clang
   Version: 4.0
  Hardware: All
OS: OpenBSD
Status: NEW
  Severity: normal
  Priority: P
 Component: Driver
  Assignee: unassignedclangb...@nondot.org
  Reporter: b...@comstyle.com
CC: llvm-bugs@lists.llvm.org

To backport the minimal changes for proper 64-bit / 32-bit ARM support for
OpenBSD.

r295786 for 64-bit ARM. r296430 (clang) and r296493 (llvm) for 32-bit ARM.

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

[llvm-bugs] [Bug 32321] New: Apply r 295614 to 4.0 release branch

2017-03-16 Thread via llvm-bugs

http://bugs.llvm.org/show_bug.cgi?id=32321

Bug ID: 32321
   Summary: Apply r 295614 to 4.0 release branch
   Product: clang
   Version: 4.0
  Hardware: All
OS: OpenBSD
Status: NEW
  Severity: normal
  Priority: P
 Component: Driver
  Assignee: unassignedclangb...@nondot.org
  Reporter: b...@comstyle.com
CC: llvm-bugs@lists.llvm.org

Fixes __float128 support on OpenBSD/X86.

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

[llvm-bugs] [Bug 32320] New: [ppc] crandc of two cmps is much slower than two cmp/br

2017-03-16 Thread via llvm-bugs

https://bugs.llvm.org/show_bug.cgi?id=32320

Bug ID: 32320
   Summary: [ppc] crandc of two cmps is much slower than two
cmp/br
   Product: libraries
   Version: trunk
  Hardware: PC
OS: All
Status: NEW
  Severity: enhancement
  Priority: P
 Component: Backend: PowerPC
  Assignee: unassignedb...@nondot.org
  Reporter: car...@google.com
CC: llvm-bugs@lists.llvm.org

Compile following source code with options -mvsx -mcpu=power8 -O2


struct S{
  struct S* next;
};

struct S* foo(struct S* p, struct S* e)
{
  struct S* n;
  for (; (n = p->next) !=0 && n < e; p = n);
  return n;
}

LLVM generates:

foo:# @foo
.Lfunc_begin0:
# BB#0: # %entry
.p2align5
.LBB0_1:# %for.cond
# =>This Inner Loop Header: Depth=1
ld 3, 0(3)
cmpdi3, 0// (n = p->next) !=0
cmpld 1, 3, 4// n < e
crandc 20, 4, 2  //&&
bc 12, 20, .LBB0_1
# BB#2: # %for.end
blr


It uses crandc to combine the previous two cmp results, and then branch. It is
much slower than 2 simple cmp/br on power8, because crandc has data dependence
on previous cmp instructions, they have 5 cycles latency. In an internal
bigtable benchmark, the crandc version has only half of the performance of the
simple cmp/br version, with a similar code pattern.

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

[llvm-bugs] [Bug 32288] Unnecessary narrowing of register reference in DW_AT_location for int parameter

2017-03-16 Thread via llvm-bugs

http://bugs.llvm.org/show_bug.cgi?id=32288

Adrian Prantl  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|ASSIGNED|RESOLVED

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

[llvm-bugs] [Bug 31616] undefined reference to pthread_create

2017-03-16 Thread via llvm-bugs

https://bugs.llvm.org/show_bug.cgi?id=31616

Laurent Carlier  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

--- Comment #1 from Laurent Carlier  ---
Seems fixed now, closing

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

[llvm-bugs] [Bug 32319] New: .gdb_index is broken/incomplete

2017-03-16 Thread via llvm-bugs

http://bugs.llvm.org/show_bug.cgi?id=32319

Bug ID: 32319
   Summary: .gdb_index is broken/incomplete
   Product: lld
   Version: unspecified
  Hardware: PC
OS: All
Status: NEW
  Severity: enhancement
  Priority: P
 Component: ELF
  Assignee: unassignedb...@nondot.org
  Reporter: r...@google.com
CC: llvm-bugs@lists.llvm.org

Reported by David Blaikie.

He is using GDB 7.9 (a google internal build) to debug LLVM's 'llc' binary on
an assert-failure. A few of the later frames (endFunction,
runOnMachineFunction, runOnFunction) doesn't have source information.

#9  0x037d9278 in llvm::DwarfCompileUnit::constructVariableDIEImpl
(this=0x540a390, DV=..., Abstract=false) at
/usr/local/google/home/blaikie/dev/llvm/src/lib/CodeGen/AsmPrinter/DwarfCompileUnit.cpp:543
(gdb)
#10 0x037d8c6c in llvm::DwarfCompileUnit::constructVariableDIE
(this=0x540a390, DV=..., Abstract=false) at
/usr/local/google/home/blaikie/dev/llvm/src/lib/CodeGen/AsmPrinter/DwarfCompileUnit.cpp:479
(gdb)
#11 0x037d97b6 in llvm::DwarfCompileUnit::constructVariableDIE
(this=0x540a390, DV=..., Scope=..., ObjectPointer=@0x7fffb488: 0x0) at
/usr/local/google/home/blaikie/dev/llvm/src/lib/CodeGen/AsmPrinter/DwarfCompileUnit.cpp:560
(gdb)
#12 0x037d8231 in llvm::DwarfCompileUnit::createScopeChildrenDIE
(this=0x540a390, Scope=0x5482df0, Children=llvm::SmallVector of length 0,
capacity 8, ChildScopeCount=0x0) at
/usr/local/google/home/blaikie/dev/llvm/src/lib/CodeGen/AsmPrinter/DwarfCompileUnit.cpp:572
(gdb)
#13 0x037d99b7 in llvm::DwarfCompileUnit::createAndAddScopeChildren
(this=0x540a390, Scope=0x5482df0, ScopeDIE=...) at
/usr/local/google/home/blaikie/dev/llvm/src/lib/CodeGen/AsmPrinter/DwarfCompileUnit.cpp:614
(gdb)
#14 0x037d98a4 in llvm::DwarfCompileUnit::constructSubprogramScopeDIE
(this=0x540a390, Sub=0x53cd568, Scope=0x5482df0) at
/usr/local/google/home/blaikie/dev/llvm/src/lib/CodeGen/AsmPrinter/DwarfCompileUnit.cpp:594
(gdb) 
#15 0x0376a087 in llvm::DwarfDebug::endFunctionImpl (this=0x54082c0,
MF=0x5439b60) at
/usr/local/google/home/blaikie/dev/llvm/src/lib/CodeGen/AsmPrinter/DwarfDebug.cpp:1240
(gdb) 
#16 0x037c93c9 in
llvm::DebugHandlerBase::endFunction(llvm::MachineFunction const*) ()
(gdb) 
#17 0x03733d6a in llvm::AsmPrinter::EmitFunctionBody (this=0x53fa9a0)
at
/usr/local/google/home/blaikie/dev/llvm/src/lib/CodeGen/AsmPrinter/AsmPrinter.cpp:1083
(gdb) 
#18 0x03107e61 in
llvm::X86AsmPrinter::runOnMachineFunction(llvm::MachineFunction&) ()
(gdb) 
#19 0x03a263b1 in
llvm::MachineFunctionPass::runOnFunction(llvm::Function&) ()

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

[llvm-bugs] [Bug 31753] llvm/lib/CodeGen/MachinePipeliner.cpp: 2 * pointless tests

2017-03-16 Thread via llvm-bugs

https://bugs.llvm.org/show_bug.cgi?id=31753

Simon Pilgrim  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|NEW |RESOLVED

--- Comment #2 from Simon Pilgrim  ---
Fixed at rL297976

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

[llvm-bugs] [Bug 30996] [META] PVS Studio Warnings

2017-03-16 Thread via llvm-bugs

https://bugs.llvm.org/show_bug.cgi?id=30996
Bug 30996 depends on bug 31753, which changed state.

Bug 31753 Summary: llvm/lib/CodeGen/MachinePipeliner.cpp: 2 * pointless tests
https://bugs.llvm.org/show_bug.cgi?id=31753

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

[llvm-bugs] [Bug 32318] New: -ast-dump-all crashes on empty files

2017-03-16 Thread via llvm-bugs

https://bugs.llvm.org/show_bug.cgi?id=32318

Bug ID: 32318
   Summary: -ast-dump-all crashes on empty files
   Product: clang
   Version: trunk
  Hardware: PC
OS: Windows NT
Status: NEW
  Severity: enhancement
  Priority: P
 Component: Frontend
  Assignee: unassignedclangb...@nondot.org
  Reporter: aa...@aaronballman.com
CC: llvm-bugs@lists.llvm.org

If the file contains no declarations or lookups, then calling -ast-dump-all
asserts.

What's interesting is that a regular -ast-dump has content.

D:\llvm\build\Debug\bin>touch test.c
D:\llvm\build\Debug\bin>clang -cc1 -ast-dump test.c
TranslationUnitDecl 0x2225c9eead0 <> 
|-TypedefDecl 0x2225c9ef020 <>  implicit __int128_t
'__int128'
| `-BuiltinType 0x2225c9eed40 '__int128'
|-TypedefDecl 0x2225c9ef088 <>  implicit
__uint128_t 'unsigned __int128'
| `-BuiltinType 0x2225c9eed60 'unsigned __int128'
|-TypedefDecl 0x2225c9ef378 <>  implicit
__NSConstantString 'struct __NSConstantString_tag'
| `-RecordType 0x2225c9ef160 'struct __NSConstantString_tag'
|   `-Record 0x2225c9ef0d8 '__NSConstantString_tag'
|-TypedefDecl 0x2225c9ef410 <>  implicit
__builtin_ms_va_list 'char *'
| `-PointerType 0x2225c9ef3d0 'char *'
|   `-BuiltinType 0x2225c9eeb60 'char'
`-TypedefDecl 0x2225c9ef478 <>  implicit
__builtin_va_list 'char *'
  `-PointerType 0x2225c9ef3d0 'char *'
`-BuiltinType 0x2225c9eeb60 'char'

D:\llvm\build\Debug\bin>clang -cc1 -ast-dump-all test.c
Assertion failed: (DumpDecls || DumpLookups) && "nothing to dump", file
D:\llvm\llvm\tools\clang\lib\Frontend\ASTConsumers.cpp, line 145
Wrote crash dump file
"C:\Users\aballman\AppData\Local\Temp\clang.exe-abbfb1.dmp"
#0 0x7ff7a30d2f8c HandleAbort
d:\llvm\llvm\lib\support\windows\signals.inc:405:0
#1 0x7ff93b431c81 (C:\Windows\SYSTEM32\ucrtbased.dll+0x81c81)
#2 0x7ff93b4338a9 (C:\Windows\SYSTEM32\ucrtbased.dll+0x838a9)
#3 0x7ff93b439495 (C:\Windows\SYSTEM32\ucrtbased.dll+0x89495)
#4 0x7ff93b438ff7 (C:\Windows\SYSTEM32\ucrtbased.dll+0x88ff7)
#5 0x7ff93b437061 (C:\Windows\SYSTEM32\ucrtbased.dll+0x87061)
#6 0x7ff93b439a3f (C:\Windows\SYSTEM32\ucrtbased.dll+0x89a3f)
#7 0x7ff7a40471d8 clang::CreateASTDumper(class
llvm::StringRef,bool,bool,bool)
d:\llvm\llvm\tools\clang\lib\frontend\astconsumers.cpp:145:0
#8 0x7ff7a3fc19a2 clang::ASTDumpAction::CreateASTConsumer(class
clang::CompilerInstance &,class llvm::StringRef)
d:\llvm\llvm\tools\clang\lib\frontend\frontendactions.cpp:58:0
#9 0x7ff7a3fb65c5 clang::FrontendAction::CreateWrappedASTConsumer(class
clang::CompilerInstance &,class llvm::StringRef)
d:\llvm\llvm\tools\clang\lib\frontend\frontendaction.cpp:143:0
#10 0x7ff7a3fb7bad clang::FrontendAction::BeginSourceFile(class
clang::CompilerInstance &,class clang::FrontendInputFile const &)
d:\llvm\llvm\tools\clang\lib\frontend\frontendaction.cpp:387:0
#11 0x7ff7a3f24aec clang::CompilerInstance::ExecuteAction(class
clang::FrontendAction &)
d:\llvm\llvm\tools\clang\lib\frontend\compilerinstance.cpp:949:0
#12 0x7ff7a415e206 clang::ExecuteCompilerInvocation(class
clang::CompilerInstance *)
d:\llvm\llvm\tools\clang\lib\frontendtool\executecompilerinvocation.cpp:249:0
#13 0x7ff7a0136194 cc1_main(class llvm::ArrayRef,char const
*,void *) d:\llvm\llvm\tools\clang\tools\driver\cc1_main.cpp:221:0
#14 0x7ff7a011a4dd ExecuteCC1Tool
d:\llvm\llvm\tools\clang\tools\driver\driver.cpp:299:0
#15 0x7ff7a011ad8c main
d:\llvm\llvm\tools\clang\tools\driver\driver.cpp:380:0
#16 0x7ff7a7bdf194 invoke_main
f:\dd\vctools\crt\vcstartup\src\startup\exe_common.inl:65:0
#17 0x7ff7a7bdf057 __scrt_common_main_seh
f:\dd\vctools\crt\vcstartup\src\startup\exe_common.inl:253:0
#18 0x7ff7a7bdef1e __scrt_common_main
f:\dd\vctools\crt\vcstartup\src\startup\exe_common.inl:296:0
#19 0x7ff7a7bdf1b9 mainCRTStartup
f:\dd\vctools\crt\vcstartup\src\startup\exe_main.cpp:17:0
#20 0x7ff968d88364 (C:\Windows\System32\KERNEL32.DLL+0x8364)
#21 0x7ff96b8570d1 (C:\Windows\SYSTEM32\ntdll.dll+0x670d1)

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

[llvm-bugs] [Bug 32249] PVS-Studio: Use of Uninitialized Variable (CWE-457)

2017-03-16 Thread via llvm-bugs

https://bugs.llvm.org/show_bug.cgi?id=32249

Zachary Turner  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

--- Comment #3 from Zachary Turner  ---
The patch looks fine, but I think I can make it a bit more concise.  We should
be able to replace this entire else block with just 

StringRef N(Name);
N = N.take_front(BytesLeft-1);
error(IO.mapStringZ(N));

I looked into why this wasn't caught by msan, and it's because this is a
hard-to-encounter edge case that doesn't have test coverage.  I've been
improving the testability of this code for a while now, so we should be at the
point fairly soon where I can get test coverage for these weird edge cases.

I'm going to close this as fixed and submit the patch shortly.  Thanks
Svyatoslav!

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

[llvm-bugs] [Bug 30996] [META] PVS Studio Warnings

2017-03-16 Thread via llvm-bugs

https://bugs.llvm.org/show_bug.cgi?id=30996
Bug 30996 depends on bug 32249, which changed state.

Bug 32249 Summary: PVS-Studio: Use of Uninitialized Variable (CWE-457)
https://bugs.llvm.org/show_bug.cgi?id=32249

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

[llvm-bugs] [Bug 32317] New: Loop vectorizer miscompile resulting in additional loop iteration

2017-03-16 Thread via llvm-bugs

https://bugs.llvm.org/show_bug.cgi?id=32317

Bug ID: 32317
   Summary: Loop vectorizer miscompile resulting in additional
loop iteration
   Product: libraries
   Version: trunk
  Hardware: PC
OS: All
Status: NEW
  Severity: enhancement
  Priority: P
 Component: Loop Optimizer
  Assignee: unassignedb...@nondot.org
  Reporter: i...@azulsystems.com
CC: llvm-bugs@lists.llvm.org

Attached test case produces incorrect result when run -force-vector-width=2:

$ lli test.ll
89.00

$ opt -S -O3 -force-vector-width=2 test.ll > test.opt.ll
$ lli test.opt.ll
90.00

$ opt -S -O3 -force-vector-width=4 test.ll > test.opt.ll
$ lli test.opt.ll
89.00

Looking at the output I believe that vectorizer incorrectly calculates
resulting loop value for the fFld:

vector.body:  
  %index = phi i64 [ 0, %vector.ph ], [ %index.next, %vector.body ]
  %vec.ind = phi <2 x i64> [ , %vector.ph ], [ %vec.ind.next,
%vector.body ]
  %vector.recur = phi <2 x i64> [ %vector.recur.init, %vector.ph ], [ %20,
%vector.body ]
  %20 = add nsw <2 x i64> %vec.ind, %broadcast.splat
  %21 = shufflevector <2 x i64> %vector.recur, <2 x i64> %20, <2 x i32> 
  %index.next = add i64 %index, 2
  %vec.ind.next = add <2 x i64> %vec.ind, 
  %22 = icmp eq i64 %index.next, 86
  br i1 %22, label %middle.block, label %vector.body, !llvm.loop !52

middle.block: ; preds = %vector.body
  %cmp.n = icmp eq i64 86, 86
  %vector.recur.extract = extractelement <2 x i64> %20, i32 1
  br i1 %cmp.n, label %bci_64, label %scalar.ph

If in the "%vector.recur.extract" instead of the "%20" we would have used
"%vec.ind" - result would have been correct.

Attached .ll test case and roughly equivalent c code.

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

[llvm-bugs] [Bug 32316] New: Assertion `N1.getValueType() == N2.getValueType() && N1.getValueType() == VT && "Binary operator types must match!"' failed with -O1 -march=skx

2017-03-16 Thread via llvm-bugs

https://bugs.llvm.org/show_bug.cgi?id=32316

Bug ID: 32316
   Summary: Assertion `N1.getValueType() == N2.getValueType() &&
N1.getValueType() == VT && "Binary operator types must
match!"' failed with -O1 -march=skx
   Product: new-bugs
   Version: trunk
  Hardware: PC
OS: Linux
Status: NEW
  Severity: enhancement
  Priority: P
 Component: new bugs
  Assignee: unassignedb...@nondot.org
  Reporter: vsevolod.livins...@frtk.ru
CC: llvm-bugs@lists.llvm.org

Created attachment 18115
  --> https://bugs.llvm.org/attachment.cgi?id=18115=edit
Reproducer.

Clang fails with assertion with -O3 -march=skx option.

Reproducer:
unsigned char a, b, c, d;

void foo() {
  d = (!b > c) + (a != 0);
}

Error:
>$ clang++ -w -O3 -march=skx -c repr.cpp
llvm-trunk/lib/CodeGen/SelectionDAG/SelectionDAG.cpp:3975: llvm::SDValue
llvm::SelectionDAG::getNode(unsigned int, const llvm::SDLoc&, llvm::EVT,
llvm::SDValue, llvm::SDValue, const llvm::SDNodeFlags*): Assertion
`N1.getValueType() == N2.getValueType() && N1.getValueType() == VT && "Binary
operator types must match!"' failed.

1.   parser at end of file
2.  Code generation
3.  Running pass 'Function Pass Manager' on module
'func_reduced_clang_skx_opt.cpp'.
4.  Running pass 'X86 DAG->DAG Instruction Selection' on function
'@_Z3foov'

LLVM version:
clang version 5.0.0 (trunk 297835)
Target: x86_64-unknown-linux-gnu
Thread model: posix
InstalledDir: /home/vsevolod/workspace/llvm/bin-trunk/bin
Found candidate GCC installation: /usr/lib/gcc/i686-linux-gnu/5
Found candidate GCC installation: /usr/lib/gcc/i686-linux-gnu/5.4.0
Found candidate GCC installation: /usr/lib/gcc/i686-linux-gnu/6
Found candidate GCC installation: /usr/lib/gcc/i686-linux-gnu/6.0.0
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/5
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/5.4.0
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/6
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/6.0.0
Selected GCC installation: /usr/lib/gcc/x86_64-linux-gnu/5.4.0
Candidate multilib: .;@m64
Candidate multilib: 32;@m32
Candidate multilib: x32;@mx32
Selected multilib: .;@m64

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

[llvm-bugs] [Bug 32315] New: merge r292034 to 4.0.1

2017-03-16 Thread via llvm-bugs

https://bugs.llvm.org/show_bug.cgi?id=32315

Bug ID: 32315
   Summary: merge r292034 to 4.0.1
   Product: new-bugs
   Version: trunk
  Hardware: PC
OS: Linux
Status: NEW
  Severity: enhancement
  Priority: P
 Component: new bugs
  Assignee: unassignedb...@nondot.org
  Reporter: h...@chromium.org
CC: llvm-bugs@lists.llvm.org
Depends on: 32295
Blocks: 32061

merge r292034 to 4.0.1


Referenced Bugs:

https://bugs.llvm.org/show_bug.cgi?id=32061
[Bug 32061] [meta] 4.0.1 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=32295
[Bug 32295] missing const qualifier in two DenseSetImpl overloaded operators
(Clang build fails)
-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

[llvm-bugs] [Bug 32295] missing const qualifier in two DenseSetImpl overloaded operators (Clang build fails)

2017-03-16 Thread via llvm-bugs

https://bugs.llvm.org/show_bug.cgi?id=32295

Reid Kleckner  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

--- Comment #2 from Reid Kleckner  ---
A fix was committed in https://reviews.llvm.org/D28726 / r292034.

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

[llvm-bugs] [Bug 32304] AVX512: _mm512_sin_ps and similar intrinsics missing

2017-03-16 Thread via llvm-bugs

https://bugs.llvm.org/show_bug.cgi?id=32304

Craig Topper  changed:

   What|Removed |Added

 CC||craig.top...@gmail.com
 Resolution|--- |WONTFIX
 Status|NEW |RESOLVED

--- Comment #2 from Craig Topper  ---
These intrinsics don't correspond to single instructions. They are part of
Intel's SVML math library which ships with the Intel compiler.

Neither clang or gcc are likely to ever support these as it would require a
math library to be created and released with the compiler.

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

[llvm-bugs] [Bug 32314] New: Miscompile in GVN due to bug in BasisAA

2017-03-16 Thread via llvm-bugs

http://bugs.llvm.org/show_bug.cgi?id=32314

Bug ID: 32314
   Summary: Miscompile in GVN due to bug in BasisAA
   Product: libraries
   Version: trunk
  Hardware: PC
OS: Windows NT
Status: NEW
  Severity: enhancement
  Priority: P
 Component: Global Analyses
  Assignee: unassignedb...@nondot.org
  Reporter: craig.top...@gmail.com
CC: llvm-bugs@lists.llvm.org

Created attachment 18113
  --> http://bugs.llvm.org/attachment.cgi?id=18113=edit
IR just before GVN runs.

In the attached IR, GVN removes the following load

  %6 = load i32, i32* %p.017, align 4, !tbaa !1

as it believes it can get the value from the previous iteration of the loop.

What it fails to realize is that this store

  store i32 50, i32* %arrayidx, align 4, !tbaa !1

aliases the load.

This is because during BasicAA we go through this PHI feeding the load

  %p.017 = phi i32* [ %r, %entry ], [ %arrayidx3, %for.body ]

to find this GEP

  %arrayidx3 = getelementptr inbounds [3 x i32], [3 x i32]* %a, i64 0, i64
%indvars.iv

then compare it to this GEP which feeds the store

  %arrayidx = getelementptr inbounds [3 x i32], [3 x i32]* %a, i64 0, i64 %4

Then we ask ValueTracking if %4 is known non-equal to %indvars.iv.
ValueTracking sees that %4 is equal to %indvars.iv - 1, so returns that they
are known non-equal and BasicAA returns NoAlias. But this is wrong because we
crossed a PHI to get to the GEP using %indvars.i so we're really looking at
%indvars.iv from two different loop iterations.

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

[llvm-bugs] [Bug 10610] PVS-Studio vs Clang

2017-03-16 Thread via llvm-bugs

https://bugs.llvm.org/show_bug.cgi?id=10610

Simon Pilgrim  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

--- Comment #4 from Simon Pilgrim  ---
Resolving this - all these PVS warnings are fixed.

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

[llvm-bugs] [Bug 30996] [META] PVS Studio Warnings

2017-03-16 Thread via llvm-bugs

https://bugs.llvm.org/show_bug.cgi?id=30996
Bug 30996 depends on bug 10610, which changed state.

Bug 10610 Summary: PVS-Studio vs Clang
https://bugs.llvm.org/show_bug.cgi?id=10610

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

[llvm-bugs] [Bug 12357] PVS-Studio

2017-03-16 Thread via llvm-bugs

https://bugs.llvm.org/show_bug.cgi?id=12357

Simon Pilgrim  changed:

   What|Removed |Added

 CC||llvm-...@redking.me.uk
 Resolution|--- |FIXED
 Status|NEW |RESOLVED

--- Comment #13 from Simon Pilgrim  ---
Resolving this - all these PVS warnings were fixed long ago.

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

[llvm-bugs] [Bug 30996] [META] PVS Studio Warnings

2017-03-16 Thread via llvm-bugs

https://bugs.llvm.org/show_bug.cgi?id=30996
Bug 30996 depends on bug 12357, which changed state.

Bug 12357 Summary: PVS-Studio
https://bugs.llvm.org/show_bug.cgi?id=12357

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

[llvm-bugs] [Bug 32313] New: lib/xray/tests/unit/xray_fdr_log_printer_tool.cc should include

2017-03-16 Thread via llvm-bugs

https://bugs.llvm.org/show_bug.cgi?id=32313

Bug ID: 32313
   Summary: lib/xray/tests/unit/xray_fdr_log_printer_tool.cc
should include 
   Product: XRay
   Version: unspecified
  Hardware: PC
OS: Linux
Status: NEW
  Severity: enhancement
  Priority: P
 Component: Compiler instrumentation
  Assignee: dber...@google.com
  Reporter: octopl...@yandex.com
CC: llvm-bugs@lists.llvm.org

building with gcc trunk shows:

/home/markus/llvm/projects/compiler-rt/lib/xray/tests/unit/xray_fdr_log_printer_tool.cc:
In function ‘int main(int, char**)’:
/home/markus/llvm/projects/compiler-rt/lib/xray/tests/unit/xray_fdr_log_printer_tool.cc:284:30:
error: ‘function’ is not a member of ‘std’
   std::map>
TopLevelRecordMap;
  ^~~~
/home/markus/llvm/projects/compiler-rt/lib/xray/tests/unit/xray_fdr_log_printer_tool.cc:284:30:
note: suggested alternative: ‘is_function’
   std::map>
TopLevelRecordMap;
  ^~~~
  is_function
/home/markus/llvm/projects/compiler-rt/lib/xray/tests/unit/xray_fdr_log_printer_tool.cc:284:30:
error: ‘function’ is not a member of ‘std’
/home/markus/llvm/projects/compiler-rt/lib/xray/tests/unit/xray_fdr_log_printer_tool.cc:284:30:
note: suggested alternative: ‘is_function’
   std::map>
TopLevelRecordMap;
  ^~~~
  is_function
/home/markus/llvm/projects/compiler-rt/lib/xray/tests/unit/xray_fdr_log_printer_tool.cc:284:59:
error: template argument 2 is invalid
   std::map>
TopLevelRecordMap;
   ^~
/home/markus/llvm/projects/compiler-rt/lib/xray/tests/unit/xray_fdr_log_printer_tool.cc:284:59:
error: template argument 4 is invalid
...

diff --git a/lib/xray/tests/unit/xray_fdr_log_printer_tool.cc
b/lib/xray/tests/unit/xray_fdr_log_printer_tool.cc
index a4d05f200de5..6e209809e346 100644
--- a/lib/xray/tests/unit/xray_fdr_log_printer_tool.cc
+++ b/lib/xray/tests/unit/xray_fdr_log_printer_tool.cc
@@ -17,6 +17,7 @@
 #include 
 #include 
 #include 
+#include 
 #include 
 #include 
 #include 

fixes the issue.

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

[llvm-bugs] [Bug 22338] bool llvm::SelectionDAG::RemoveNodeFromCSEMaps(llvm::SDNode*): Assertion `N->getOpcode() != ISD::DELETED_NODE && "DELETED_NODE in CSEMap!"' failed

2017-03-16 Thread via llvm-bugs

https://bugs.llvm.org/show_bug.cgi?id=22338

Simon Pilgrim  changed:

   What|Removed |Added

 CC||llvm-...@redking.me.uk
 Resolution|--- |FIXED
 Status|NEW |RESOLVED

--- Comment #4 from Simon Pilgrim  ---
This was broken by 3.5 and fixed for 3.7. I've added a test case at rL297957.

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

[llvm-bugs] [Bug 32312] New: clang-format incorrectly puts space before and after * in local function pointer decl

2017-03-16 Thread via llvm-bugs

https://bugs.llvm.org/show_bug.cgi?id=32312

Bug ID: 32312
   Summary: clang-format incorrectly puts space before and after *
in local function pointer decl
   Product: clang
   Version: unspecified
  Hardware: PC
OS: Windows NT
Status: NEW
  Severity: enhancement
  Priority: P
 Component: Formatter
  Assignee: unassignedclangb...@nondot.org
  Reporter: nicolaswe...@gmx.de
CC: djas...@google.com, kli...@google.com,
llvm-bugs@lists.llvm.org

Not sure if this is a regression, but

void f() {
  void (*SetRow)(uint8* dst, uint8 value, int width) = SetRow_C;
}

gets turned into

C:\src\chrome\src>buildtools\win\clang-format.exe temp.cc
void f() {
  void (*SetRow)(uint8 * dst, uint8 value, int width) = SetRow_C;
}

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

[llvm-bugs] [Bug 32285] ToT fails to compile LegalizeIntegerTypes with code coverage enabled

2017-03-16 Thread via llvm-bugs

http://bugs.llvm.org/show_bug.cgi?id=32285

Jonas Paulsson  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|NEW |RESOLVED

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

[llvm-bugs] [Bug 32311] New: Incorrect result with -O1 -march=skx

2017-03-16 Thread via llvm-bugs

https://bugs.llvm.org/show_bug.cgi?id=32311

Bug ID: 32311
   Summary: Incorrect result with -O1 -march=skx
   Product: new-bugs
   Version: trunk
  Hardware: PC
OS: Linux
Status: NEW
  Severity: enhancement
  Priority: P
 Component: new bugs
  Assignee: unassignedb...@nondot.org
  Reporter: vsevolod.livins...@frtk.ru
CC: llvm-bugs@lists.llvm.org

Created attachment 18112
  --> https://bugs.llvm.org/attachment.cgi?id=18112=edit
Reproducer.

Clang produces wrong code with -O1/2/3 -march=skx options. 
According to LLVM bisect, it is a fault of X86 DAG->DAG Instruction Selection
(as far as I understood its output).
BISECT: running pass (62) X86 DAG->DAG Instruction Selection on function
BISECT: NOT running pass (63) Local Dynamic TLS Access Clean-up on function

Unfortunately, I failed to reduce test case further.

Error:
>$ clang++ -w -O0 -march=skx *.cpp 
>$ sde -skx -- ./a.out
1
>$ clang++ -w -O1 -march=skx *.cpp 
>$ sde -skx -- ./a.out 
-1

LLVM version:
clang version 5.0.0 (trunk 297835)
Target: x86_64-unknown-linux-gnu
Thread model: posix
InstalledDir: /home/vsevolod/workspace/llvm/bin-trunk/bin
Found candidate GCC installation: /usr/lib/gcc/i686-linux-gnu/5
Found candidate GCC installation: /usr/lib/gcc/i686-linux-gnu/5.4.0
Found candidate GCC installation: /usr/lib/gcc/i686-linux-gnu/6
Found candidate GCC installation: /usr/lib/gcc/i686-linux-gnu/6.0.0
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/5
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/5.4.0
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/6
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/6.0.0
Selected GCC installation: /usr/lib/gcc/x86_64-linux-gnu/5.4.0
Candidate multilib: .;@m64
Candidate multilib: 32;@m32
Candidate multilib: x32;@mx32
Selected multilib: .;@m64

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

[llvm-bugs] [Bug 32310] New: clang SIGSEV crash in clang::DecltypeType::desugar

2017-03-16 Thread via llvm-bugs

https://bugs.llvm.org/show_bug.cgi?id=32310

Bug ID: 32310
   Summary: clang SIGSEV crash in clang::DecltypeType::desugar
   Product: clang
   Version: unspecified
  Hardware: PC
OS: Linux
Status: NEW
  Severity: normal
  Priority: P
 Component: C++
  Assignee: unassignedclangb...@nondot.org
  Reporter: bicapitalizat...@gmail.com
CC: dgre...@apple.com, llvm-bugs@lists.llvm.org

Created attachment 18110
  --> https://bugs.llvm.org/attachment.cgi?id=18110=edit
Preprocessed source that causes the crash

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

[llvm-bugs] [Bug 32309] New: ld: unknown option: --version-script= failure in lib/libomptarget.dylib

2017-03-16 Thread via llvm-bugs

http://bugs.llvm.org/show_bug.cgi?id=32309

Bug ID: 32309
   Summary: ld: unknown option: --version-script= failure in
lib/libomptarget.dylib
   Product: OpenMP
   Version: unspecified
  Hardware: Macintosh
OS: MacOS X
Status: NEW
  Severity: normal
  Priority: P
 Component: Runtime Library
  Assignee: unassignedb...@nondot.org
  Reporter: howarth.mailing.li...@gmail.com
CC: llvm-bugs@lists.llvm.org

The build of openmp for current svn trunk fails on x86_64-apple-darwin16 with
the error...

[ 46%] Linking CXX shared library ../../../lib/libomptarget.dylib
cd /sw/src/fink.build/llvm50-5.0.0-1/build/stage1/projects/openmp/libomptarget
&& /sw/bin/cmake -E cmake_link_script CMakeFiles/omptarget.dir/link.txt
--verbose=1
/sw/src/fink.build/llvm50-5.0.0-1/opt-bin/ccclang++ -fno-common -fPIC
-fvisibility-inlines-hidden -Wall -W -Wno-unused-parameter -Wwrite-strings
-Wcast-qual -Wmissing-field-initializers -pedantic -Wno-long-long
-Wcovered-switch-default -Wnon-virtual-dtor -Wdelete-non-virtual-dtor
-Wstring-conversion -Werror=date-time -std=c++11 -O3 -dynamiclib
-Wl,-headerpad_max_install_names  -L/sw/lib -o ../../../lib/libomptarget.dylib
-install_name
/sw/src/fink.build/llvm50-5.0.0-1/build/stage1/lib/libomptarget.dylib
CMakeFiles/omptarget.dir/src/omptarget.cpp.o -ldl
-Wl,--version-script=/sw/src/fink.build/llvm50-5.0.0-1/llvm-5.0.0.src/projects/openmp/libomptarget/exports
 
ld: unknown option:
--version-script=/sw/src/fink.build/llvm50-5.0.0-1/llvm-5.0.0.src/projects/openmp/libomptarget/exports
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[2]: *** [lib/libomptarget.dylib] Error 1
make[1]: *** [projects/openmp/libomptarget/CMakeFiles/omptarget.dir/all] Error
2
make: *** [all] Error 2

due to the lack of support for the --version-script= option in the darwin
linker.

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

[llvm-bugs] [Bug 32308] New: ld.lld doesn't support --compress-debug-sections option

2017-03-16 Thread via llvm-bugs

https://bugs.llvm.org/show_bug.cgi?id=32308

Bug ID: 32308
   Summary: ld.lld doesn't support --compress-debug-sections
option
   Product: lld
   Version: unspecified
  Hardware: PC
OS: Linux
Status: NEW
  Severity: enhancement
  Priority: P
 Component: ELF
  Assignee: unassignedb...@nondot.org
  Reporter: wielkie...@gmail.com
CC: llvm-bugs@lists.llvm.org

Linux ld has an option --compress-debug-sections that is used in order to
compress debug sections into the output binary. ld.lld currently lacks this
option.

http://man7.org/linux/man-pages/man1/ld.1.html

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

[llvm-bugs] [Bug 32307] New: Inconsistent init_array section type when using -static-libstdc++

2017-03-16 Thread via llvm-bugs

https://bugs.llvm.org/show_bug.cgi?id=32307

Bug ID: 32307
   Summary: Inconsistent init_array section type when using
-static-libstdc++
   Product: lld
   Version: unspecified
  Hardware: PC
OS: Linux
Status: NEW
  Severity: normal
  Priority: P
 Component: ELF
  Assignee: unassignedb...@nondot.org
  Reporter: wielkie...@gmail.com
CC: llvm-bugs@lists.llvm.org

When building anything that uses any symbol from libstdc++ using gcc-5.2 and
lld-4.0 linker with -static-libstdc++ option I get the following:

ld: error: Section has different type from others with the same name
basic_file.o:(.init_array.00099)
ld: error: Section has different type from others with the same name
list.o:(.init_array.00099)
ld: error: Section has different type from others with the same name
globals_io.o:(.init_array.00099)
...

Reproducible example:

echo -e '#include\nint main() { return 0; }' | g++ -xc++ -
-static-libstdc++

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

[llvm-bugs] [Bug 32306] New: _mm256_max_epi32 broken up into cmp and blend

2017-03-16 Thread via llvm-bugs

https://bugs.llvm.org/show_bug.cgi?id=32306

Bug ID: 32306
   Summary: _mm256_max_epi32 broken up into cmp and blend
   Product: clang
   Version: 4.0
  Hardware: PC
OS: Linux
Status: NEW
  Severity: normal
  Priority: P
 Component: -New Bugs
  Assignee: unassignedclangb...@nondot.org
  Reporter: m...@sven-woop.de
CC: llvm-bugs@lists.llvm.org

Created attachment 18109
  --> https://bugs.llvm.org/attachment.cgi?id=18109=edit
reproducer

Under some circumstances _mm256_max_epi32 will get broken up into some compare
and blend intrinsics which hurts performance. Minimal reproducer attached.

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

[llvm-bugs] [Bug 32146] Enable -verify-machineinstrs with EXPENSIVE_CHECKS

2017-03-16 Thread via llvm-bugs

https://bugs.llvm.org/show_bug.cgi?id=32146
Bug 32146 depends on bug 30999, which changed state.

Bug 30999 Summary: LLVM_ENABLE_EXPENSIVE_CHECKS reveals 540 failures.
https://bugs.llvm.org/show_bug.cgi?id=30999

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

[llvm-bugs] [Bug 30999] LLVM_ENABLE_EXPENSIVE_CHECKS reveals 540 failures.

2017-03-16 Thread via llvm-bugs

https://bugs.llvm.org/show_bug.cgi?id=30999

Florian Hahn  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

--- Comment #23 from Florian Hahn  ---
Yes I think we should. Given that the build bot seems stable I'll close this
issue. Thanks everyone involved!

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

[llvm-bugs] [Bug 32305] New: AVX512: _mm512_cvtss_f32 intrinsic missing

2017-03-16 Thread via llvm-bugs

https://bugs.llvm.org/show_bug.cgi?id=32305

Bug ID: 32305
   Summary: AVX512: _mm512_cvtss_f32 intrinsic missing
   Product: clang
   Version: 4.0
  Hardware: PC
OS: All
Status: NEW
  Severity: normal
  Priority: P
 Component: -New Bugs
  Assignee: unassignedclangb...@nondot.org
  Reporter: m...@sven-woop.de
CC: llvm-bugs@lists.llvm.org

Created attachment 18108
  --> https://bugs.llvm.org/attachment.cgi?id=18108=edit
reproducer

The _mm512_cvtss_f32 intrinsic is missing. Reproducer attached.

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

[llvm-bugs] [Bug 32304] New: AVX512: _mm512_sin_ps and similar intrinsics missing

2017-03-16 Thread via llvm-bugs

https://bugs.llvm.org/show_bug.cgi?id=32304

Bug ID: 32304
   Summary: AVX512: _mm512_sin_ps and similar intrinsics missing
   Product: clang
   Version: 4.0
  Hardware: PC
OS: All
Status: NEW
  Severity: normal
  Priority: P
 Component: -New Bugs
  Assignee: unassignedclangb...@nondot.org
  Reporter: m...@sven-woop.de
CC: llvm-bugs@lists.llvm.org

Created attachment 18106
  --> https://bugs.llvm.org/attachment.cgi?id=18106=edit
reproducer

AVX512 versions of sin/cos/exp and similar intrinsics are missing. A reproducer
is attached.

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

[llvm-bugs] [Bug 32303] New: llvm-tblgen crashes when compiling llvm 4.0 with gcc 6.2.1

2017-03-16 Thread via llvm-bugs

https://bugs.llvm.org/show_bug.cgi?id=32303

Bug ID: 32303
   Summary: llvm-tblgen crashes when compiling llvm 4.0 with gcc
6.2.1
   Product: new-bugs
   Version: 4.0
  Hardware: PC
OS: Linux
Status: NEW
  Severity: enhancement
  Priority: P
 Component: new bugs
  Assignee: unassignedb...@nondot.org
  Reporter: blastr...@free.fr
CC: llvm-bugs@lists.llvm.org

Created attachment 18105
  --> https://bugs.llvm.org/attachment.cgi?id=18105=edit
Backtrace of the crash

Hi,

I'm trying to compile the latest version of llvm. I have checked out the
release_40 branch in my worktree, but llvm-tblgen keeps crashing.

I am using debian testing with GCC 6.2.1

To reproduce the crash:

cmake -DLLVM_TARGETS_TO_BUILD=X86 -DBUILD_SHARED_LIBS=ON
-DCMAKE_INSTALL_PREFIX=$HOME/.local -DCMAKE_BUILD_TYPE=RelWithDebInfo -G Ninja
..
ninja lib/Target/X86/X86GenRegisterInfo.inc # to go straight to the crash
...
0.  Program arguments: /home/philippe/packages/llvm/build/bin/llvm-tblgen
-gen-register-info -I /home/philippe/packages/llvm/lib/Target/X86 -I
/home/philippe/packages/llvm/include -I /home/philippe/packages/llvm/lib/Target
/home/philippe/packages/llvm/lib/Target/X86/X86.td -o
/home/philippe/packages/llvm/build/lib/Target/X86/X86GenRegisterInfo.inc.tmp 
Segmentation fault (core dumped)

I am attaching the full backtrace

The crash does not occur when building in debug.

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

[llvm-bugs] [Bug 32302] New: Template parameter type deduction of function conflicts when parameter is a vector return value of builtin function

2017-03-16 Thread via llvm-bugs

https://bugs.llvm.org/show_bug.cgi?id=32302

Bug ID: 32302
   Summary: Template parameter type deduction of function
conflicts when parameter is a vector return value of
builtin function
   Product: clang
   Version: trunk
  Hardware: Other
OS: Linux
Status: NEW
  Severity: enhancement
  Priority: P
 Component: C++
  Assignee: unassignedclangb...@nondot.org
  Reporter: westion...@gmail.com
CC: dgre...@apple.com, llvm-bugs@lists.llvm.org

cat a.C

template 
A f(const A& a, const A& b){
return a+b;
}

int main(){
vector int a;
vector float b;
f(__builtin_altivec_vcfsx(a,0),b);
}


clang++ a.C -faltivec
a.C:9:1: error: no matching function for call to 'f'
f(__builtin_altivec_vcfsx(a,0),b);
^
a.C:2:3: note: candidate template ignored: deduced conflicting types for
parameter 'A' ('__attribute__((__vector_size__(4 * sizeof(float float'
  (vector of 4 'float' values) vs. '__vector float' (vector of 4 'float'
values))
A f(const A& a, const A& b){
  ^
1 error generated.

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

[llvm-bugs] [Bug 32300] New: Wrong resolving boost::variant template arguments by formatters API

2017-03-16 Thread via llvm-bugs

https://bugs.llvm.org/show_bug.cgi?id=32300

Bug ID: 32300
   Summary: Wrong resolving boost::variant template arguments by
formatters API
   Product: lldb
   Version: 3.9
  Hardware: Macintosh
OS: MacOS X
Status: NEW
  Severity: normal
  Priority: P
 Component: All Bugs
  Assignee: lldb-...@lists.llvm.org
  Reporter: andrew.stepano...@gmail.com
CC: llvm-bugs@lists.llvm.org

1. Use C++ code:

#include 
#include 
#include 

template
struct Example
{
using Variant = boost::variant;
};

int main()
{
Example::Variant ex(std::string("string"));
Example::Variant ex2(10);
return ex.which() == ex2.which();
}


2. Use formatter for boost::variant:

import lldb
import lldb.formatters.Logger

def get_template_arg(valobj, i):
valobj_type = valobj.GetType().GetUnqualifiedType()
if valobj_type.IsReferenceType():
valobj_type = valobj_type.GetDereferencedType()
if valobj_type.GetNumberOfTemplateArguments() > i:
data_type = valobj_type.GetTemplateArgumentType(i)
else:
data_type = None
return data_type

class BoostVariantSynthProvider:
def __init__(self, valobj, dict):
self.val_obj = valobj
self.value = None
self.update()

def num_children(self):
return 1

def has_children(self):
return True

def get_child_index(self, name):
if name == "value":
return 0

return -1

def get_child_at_index(self, index):
if index == 0:
return self.value

return None

def update(self):
type_index =
self.val_obj.GetChildMemberWithName("which_").GetValueAsUnsigned()
element_type = get_template_arg(self.val_obj, type_index)
self.value =
self.val_obj.GetChildMemberWithName("storage_").GetChildMemberWithName("data_").
\
GetChildMemberWithName("buf").CreateChildAtOffset("value", 0,
element_type)

Actual:
GetNumberOfTemplateArguments() returns 1 for Example::Variant type and
get_template_arg returns 'None'
Expected:
GetNumberOfTemplateArguments() should return 3 for Example::Variant type
and get_template_arg should returns std::string type

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

39 matches

Mail list logo