[llvm-bugs] Issue 5212 in oss-fuzz: llvm/llvm-isel-fuzzer--aarch64-gisel: Out-of-memory in llvm_llvm-isel-fuzzer--aarch64-gisel

2018-01-09 Thread ClusterFuzz-External via monorail via llvm-bugs 

Status: New
Owner: 
CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com,  
igm...@gmail.com, llvm-b...@lists.llvm.org, v...@apple.com,  
mitchphi...@outlook.com, akils...@apple.com
Labels: ClusterFuzz Reproducible Engine-libfuzzer Proj-llvm  
Reported-2018-01-10

Type: Bug

New issue 5212 by ClusterFuzz-External:  
llvm/llvm-isel-fuzzer--aarch64-gisel: Out-of-memory in  
llvm_llvm-isel-fuzzer--aarch64-gisel

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=5212

Detailed report: https://oss-fuzz.com/testcase?key=5510734101348352

Project: llvm
Fuzzer: libFuzzer_llvm_llvm-isel-fuzzer--aarch64-gisel
Fuzz target binary: llvm-isel-fuzzer--aarch64-gisel
Job Type: libfuzzer_asan_llvm
Platform Id: linux

Crash Type: Out-of-memory (exceeds 2048 MB)
Crash Address:
Crash State:
  llvm_llvm-isel-fuzzer--aarch64-gisel

Sanitizer: address (ASAN)

Regressed:  
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm=201710121744:201710130152


Reproducer Testcase:  
https://oss-fuzz.com/download?testcase_id=5510734101348352


Issue filed automatically.

See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for  
more information.


When you fix this bug, please
  * mention the fix revision(s).
  * state whether the bug was a short-lived regression or an old bug in any  
stable releases.

  * add any other useful information.
This information can help downstream consumers.

If you have questions for the OSS-Fuzz team, please file an issue at  
https://github.com/google/oss-fuzz/issues.


--
You received this message because:
  1. You were specifically CC'd on the issue

You may adjust your notification preferences at:
https://bugs.chromium.org/hosting/settings

Reply to this email to add a comment.
___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

[llvm-bugs] [Bug 31476] LLD failed to link symbols with "protected" visibility

2018-01-09 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=31476

Rafael Ávila de Espíndola  changed:

   What|Removed |Added

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

--- Comment #10 from Rafael Ávila de Espíndola  ---
r322152 adds --ignore-function-address-equality and
--ignore-data-address-equality.

-- 
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 35881] New: Unable to initialize/assign a pointer to VLA

2018-01-09 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=35881

Bug ID: 35881
   Summary: Unable to initialize/assign a pointer to VLA
   Product: clang
   Version: trunk
  Hardware: PC
OS: All
Status: NEW
  Severity: enhancement
  Priority: P
 Component: C++
  Assignee: unassignedclangb...@nondot.org
  Reporter: ignat.losku...@gmail.com
CC: dgre...@apple.com, llvm-bugs@lists.llvm.org

Consider the following example:

int foo(int *ptr, size_t rows, size_t cols) {
int (*m)[cols] = (int(*)[cols])(ptr);
return m[rows - 1][cols - 1];
}

It fails to compile in C++ mode with a weird error message:

1 : :1:11: error: cannot initialize a variable of type 'int (*)[cols]'
with an rvalue of type 'int (*)[cols]'
int (*ptr)[cols] = (int(*)[cols])(m);
  ^~

Although VLAs are not a part of C++ standard, Clang claims to support them for
compatibility with GCC. GCC, ICC, and Clang in C mode compile this piece of
code successfully.

-- 
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 35858] .space asm directive does not accept multiple symbols with .space between

2018-01-09 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=35858

Rafael Ávila de Espíndola  changed:

   What|Removed |Added

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

--- Comment #3 from Rafael Ávila de Espíndola  ---
Fixed in r322131.

-- 
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 35880] New: dlsym causes illegal hardware instruction

2018-01-09 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=35880

Bug ID: 35880
   Summary: dlsym causes illegal hardware instruction
   Product: new-bugs
   Version: trunk
  Hardware: PC
OS: Linux
Status: NEW
  Severity: normal
  Priority: P
 Component: new bugs
  Assignee: unassignedb...@nondot.org
  Reporter: kongy@gmail.com
CC: llvm-bugs@lists.llvm.org

#define _GNU_SOURCE
#include 

int main() {
  void** addrPtr;
  *addrPtr = dlsym(RTLD_NEXT, "signal");
}

This code should segfault, but with
$ clang illegal.c -O1 -ldl
$ ./a.out
[1]229484 illegal hardware instruction  ./a.out

-- 
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 35879] Loop Vectorizer does not handle masked gather

2018-01-09 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=35879

Trass3r  changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|INVALID |---

--- Comment #2 from Trass3r  ---
Not exactly. Let's forget about the int return type:
https://godbolt.org/g/dm8nvd

 control flow cannot be substituted for a select
 value that could not be identified as reduction is used outside the loop
 cannot identify array bounds

I disabled loop unroll to actually see some vectorizer analysis results.
Is it intentional that the unroller "overrides" the loop vectorizer?
Does the SLP vectorizer kick in after that? I couldn't find any analysis option
for it.

-- 
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 35879] Loop Vectorizer does not handle masked gather

2018-01-09 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=35879

Davide Italiano  changed:

   What|Removed |Added

 CC||dav...@freebsd.org
 Status|NEW |RESOLVED
 Resolution|--- |INVALID

--- Comment #1 from Davide Italiano  ---
Same as PR35878.

-- 
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 35878] Loop Vectorizer does not recognize packed load

2018-01-09 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=35878

Davide Italiano  changed:

   What|Removed |Added

 CC||dav...@freebsd.org
 Status|NEW |RESOLVED
 Resolution|--- |INVALID

--- Comment #1 from Davide Italiano  ---
Your program exhibits UB, as you're missing a `return`.

Change it to:

#include 
int foo(uint32_t* __restrict r, uint32_t* __restrict ptr)
{
for (int j = 0; j < 8; ++j)
r[j] = *(ptr++);
return 0;
}

And you get:

foo(unsigned int*, unsigned int*): # @foo(unsigned int*, unsigned int*)
  vmovups ymm0, ymmword ptr [rsi]
  vmovups ymmword ptr [rdi], ymm0
  xor eax, eax
  vzeroupper
  ret


which is a vectorized sequence.

-- 
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 35804] [meta] 6.0.0 Release Blockers

2018-01-09 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=35804
Bug 35804 depends on bug 35628, which changed state.

Bug 35628 Summary: [SLP] "Replacing out-of-tree value with undef" in 
SLPVectorizer.cpp
https://bugs.llvm.org/show_bug.cgi?id=35628

   What|Removed |Added

 Status|ASSIGNED|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 35628] [SLP] "Replacing out-of-tree value with undef" in SLPVectorizer.cpp

2018-01-09 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=35628

Alexey Bataev  changed:

   What|Removed |Added

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

--- Comment #3 from Alexey Bataev  ---
Fixed in rL321993

-- 
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 35777] Invalid InsertValueInst operands!

2018-01-09 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=35777

Alexey Bataev  changed:

   What|Removed |Added

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

--- Comment #6 from Alexey Bataev  ---
Fixed in rL321994

-- 
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 35804] [meta] 6.0.0 Release Blockers

2018-01-09 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=35804
Bug 35804 depends on bug 35777, which changed state.

Bug 35777 Summary: Invalid InsertValueInst operands!
https://bugs.llvm.org/show_bug.cgi?id=35777

   What|Removed |Added

 Status|ASSIGNED|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 35865] [SLP] Regression (r310260): Not a vector MVT! UNREACHABLE executed

2018-01-09 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=35865

Alexey Bataev  changed:

   What|Removed |Added

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

--- Comment #1 from Alexey Bataev  ---
Fixed in rL322106

-- 
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 35804] [meta] 6.0.0 Release Blockers

2018-01-09 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=35804
Bug 35804 depends on bug 35865, which changed state.

Bug 35865 Summary: [SLP] Regression (r310260): Not a vector MVT! UNREACHABLE 
executed
https://bugs.llvm.org/show_bug.cgi?id=35865

   What|Removed |Added

 Status|ASSIGNED|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 35879] New: Loop Vectorizer does not handle masked gather

2018-01-09 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=35879

Bug ID: 35879
   Summary: Loop Vectorizer does not handle masked gather
   Product: libraries
   Version: trunk
  Hardware: PC
OS: All
Status: NEW
  Severity: normal
  Priority: P
 Component: Loop Optimizer
  Assignee: unassignedb...@nondot.org
  Reporter: tras...@gmail.com
CC: llvm-bugs@lists.llvm.org

#include 
int foo(uint32_t* __restrict r, uint32_t* __restrict ptr)
{
for (int j = 0; j < 8; ++j)
   if (r[j] < 1024)
r[j] = *(ptr++);
}

https://software.intel.com/en-us/node/523959

$ clang -std=c++14 -O3 -S -fverbose-asm -march=haswell
-Rpass-missed=loop-vectorize -Rpass-analysis=loop-vectorize test.cpp

  loop control flow is not understood by vectorizer

https://godbolt.org/g/8HNuay

Oddly enough when simply changing the return type to void the loop unroller
takes over and no vectorization is attempted at all (which is kind of common
with clang).

-- 
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 35878] New: Loop Vectorizer does not recognize packed load

2018-01-09 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=35878

Bug ID: 35878
   Summary: Loop Vectorizer does not recognize packed load
   Product: libraries
   Version: trunk
  Hardware: PC
OS: All
Status: NEW
  Severity: normal
  Priority: P
 Component: Loop Optimizer
  Assignee: unassignedb...@nondot.org
  Reporter: tras...@gmail.com
CC: llvm-bugs@lists.llvm.org

#include 
int foo(uint32_t* __restrict r, uint32_t* __restrict ptr)
{
for (int j = 0; j < 8; ++j)
r[j] = *(ptr++);
}

$ clang -std=c++14 -O3 -S -fverbose-asm -march=haswell
-Rpass-missed=loop-vectorize -Rpass-analysis=loop-vectorize test.cpp

loop control flow is not understood by vectorizer

Oddly enough it does work when changing the return type to void!

https://godbolt.org/g/5uvodB

-- 
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 30995] [META][GVN] NewGVN Integration

2018-01-09 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=30995
Bug 30995 depends on bug 33367, which changed state.

Bug 33367 Summary: Essential code deleted by new GVN
https://bugs.llvm.org/show_bug.cgi?id=33367

   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 33367] Essential code deleted by new GVN

2018-01-09 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=33367

Daniel Berlin  changed:

   What|Removed |Added

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

--- Comment #16 from Daniel Berlin  ---
Fix in r322115

-- 
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 35869] _mm_setzero_si64 violates the spec by generating xorps instead of pxor

2018-01-09 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=35869

Gonzalo BG  changed:

   What|Removed |Added

 Resolution|--- |INVALID
 Status|NEW |RESOLVED

--- Comment #5 from Gonzalo BG  ---
> Okay... so that function requests a zero value in an SSE register.

Oh. I screwed up, I thought that `__m64` was always going to be an MMX
register. What is happening in this case? Is the calling convention requiring
it to be turned into an SSE register?

-- 
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 35846] [InstCombine] Compare known true or false was not folded

2018-01-09 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=35846

Sanjay Patel  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED
 Fixed By Commit(s)||322104

--- Comment #2 from Sanjay Patel  ---
I remembered that we added remarks for this kind of situation:
https://reviews.llvm.org/rL294208

...and it works from -instsimplify:

$ ./opt -instsimplify 35846.ll -S -pass-remarks-analysis=.*
remark: :0:0: Detected conflicting code assumptions. Program may have
undefined behavior, or compiler may have internal error.

...but not with -instcombine, so maybe the simplify query isn't populated
correctly in instcombine.

But this should be fixed with:
https://reviews.llvm.org/rL322104

-- 
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 35804] [meta] 6.0.0 Release Blockers

2018-01-09 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=35804
Bug 35804 depends on bug 35724, which changed state.

Bug 35724 Summary: regression (r315984): fatal error: error in backend: Broken 
function found (Did not see access type in access path!)
https://bugs.llvm.org/show_bug.cgi?id=35724

   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 35724] regression (r315984): fatal error: error in backend: Broken function found (Did not see access type in access path!)

2018-01-09 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=35724

Alex Lorenz  changed:

   What|Removed |Added

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

--- Comment #4 from Alex Lorenz  ---
Yep, your fix got rid of the crash that we saw. Thank you!

-- 
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 35877] New: LLD does not support "INSERT [AFTER|BEFORE]" statement(s) in LD scripts

2018-01-09 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=35877

Bug ID: 35877
   Summary: LLD does not support "INSERT [AFTER|BEFORE]"
statement(s) in LD scripts
   Product: lld
   Version: unspecified
  Hardware: Other
OS: other
Status: NEW
  Severity: normal
  Priority: P
 Component: ELF
  Assignee: unassignedb...@nondot.org
  Reporter: eblot...@gmail.com
CC: llvm-bugs@lists.llvm.org

Sequences such as the following:

SECTIONS
{
   ...
} INSERT AFTER .data;

are not recognised as valid directives:

"unknown directive: INSERT
>>> } INSERT AFTER .data;"

-- 
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 35876] New: Merge r322003 into 6.0

2018-01-09 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=35876

Bug ID: 35876
   Summary: Merge r322003 into 6.0
   Product: new-bugs
   Version: 6.0
  Hardware: PC
OS: Linux
Status: NEW
  Severity: normal
  Priority: P
 Component: new bugs
  Assignee: unassignedb...@nondot.org
  Reporter: nir...@google.com
CC: llvm-bugs@lists.llvm.org

I'm nominating merging "Teach BaseIndexOffset to correctly handle with indexed
operations" for the 6.0.0 branch. 

This is a straightforward bugfix in SelectionDAG's address analysis which was
triggered by a post-split commit in trunk.

-- 
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 35875] New: Arm regression for three way min/max

2018-01-09 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=35875

Bug ID: 35875
   Summary: Arm regression for three way min/max
   Product: libraries
   Version: trunk
  Hardware: PC
OS: Linux
Status: NEW
  Severity: enhancement
  Priority: P
 Component: Scalar Optimizations
  Assignee: unassignedb...@nondot.org
  Reporter: david.gr...@arm.com
CC: llvm-bugs@lists.llvm.org

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

This is https://bugs.llvm.org/show_bug.cgi?id=35717, part 2.

The regression is fixed for x86, we just need to do the same for Arm.

This is a piece of code that at it's heart does a three way min (also
attached):

target datalayout = "e-m:e-p:32:32-i64:64-v128:64:128-a:0:32-n32-S64"
target triple = "thumbv8m.base-arm-none-eabi"
define void @test(i8* nocapture readonly, i8* nocapture) {
  %3 = getelementptr inbounds i8, i8* %0, i32 1
  %4 = load i8, i8* %0, align 1
  %5 = getelementptr inbounds i8, i8* %0, i32 2
  %6 = load i8, i8* %3, align 1
  %7 = load i8, i8* %5, align 1
  %8 = xor i8 %4, -1
  %9 = xor i8 %6, -1
  %10 = xor i8 %7, -1
  %11 = zext i8 %8 to i32
  %12 = zext i8 %9 to i32
  %13 = icmp ult i8 %6, %4
  %14 = zext i8 %10 to i32
  %15 = icmp ult i32 %11, %14
  %16 = select i1 %15, i32 %11, i32 %14
  %17 = icmp ult i32 %12, %14
  %18 = select i1 %17, i32 %12, i32 %14
  %19 = select i1 %13, i32 %16, i32 %18
  %20 = trunc i32 %19 to i8
  %21 = sub nsw i32 %11, %19
  %22 = trunc i32 %21 to i8
  %23 = sub nsw i32 %12, %19
  %24 = trunc i32 %23 to i8
  %25 = sub nsw i32 %14, %19
  %26 = trunc i32 %25 to i8
  %27 = getelementptr inbounds i8, i8* %1, i32 1
  store i8 %20, i8* %1, align 1
  %28 = getelementptr inbounds i8, i8* %1, i32 2
  store i8 %22, i8* %27, align 1
  %29 = getelementptr inbounds i8, i8* %1, i32 3
  store i8 %24, i8* %28, align 1
  store i8 %26, i8* %29, align 1
  ret void
}

Because i8 isn't a legal type we don't remove the zext/trunc's. And because the
negated values are also stored we do not fold the 3 selects into 2.

-- 
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] Issue 5044 in oss-fuzz: llvm/llvm-isel-fuzzer--x86_64-O2: ASSERT: N->getNodeId() == -1 && "Node already inserted!"

2018-01-09 Thread ClusterFuzz-External via monorail via llvm-bugs 

Status: New
Owner: 
CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com,  
igm...@gmail.com, llvm-b...@lists.llvm.org, v...@apple.com,  
mitchphi...@outlook.com, akils...@apple.com
Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible  
Engine-libfuzzer Proj-llvm Reported-2018-01-09

Type: Bug

New issue 5044 by ClusterFuzz-External: llvm/llvm-isel-fuzzer--x86_64-O2:  
ASSERT: N->getNodeId() == -1 && "Node already inserted!"

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=5044

Detailed report: https://oss-fuzz.com/testcase?key=4701442003697664

Project: llvm
Fuzzer: libFuzzer_llvm_llvm-isel-fuzzer--x86_64-O2
Fuzz target binary: llvm-isel-fuzzer--x86_64-O2
Job Type: libfuzzer_asan_llvm
Platform Id: linux

Crash Type: ASSERT
Crash Address:
Crash State:
  N->getNodeId() == -1 && "Node already inserted!"
  ScheduleDAGRRList::PickNodeToScheduleBottomUp
  ScheduleDAGRRList::Schedule

Sanitizer: address (ASAN)

Regressed:  
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm=201710160455:201710190451


Reproducer Testcase:  
https://oss-fuzz.com/download?testcase_id=4701442003697664


Issue filed automatically.

See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for  
more information.


When you fix this bug, please
  * mention the fix revision(s).
  * state whether the bug was a short-lived regression or an old bug in any  
stable releases.

  * add any other useful information.
This information can help downstream consumers.

If you have questions for the OSS-Fuzz team, please file an issue at  
https://github.com/google/oss-fuzz/issues.


--
You received this message because:
  1. You were specifically CC'd on the issue

You may adjust your notification preferences at:
https://bugs.chromium.org/hosting/settings

Reply to this email to add a comment.
___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

[llvm-bugs] [Bug 35804] [meta] 6.0.0 Release Blockers

2018-01-09 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=35804
Bug 35804 depends on bug 35864, which changed state.

Bug 35864 Summary: After r320749, Assertion failed: (ScaledReg == nullptr), 
function SetCombinedField, file lib/CodeGen/CodeGenPrepare.cpp, line 1980.
https://bugs.llvm.org/show_bug.cgi?id=35864

   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 35864] After r320749, Assertion failed: (ScaledReg == nullptr), function SetCombinedField, file lib/CodeGen/CodeGenPrepare.cpp, line 1980.

2018-01-09 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=35864

Dimitry Andric  changed:

   What|Removed |Added

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

--- Comment #1 from Dimitry Andric  ---
Fixed by https://reviews.llvm.org/rL322056, like bug 35799.

-- 
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] Issue 3669 in oss-fuzz: llvm: ASSERT: NumParams == params.size() && "function has too many parameters"

2018-01-09 Thread sheriff… via monorail via llvm-bugs 

Updates:
Labels: Deadline-Approaching

Comment #5 on issue 3669 by sheriff...@chromium.org: llvm: ASSERT:  
NumParams == params.size() && "function has too many parameters"

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3669#c5

This bug is approaching its deadline for being fixed, and will be  
automatically derestricted within 7 days. If a fix is planned within 2  
weeks after the deadline has passed, a grace extension can be granted.


- Your friendly Sheriffbot

--
You received this message because:
  1. You were specifically CC'd on the issue

You may adjust your notification preferences at:
https://bugs.chromium.org/hosting/settings

Reply to this email to add a comment.
___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

[llvm-bugs] Issue 3676 in oss-fuzz: llvm/clang-format-fuzzer: ASSERT: PPBranchLevel < (int)PPLevelBranchIndex.size()

2018-01-09 Thread sheriff… via monorail via llvm-bugs 

Updates:
Labels: Deadline-Approaching

Comment #6 on issue 3676 by sheriff...@chromium.org:  
llvm/clang-format-fuzzer: ASSERT: PPBranchLevel <  
(int)PPLevelBranchIndex.size()

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3676#c6

This bug is approaching its deadline for being fixed, and will be  
automatically derestricted within 7 days. If a fix is planned within 2  
weeks after the deadline has passed, a grace extension can be granted.


- Your friendly Sheriffbot

--
You received this message because:
  1. You were specifically CC'd on the issue

You may adjust your notification preferences at:
https://bugs.chromium.org/hosting/settings

Reply to this email to add a comment.
___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

[llvm-bugs] [Bug 35874] New: [InstCombine] Support non-uniform constant vectors for mul -> shl

2018-01-09 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=35874

Bug ID: 35874
   Summary: [InstCombine] Support non-uniform constant vectors for
mul -> shl
   Product: libraries
   Version: trunk
  Hardware: PC
OS: Windows NT
Status: NEW
  Severity: enhancement
  Priority: P
 Component: Common Code Generator Code
  Assignee: unassignedb...@nondot.org
  Reporter: llvm-...@redking.me.uk
CC: david.majne...@gmail.com, efrie...@codeaurora.org,
llvm-bugs@lists.llvm.org, spatel+l...@rotateright.com

rL322072 demonstrates several cases where only scalars/uniform-vectors are
actually combined:

e.g.

define <2 x i17> @test2(<2 x i17> %X) {
; CHECK-LABEL: @test2(
; CHECK-NEXT:[[Y:%.*]] = shl <2 x i17> [[X:%.*]], 
; CHECK-NEXT:ret <2 x i17> [[Y]]
;
  %Y = mul <2 x i17> %X, 
  ret <2 x i17> %Y
}

define <2 x i17> @test3(<2 x i17> %X) {
; CHECK-LABEL: @test3(
; CHECK-NEXT:[[Y:%.*]] = mul <2 x i17> [[X:%.*]], 
; CHECK-NEXT:ret <2 x i17> [[Y]]
;
  %Y = mul <2 x i17> %X, 
  ret <2 x i17> %Y
}

It'd be very useful to support non-uniform vectors, possibly through a similar
approach to DAGCombine's matchUnaryPredicate/matchBinaryPredicate mechanism.

This is the tip of iceberg as most InstCombine patterns don't support
non-uniform vectors.

-- 
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 35873] New: misleading data sharing error message for const variable

2018-01-09 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=35873

Bug ID: 35873
   Summary: misleading data sharing error message for const
variable
   Product: OpenMP
   Version: unspecified
  Hardware: All
OS: All
Status: NEW
  Severity: normal
  Priority: P
 Component: Clang Compiler Support
  Assignee: unassignedclangb...@nondot.org
  Reporter: tras...@gmail.com
CC: llvm-bugs@lists.llvm.org

https://godbolt.org/g/X6XySq

void foo(const int rows)
{
#pragma omp parallel for default(none) firstprivate(rows)
for (int row = 0; row < rows; ++row)
{
}
}

$ clang-cl -Xclang -fopenmp -c test.cpp
test.cpp(4,26):  error: variable 'rows' must have explicitly specified data
sharing attributes

This is very misleading as rows _is_ specified.
It would be better to output something conveying "rows is shared because of
const".
gcc just accepts the code btw.

-- 
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 35872] New: Merge r322068 into the 6.0 branch: Fix type mismatch in omp_control_tool() implementation that makes it run incorrectly on 32-bit machines.

2018-01-09 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=35872

Bug ID: 35872
   Summary: Merge r322068 into the 6.0 branch: Fix type mismatch
in omp_control_tool() implementation that makes it run
incorrectly on 32-bit machines.
   Product: OpenMP
   Version: unspecified
  Hardware: PC
OS: Linux
Status: NEW
  Severity: release blocker
  Priority: P
 Component: Runtime Library
  Assignee: andrey.churba...@intel.com
  Reporter: hah...@hahnjo.de
CC: h...@chromium.org, llvm-bugs@lists.llvm.org,
pawel.osmialow...@foss.arm.com
Blocks: 35804

Andrey, Hans, is this ok to merge?


Referenced Bugs:

https://bugs.llvm.org/show_bug.cgi?id=35804
[Bug 35804] [meta] 6.0.0 Release Blockers
-- 
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 35871] New: AMDGPU some tests failed for openSUSE ppc64/ppc64le llvm5

2018-01-09 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=35871

Bug ID: 35871
   Summary: AMDGPU some tests failed for openSUSE ppc64/ppc64le
llvm5
   Product: libraries
   Version: 5.0
  Hardware: PC
OS: Linux
Status: NEW
  Severity: enhancement
  Priority: P
 Component: Backend: AMDGPU
  Assignee: unassignedb...@nondot.org
  Reporter: norm...@linux.vnet.ibm.com
CC: llvm-bugs@lists.llvm.org

Created attachment 19646
  --> https://bugs.llvm.org/attachment.cgi?id=19646=edit
llvm5_ppc64le_amdgpu_tests_failure.log.gz

AMDGPU some tests failed for openSUSE ppc64/ppc64le llvm5

as extracted from (1)
===
Failing Tests (12): 
LLVM :: CodeGen/AMDGPU/GlobalISel/amdgpu-irtranslator.ll 
LLVM :: CodeGen/AMDGPU/GlobalISel/inst-select-load-flat.mir  
LLVM :: CodeGen/AMDGPU/GlobalISel/inst-select-load-smrd.mir  
LLVM :: CodeGen/AMDGPU/GlobalISel/inst-select-store-flat.mir 
LLVM :: CodeGen/AMDGPU/GlobalISel/legalize-add.mir   
LLVM :: CodeGen/AMDGPU/GlobalISel/legalize-and.mir   
LLVM :: CodeGen/AMDGPU/GlobalISel/legalize-bitcast.mir   
LLVM :: CodeGen/AMDGPU/GlobalISel/legalize-constant.mir  
LLVM :: CodeGen/AMDGPU/GlobalISel/legalize-icmp.mir  
LLVM :: CodeGen/AMDGPU/GlobalISel/legalize-select.mir
LLVM :: CodeGen/AMDGPU/GlobalISel/legalize-shl.mir   
LLVM :: CodeGen/AMDGPU/GlobalISel/regbankselect.mir  

Expected Passes: 10448 
Expected Failures  : 47
Unsupported Tests  : 10925 
Unexpected Failures: 12  
===

(1)
https://build.opensuse.org/package/live_build_log/devel:tools:compiler/llvm5/openSUSE_Factory_PowerPC/ppc64le
same as attached llvm5_ppc64le_amdgpu_tests_failure.log.gz

-- 
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 35869] New: _mm_setzero_si64 violates the spec by generating xorps instead of pxor

2018-01-09 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=35869

Bug ID: 35869
   Summary: _mm_setzero_si64 violates the spec by generating xorps
instead of pxor
   Product: clang
   Version: trunk
  Hardware: PC
OS: All
Status: NEW
  Severity: enhancement
  Priority: P
 Component: C++
  Assignee: unassignedclangb...@nondot.org
  Reporter: gonzalob...@gmail.com
CC: dgre...@apple.com, llvm-bugs@lists.llvm.org

In the `` header, the intrinsic `__mm_setzero_si64` [0] implemented
as follows:

static __inline__ __m64 __DEFAULT_FN_ATTRS
_mm_setzero_si64(void)
{
return (__m64){ 0LL };
}

generates `xorps` [1] violating the spec [2] which says that it should generate
the instruction sequence `pxor mm, mm`.

[0]:
https://github.com/llvm-mirror/clang/blob/master/lib/Headers/mmintrin.h#L1296
[1]: https://godbolt.org/g/FnQYkf
[2]:
https://software.intel.com/sites/landingpage/IntrinsicsGuide/#text=_mm_setzero_si64=4727,4727

-- 
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 35868] New: Merge r321986 and r322041 into the 6.0 branch

2018-01-09 Thread via llvm-bugs 
https://bugs.llvm.org/show_bug.cgi?id=35868

Bug ID: 35868
   Summary: Merge r321986 and r322041 into the 6.0 branch
   Product: lld
   Version: unspecified
  Hardware: PC
OS: All
Status: NEW
  Severity: release blocker
  Priority: P
 Component: ELF
  Assignee: unassignedb...@nondot.org
  Reporter: dimi...@andric.com
CC: llvm-bugs@lists.llvm.org

Please merge r321986 and r322041 into the 6.0 branch for lld:
* r321986 fixes a thread race between SectionBase::getOffset() and
OutputSection::maybeCompress()
* r322041 fixes a possible hang due to reentrancy of paralellForEach.

Together these fix part of bug 35788 (there still is one thread race left,
though, but it is less critical).

-- 
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] Issue 5008 in oss-fuzz: llvm/llvm-isel-fuzzer--x86_64-O2: Abrt in llvm::llvm_unreachable_internal

2018-01-09 Thread ClusterFuzz-External via monorail via llvm-bugs 

Updates:
Labels: ClusterFuzz-Verified
Status: Verified

Comment #3 on issue 5008 by ClusterFuzz-External:  
llvm/llvm-isel-fuzzer--x86_64-O2: Abrt in llvm::llvm_unreachable_internal

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=5008#c3

ClusterFuzz testcase 394916122624 is verified as fixed, so closing  
issue as verified.


If this is incorrect, please file a bug on  
https://github.com/google/oss-fuzz/issues/new


--
You received this message because:
  1. You were specifically CC'd on the issue

You may adjust your notification preferences at:
https://bugs.chromium.org/hosting/settings

Reply to this email to add a comment.
___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

[llvm-bugs] Issue 5008 in oss-fuzz: llvm/llvm-isel-fuzzer--x86_64-O2: Abrt in llvm::llvm_unreachable_internal

2018-01-09 Thread ClusterFuzz-External via monorail via llvm-bugs 


Comment #2 on issue 5008 by ClusterFuzz-External:  
llvm/llvm-isel-fuzzer--x86_64-O2: Abrt in llvm::llvm_unreachable_internal

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=5008#c2

ClusterFuzz has detected this issue as fixed in range  
201801080609:201801082049.


Detailed report: https://oss-fuzz.com/testcase?key=394916122624

Project: llvm
Fuzzer: libFuzzer_llvm_llvm-isel-fuzzer--x86_64-O2
Fuzz target binary: llvm-isel-fuzzer--x86_64-O2
Job Type: libfuzzer_asan_llvm
Platform Id: linux

Crash Type: Abrt
Crash Address: 0x0001
Crash State:
  llvm::llvm_unreachable_internal
  matchMinMaxOfMinMax
  matchSelectPattern

Sanitizer: address (ASAN)

Regressed:  
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm=201801020611:201801030610
Fixed:  
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm=201801080609:201801082049


Reproducer Testcase:  
https://oss-fuzz.com/download?testcase_id=394916122624


See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for  
more information.


If you suspect that the result above is incorrect, try re-doing that job on  
the test case report page.


--
You received this message because:
  1. You were specifically CC'd on the issue

You may adjust your notification preferences at:
https://bugs.chromium.org/hosting/settings

Reply to this email to add a comment.
___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs