[llvm-bugs] [Bug 37267] SROA.cpp:2567: bool llvm::sroa::AllocaSliceRewriter::rewriteIntegerStore(llvm::Value *, llvm::StoreInst &, llvm::AAMDNodes): Assertion `BeginOffset >= NewAllocaBeginOffset && "

2018-05-16 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=37267

Hiroshi Inoue  changed:

   What|Removed |Added

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

--- Comment #2 from Hiroshi Inoue  ---
Patch committed.
https://reviews.llvm.org/rL332575

-- 
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 37473] objcopy and strip get rid of the GNU_RELRO program header for binaries produced by lld

2018-05-16 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=37473

Peter Collingbourne  changed:

   What|Removed |Added

 CC||pe...@pcc.me.uk
 Status|NEW |RESOLVED
 Resolution|--- |INVALID

--- Comment #3 from Peter Collingbourne  ---
The bug is in GNU strip and has been fixed:
https://sourceware.org/bugzilla/show_bug.cgi?id=22829

You can either upgrade your binutils or switch to another strip tool such as
elfutils or llvm-strip.

-- 
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 7698 in oss-fuzz: llvm/llvm-dwarfdump-fuzzer: Heap-buffer-overflow in llvm::DataExtractor::getU16

2018-05-16 Thread j… via monorail via llvm-bugs


Comment #2 on issue 7698 by j...@chromium.org: llvm/llvm-dwarfdump-fuzzer:  
Heap-buffer-overflow in llvm::DataExtractor::getU16

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

This is a WASM file.

--
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 7167 in oss-fuzz: llvm/llvm-dwarfdump-fuzzer: Abrt in llvm::llvm_unreachable_internal

2018-05-16 Thread j… via monorail via llvm-bugs


Comment #2 on issue 7167 by j...@chromium.org: llvm/llvm-dwarfdump-fuzzer:  
Abrt in llvm::llvm_unreachable_internal

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

Doesn't repro for me on MacOS:

/Users/jfb/Downloads/clusterfuzz-testcase-minimized-llvm-dwarfdump-fuzzer-5729224427044864.dms:  
No  
available targets are compatible with this triple.
/Users/jfb/Downloads/clusterfuzz-testcase-minimized-llvm-dwarfdump-fuzzer-5729224427044864.dms:	 
file  
format ELF32-unknown


.debug_info contents:
Process 57451 exited with status = 0 (0x)

--
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 6697 in oss-fuzz: llvm/llvm-dwarfdump-fuzzer: Heap-buffer-overflow in llvm::StringMapImpl::LookupBucketFor

2018-05-16 Thread j… via monorail via llvm-bugs


Comment #2 on issue 6697 by j...@chromium.org: llvm/llvm-dwarfdump-fuzzer:  
Heap-buffer-overflow in llvm::StringMapImpl::LookupBucketFor

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

This is a WASM file.

--
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 4619 in oss-fuzz: llvm/llvm-dwarfdump-fuzzer: Abrt in llvm::llvm_unreachable_internal

2018-05-16 Thread j… via monorail via llvm-bugs


Comment #7 on issue 4619 by j...@chromium.org: llvm/llvm-dwarfdump-fuzzer:  
Abrt in llvm::llvm_unreachable_internal

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

Doesn't report for me. Tip-of-tree LLVM with debug build on MacOS:

error: failed to decompress '(', corrupted compressed section header
error: failed to decompress '(', corrupted compressed section header
/Users/jfb/Downloads/clusterfuzz-testcase-minimized-llvm-dwarfdump-fuzzer-6647657620570112.dms:  
No  
available targets are compatible with this triple.
/Users/jfb/Downloads/clusterfuzz-testcase-minimized-llvm-dwarfdump-fuzzer-6647657620570112.dms:	 
file  
format ELF32-unknown


.debug_info contents:
Process 57335 exited with status = 0 (0x)

--
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 3822 in oss-fuzz: llvm/llvm-dwarfdump-fuzzer: Out-of-memory in llvm_llvm-dwarfdump-fuzzer

2018-05-16 Thread j… via monorail via llvm-bugs


Comment #8 on issue 3822 by j...@chromium.org: llvm/llvm-dwarfdump-fuzzer:  
Out-of-memory in llvm_llvm-dwarfdump-fuzzer

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

Doesn't repro for me, using MacOS with tip-of-tree LLVM build, in debug:

clusterfuzz-testcase-minimized-llvm-dwarfdump-fuzzer-5718235874852864.dms:  
Invalid data was encountered while parsing the file


--
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 3236 in oss-fuzz: llvm: Abrt in llvm::report_bad_alloc_error

2018-05-16 Thread j… via monorail via llvm-bugs


Comment #13 on issue 3236 by j...@chromium.org: llvm: Abrt in  
llvm::report_bad_alloc_error

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

I think this is fixed. Could it be that the fuzz checker isn't working? Or  
running into another issue?


On MacOS I get:

$ ./debug/bin/llvm-dwarfdump  
~/Downloads/clusterfuzz-testcase-minimized-llvm-dwarfdump-fuzzer-5674959462465536.dms


llvm-dwarfdump(56868,0x7fffab9a0380) malloc: ***  
mach_vm_map(size=2314885530818457600) failed (error code=3)

*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
LLVM ERROR: out of memory


--
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 15425] clang crashes with partial specialization and defaulted template parameter

2018-05-16 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=15425

Kohei Takahashi  changed:

   What|Removed |Added

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

--- Comment #3 from Kohei Takahashi  ---
I confirmed it had been fixed in 3.4 release.
https://wandbox.org/permlink/OpHVtNE76cWxPc11

-- 
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 36649] [meta] 6.0.1 Release Blockers

2018-05-16 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=36649
Bug 36649 depends on bug 37374, which changed state.

Bug 37374 Summary: Merge r323053 into the 6.0 branch : [cmake] Don't build 
Native llvm-config when cross compiling if passed by user.
https://bugs.llvm.org/show_bug.cgi?id=37374

   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 37374] Merge r323053 into the 6.0 branch : [cmake] Don't build Native llvm-config when cross compiling if passed by user.

2018-05-16 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=37374

Tom Stellard  changed:

   What|Removed |Added

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

--- Comment #4 from Tom Stellard  ---
Merged: r332568

-- 
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 37493] Merge r327354 into the 6.0 branch : Add missing "env" so that test added in r327322 passes on Windows bots.

2018-05-16 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=37493

Tom Stellard  changed:

   What|Removed |Added

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

--- Comment #2 from Tom Stellard  ---
Merged: r332566

-- 
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 36649] [meta] 6.0.1 Release Blockers

2018-05-16 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=36649
Bug 36649 depends on bug 37493, which changed state.

Bug 37493 Summary: Merge r327354 into the 6.0 branch : Add missing "env" so 
that test added in r327322 passes on Windows bots.
https://bugs.llvm.org/show_bug.cgi?id=37493

   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 37493] New: Merge r327354 into the 6.0 branch : Add missing "env" so that test added in r327322 passes on Windows bots.

2018-05-16 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=37493

Bug ID: 37493
   Summary: Merge r327354 into the 6.0 branch : Add missing "env"
so that test added in r327322 passes on Windows bots.
   Product: new-bugs
   Version: 6.0
  Hardware: All
OS: All
Status: NEW
  Severity: enhancement
  Priority: P
 Component: new bugs
  Assignee: unassignedb...@nondot.org
  Reporter: tstel...@redhat.com
CC: llvm-bugs@lists.llvm.org
Blocks: 36649

Is it OK to merge the following revision(s) to the 6.0 branch?


Referenced Bugs:

https://bugs.llvm.org/show_bug.cgi?id=36649
[Bug 36649] [meta] 6.0.1 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 37492] New: Type merging in some PDBs results in bad pointer typedefs

2018-05-16 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=37492

Bug ID: 37492
   Summary: Type merging in some PDBs results in bad pointer
typedefs
   Product: lld
   Version: unspecified
  Hardware: PC
OS: Windows NT
Status: NEW
  Severity: enhancement
  Priority: P
 Component: COFF
  Assignee: unassignedb...@nondot.org
  Reporter: amcca...@google.com
CC: llvm-bugs@lists.llvm.org

The type records for some typedefs, like `std::vector::const_pointer`, sometimes do not have the correct pointee type.  It
should be `const unsigned char`, but it's a bitfield.  Similar problem for
`const_reference` and `std::array`.

Discovered in the webview.dll.pdb from a debug Chrome build.

You can observe the problem by running `llvm-pdbutil pretty -types
webview.dll.pdb`, which will effective assert on the bad type.  If you use
`dump -types`, you can manually follow the type IDs to an `LF_BITFIELD`.

This does not happen for all PDBs.

Here are some excerpts to illustrate:

```
0x3E25 | LF_CLASS [size = 124] `std::vector >`
 unique name: `.?AV?$vector@EV?$allocator@E@std@@@std@@`
 vtable: , base list: , field list: 0x3E24
 options: contains nested class | has unique name
```

If we look in the field list for 0x3E24, we find:

```
- LF_NESTTYPE [name = `const_pointer`, parent = 0x27F1]
```

Following the parent:

```
0x27F1 | LF_POINTER [size = 12]
 referent = 0x22C6, mode = pointer, opts = None, kind = ptr32
```

And finally, the referent leads to:

```
0x22C6 | LF_BITFIELD [size = 12]
 type = 0x0020 (unsigned char), bit offset = 0, # bits = 1
```

-- 
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 24487] clang fails to compile linux "ALTERNATIVE" (integrated-as)

2018-05-16 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=24487

Bill Wendling  changed:

   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 4068] [Meta] Compiling the Linux kernel with clang

2018-05-16 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=4068
Bug 4068 depends on bug 24487, which changed state.

Bug 24487 Summary: clang fails to compile linux  "ALTERNATIVE"  (integrated-as)
https://bugs.llvm.org/show_bug.cgi?id=24487

   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 37488] wasm32: Codegen bug at O2 for llc

2018-05-16 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=37488

Dan Gohman  changed:

   What|Removed |Added

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

--- Comment #1 from Dan Gohman  ---
This turned out to be a copy+pasto; i64.load16_u was getting encoded with
i64.load16_s's opcode. Fixed in r332561.

-- 
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 36649] [meta] 6.0.1 Release Blockers

2018-05-16 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=36649
Bug 36649 depends on bug 37480, which changed state.

Bug 37480 Summary: Merge rr328408 into the 6.0 branch : Add REQUIRES lines for 
the targets being checked in this test.
https://bugs.llvm.org/show_bug.cgi?id=37480

   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 37480] Merge rr328408 into the 6.0 branch : Add REQUIRES lines for the targets being checked in this test.

2018-05-16 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=37480

Tom Stellard  changed:

   What|Removed |Added

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

--- Comment #2 from Tom Stellard  ---
Merged: r332552

-- 
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 37491] New: Please merge 332444 into 6.0.1

2018-05-16 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=37491

Bug ID: 37491
   Summary: Please merge 332444 into 6.0.1
   Product: new-bugs
   Version: 6.0
  Hardware: PC
OS: Linux
Status: NEW
  Severity: enhancement
  Priority: P
 Component: new bugs
  Assignee: unassignedb...@nondot.org
  Reporter: manojgu...@google.com
CC: llvm-bugs@lists.llvm.org, peter.sm...@linaro.org,
t.p.northo...@gmail.com
Blocks: 36649

https://reviews.llvm.org/rL332444

This adds supports for "S" constraint on AArch64 which is needed to build Linux
kernel.


Referenced Bugs:

https://bugs.llvm.org/show_bug.cgi?id=36649
[Bug 36649] [meta] 6.0.1 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 37490] New: Merge r330788 into the 6.0 branch : Bring r329960 back.

2018-05-16 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=37490

Bug ID: 37490
   Summary: Merge r330788 into the 6.0 branch : Bring r329960
back.
   Product: new-bugs
   Version: 6.0
  Hardware: All
OS: All
Status: NEW
  Severity: enhancement
  Priority: P
 Component: new bugs
  Assignee: unassignedb...@nondot.org
  Reporter: tstel...@redhat.com
CC: llvm-bugs@lists.llvm.org
Blocks: 36649

Is it OK to merge the following revision(s) to the 6.0 branch?


Referenced Bugs:

https://bugs.llvm.org/show_bug.cgi?id=36649
[Bug 36649] [meta] 6.0.1 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 37453] assertion in emitting wasm dwarf debug info

2018-05-16 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=37453

Derek Schuff  changed:

   What|Removed |Added

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

--- Comment #2 from Derek Schuff  ---
With r332517 this should be fixed. Please reopen if not.

-- 
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 37441] [X86] Suboptimal lowering of lshr/ashr <4 x i32> for non-AVX2

2018-05-16 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=37441

Simon Pilgrim  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|ASSIGNED|RESOLVED
 Fixed By Commit(s)||332524

--- Comment #3 from Simon Pilgrim  ---
Fixed in rL332524

-- 
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 37409] Writing WASM obj file with debug information fails at writeObject

2018-05-16 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=37409

Sam Clegg  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 37483] clang++ CUDA miscompile with -O1

2018-05-16 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=37483

Artem Belevich  changed:

   What|Removed |Added

 Resolution|--- |WONTFIX
 Status|NEW |RESOLVED

--- Comment #2 from Artem Belevich  ---
I can reproduce it on sm_60.

Jonas appears to be correct and that's a problem with ptxas in CUDA-8.
PTX generated by clang is identical for both CUDA-8 and CUDA-9.
However, SASS generated by ptxas is noticeably different. With CUDA-9
the code is very straightforward and you can see two writes, 8 bytes apart,
both with the same value. With CUDA-8, func3 messes up the store to *l_302 and
writes zero to the should_not_change field instead.

ptxas in cuda-8 is known to have number of unfixed issues. So does ptxas in
older cuda-9.x releases. I would suggest updating to more recent CUDA version
or, consider replacing ptxas with the one from CUDA-9.1 (though you will not be
able to compile for sm_20 if you do)

-- 
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 26115] [Inliner] Callee with single call instruction not being inlined

2018-05-16 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=26115

Chad Rosier  changed:

   What|Removed |Added

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

--- Comment #1 from Chad Rosier  ---
This was fixed as some point.

-- 
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 37477] Assertion "!is_error()" failed at polly/lib/External/isl/include/isl/isl-noexceptions.h:66

2018-05-16 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=37477

Michael Kruse  changed:

   What|Removed |Added

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

--- Comment #3 from Michael Kruse  ---
Fixed in r332488.

-- 
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 25592] [dagcombine] redundant 'and' of phi node not removed during isel

2018-05-16 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=25592

Chad Rosier  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|NEW |RESOLVED
 CC||mcros...@codeaurora.org

--- Comment #1 from Chad Rosier  ---
Committed in r253722: [CodeGenPrepare] Create more extloads and fewer ands.

-- 
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 25591] [AArch64] - i1 zextloads marked as legal; requires workaround in CodeGenPrepare::optimizeLoadExt

2018-05-16 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=25591

Chad Rosier  changed:

   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 37488] New: wasm32: Codegen bug at O2 for llc

2018-05-16 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=37488

Bug ID: 37488
   Summary: wasm32: Codegen bug at O2 for llc
   Product: libraries
   Version: trunk
  Hardware: PC
OS: Windows NT
Status: NEW
  Severity: enhancement
  Priority: P
 Component: Backend: WebAssembly
  Assignee: unassignedb...@nondot.org
  Reporter: a...@crichton.co
CC: llvm-bugs@lists.llvm.org

Created attachment 20310
  --> https://bugs.llvm.org/attachment.cgi?id=20310&action=edit
IR

Originally reported at https://github.com/rust-lang/rust/issues/50754 I've
reduced the test case to a smaller piece of Rust code
(https://gist.github.com/4b0396c7599d3b15dadc2c82f62b624e) which at `-C
opt-level=2` for the Rust compiler generates the attached IR.

When the attached IR is compiled to a wasm object file with O0 it generates a
different answer than when generated with O2:


$ llc bar.ll -filetype=obj -O0 -o bar.o
$ wasm-ld bar.o -o bar.wasm --no-entry
$ node bar.js
0
$ llc bar.ll -filetype=obj -O2 -o bar.o
$ wasm-ld bar.o -o bar.wasm --no-entry
$ node bar.js
65534

where `bar.js` looks like:

const fs = require('fs');
let buf = fs.readFileSync('bar.wasm');
let m = new WebAssembly.Module(buf);
let inst = new WebAssembly.Instance(m, {});
console.log(inst.exports.test());

I unfortunately haven't been able to track this down much farther, but I was
hoping that y'all could help me reduce from here!

-- 
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 36901] [DAGCombiner] visitBRCOND() leads to UNREACHABLE: "Operand not processed?"

2018-05-16 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=36901

Nirav Dave  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] Issue 6504 in oss-fuzz: llvm/clang-format-fuzzer: Stack-overflow in clang::format::AnnotatingParser::parseAngle

2018-05-16 Thread sheriff… via monorail via llvm-bugs

Updates:
Labels: Deadline-Approaching

Comment #2 on issue 6504 by sheriff...@chromium.org:  
llvm/clang-format-fuzzer: Stack-overflow in  
clang::format::AnnotatingParser::parseAngle

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

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 6515 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-gvn: ASSERT: (VTy->isFirstClassType() || VTy->isVoidTy() || VTy->isStructTy()) && "invalid Ca

2018-05-16 Thread sheriff… via monorail via llvm-bugs

Updates:
Labels: Deadline-Approaching

Comment #2 on issue 6515 by sheriff...@chromium.org:  
llvm/llvm-opt-fuzzer--x86_64-gvn: ASSERT: (VTy->isFirstClassType() ||  
VTy->isVoidTy() || VTy->isStructTy()) && "invalid Ca

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

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 37487] New: Using std::__throw_bad_weak_ptr can produce invalid RTTI for std::runtime_error

2018-05-16 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=37487

Bug ID: 37487
   Summary: Using std::__throw_bad_weak_ptr can produce invalid
RTTI for std::runtime_error
   Product: clang
   Version: unspecified
  Hardware: Macintosh
OS: MacOS X
Status: NEW
  Severity: enhancement
  Priority: P
 Component: C++
  Assignee: unassignedclangb...@nondot.org
  Reporter: davidcape...@gmail.com
CC: dgre...@apple.com, llvm-bugs@lists.llvm.org

If we compile a .cpp file with -frtti which throws std::runtime_error and
catches std::exception&, but then we compile another file with -fno-rtti that
uses std::__throw_bad_weak_ptr() in some way and we link both files in one
binary, the final std::runtime_error class is not identified as a derived class
of std::exception (so the catch code is not executed).

Here is a minimal example of this case:
https://gist.github.com/dacap/7ddffbe401eb42620de397e47edfcc76

clang --version
Apple LLVM version 9.1.0 (clang-902.0.39.1)
Target: x86_64-apple-darwin17.5.0
Thread model: posix
InstalledDir:
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin

-- 
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 36295] symbol version "has undefined version error" when all symbols with version are hidden.

2018-05-16 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=36295

Peter Smith  changed:

   What|Removed |Added

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

--- Comment #4 from Peter Smith  ---
D43126 was committed r332224 . This should resolve the PR.

-- 
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 37458] llvm.launder.invariant.group results in miscompile of store-to-load forwarding case

2018-05-16 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=37458

Krzysztof Pszeniczny  changed:

   What|Removed |Added

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

--- Comment #4 from Krzysztof Pszeniczny  ---
This has been fixed in rL332466.

-- 
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 37486] New: lli fails to build with GCC 8

2018-05-16 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=37486

Bug ID: 37486
   Summary: lli fails to build with GCC 8
   Product: libraries
   Version: 5.0
  Hardware: PC
OS: Linux
Status: NEW
  Severity: enhancement
  Priority: P
 Component: OrcJIT
  Assignee: unassignedb...@nondot.org
  Reporter: valentin.korenb...@smile.fr
CC: llvm-bugs@lists.llvm.org

I'm working with llvm-5.0.1.src.tar.xz, using gcc 8.1.1 under Fedora 28:

Error message:

In file included from
/home/naourr/work/instance-2/output/build/host-llvm-5.0.1/tools/lli/lli.cpp:30:
/home/naourr/work/instance-2/output/build/host-llvm-5.0.1/include/llvm/ExecutionEngine/Orc/OrcRemoteTargetClient.h:
In member function 'llvm::Expected >
llvm::orc::remote::OrcRemoteTargetClient::readMem(char*,
llvm::JITTargetAddress, uint64_t)':
/home/naourr/work/instance-2/output/build/host-llvm-5.0.1/include/llvm/ExecutionEngine/Orc/OrcRemoteTargetClient.h:722:26:
error: could not convert
'((llvm::orc::remote::OrcRemoteTargetClient*)this)->callB(Src,
Size)' from 'Expected>>' to
'Expected>>'
 return callB(Src, Size);


Full log: 

http://autobuild.buildroot.net/results/824c70e982d8ec7e518cf4db058767df42db6b04/build-end.log

-- 
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 37485] New: LLDB reads wrong registers on 64bit Windows

2018-05-16 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=37485

Bug ID: 37485
   Summary: LLDB reads wrong registers on 64bit Windows
   Product: lldb
   Version: 6.0
  Hardware: PC
OS: Windows NT
Status: NEW
  Severity: enhancement
  Priority: P
 Component: All Bugs
  Assignee: lldb-...@lists.llvm.org
  Reporter: kenji.koyan...@gmail.com
CC: llvm-bugs@lists.llvm.org

LLDB reads wrong registers on 64bit Windows because
RegisterContextWindows_x64::GetRegisterInfoAtIndex returns wrong reference.
I encountered broken backtrace when the program stopped at function which does
not have prologue code, such as compiled with '-fomit-frame-pointer'.
In this situation, CFA is equal to rsp but LLDB reads r9.

I investigated the cause.
RegisterContextWindows_x64::GetRegisterInfoAtIndex depends the order of
lldb_XXX_x86_64 values, but RegisterIndex/g_register_infos/g_gpr_reg_indices
does not follow order.

In source/Plugins/Process/Utility/lldb-x86-register-enums.h
The order of GPRs is rax, rbx, rcx, rdx, rdi, rsi, rbp, rsp, r8, ...

In source/Plugins/Process/Windows/Common/x64/RegisterContextWindows_x64.cpp
The order of GPRs is rax, rbx, rcx, rdx, rdi, rsi, r8, r9, r10, ...

I am using is what I built by myself on MinGW.

-- 
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 37484] New: src/experimental/filesystem/directory_iterator.cpp:98: suspicious call to strcmp

2018-05-16 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=37484

Bug ID: 37484
   Summary: src/experimental/filesystem/directory_iterator.cpp:98:
suspicious call to strcmp
   Product: libc++
   Version: unspecified
  Hardware: PC
OS: Linux
Status: NEW
  Severity: normal
  Priority: P
 Component: All Bugs
  Assignee: unassignedclangb...@nondot.org
  Reporter: dcb...@hotmail.com
CC: llvm-bugs@lists.llvm.org, mclow.li...@gmail.com

libcxx/src/experimental/filesystem/directory_iterator.cpp:98]: (warning) The
expression 'strcmp(__data_.cFileName,"..") != 0' is suspicious. It overlaps
'!strcmp(__data_.cFileName,".")'.

Source code is

  if (!strcmp(__data_.cFileName, ".") || strcmp(__data_.cFileName, ".."))
continue;

Maybe better code

  if (strcmp(__data_.cFileName, ".") == 0 || strcmp(__data_.cFileName, "..") ==
0)
continue;

-- 
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 37483] New: clang++ CUDA miscompile with -O1

2018-05-16 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=37483

Bug ID: 37483
   Summary: clang++ CUDA miscompile with -O1
   Product: new-bugs
   Version: 6.0
  Hardware: PC
OS: Linux
Status: NEW
  Severity: enhancement
  Priority: P
 Component: new bugs
  Assignee: unassignedb...@nondot.org
  Reporter: wangxy...@buaa.edu.cn
CC: llvm-bugs@lists.llvm.org

Created attachment 20309
  --> https://bugs.llvm.org/attachment.cgi?id=20309&action=edit
test case that trigger the bug

I have encountered a miscompile for cuda program with clang 6.0 , with
optimization '-O1'and disappear with '-O2' and '-O3'.
I have reduced the test-case appended below,

demo.cu
#include "cuda_runtime.h"
#include "device_launch_parameters.h"
#include "cuda.h"

#include 

struct S1 {
long shoud_not_change;
long irrelevant;
};

__device__ int * func_3(int ** p_221, struct S1 * ptr_arg)
{
long *l_302 = &ptr_arg->irrelevant;
(*l_302) = 0;
return *p_221;
}

__device__ void func_2(struct S1 * ptr_arg)
{
int *l_231 = (int*)0;
func_3(&l_231, ptr_arg);
}


__device__ void func_1(struct S1 * ptr_arg)
{
func_2(ptr_arg);
}

extern "C" __global__ void entry(long *result)
{
struct S1 c_783 = {
11L, // shoud_not_change  
0L, // irrelevant
};
result[0] = (long)c_783.shoud_not_change;
struct S1* ptr_arg = &c_783;
__syncthreads();
func_1(ptr_arg);
__syncthreads();
result[1] = (long)ptr_arg->shoud_not_change;
}
int main(void)
{
long h_result[2];
long* result;
size_t result_size = sizeof(long)*2;
cudaMalloc((void**)&result,result_size);
entry<<<100,100>>>(result);
cudaMemcpy(&h_result,result,result_size,cudaMemcpyDeviceToHost);
printf("result[0] is %ld, result[1] is %ld\n", h_result[0], h_result[1]);

}
--
The failing and passing behaviors are:
-
FAIL
$clang++ demo.cu -O1 -o bug --cuda-gpu-arch=sm_50 
--cuda-path=/usr/local/cuda-8.0 
-I/usr/local/cuda-8.0/targets/x86_64-linux/include/  -L/usr/local/cuda/lib64
-lcudart -lcuda

$./bug

output:result[0] is 11, result[1] is 0
-
PASS
$clang++ demo.cu -O2 -o bugfree-O2 --cuda-gpu-arch=sm_50 
--cuda-path=/usr/local/cuda-8.0 
-I/usr/local/cuda-8.0/targets/x86_64-linux/include/  -L/usr/local/cuda/lib64
-lcudart -lcuda

$./bugfree-O2

output:result[0] is 11, result[1] is 11
---
PASS
$clang++ demo.cu -O3 -o bugfree-O3 --cuda-gpu-arch=sm_50 
--cuda-path=/usr/local/cuda-8.0 
-I/usr/local/cuda-8.0/targets/x86_64-linux/include/  -L/usr/local/cuda/lib64
-lcudart -lcuda

$./bugfree-O3

output:result[0] is 11, result[1] is 11
--



Configuration->
--
#uname -a
Linux G1024-workstation1 4.4.0-121-generic #145-Ubuntu SMP Fri Apr 13 13:47:23
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
--
$ clang++ --version
clang version 6.0.0 (tags/RELEASE_600/final)
Target: x86_64-unknown-linux-gnu
Thread model: posix
InstalledDir: /usr/bin
---
cat /etc/*release*/
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.2 LTS"
NAME="Ubuntu"
VERSION="16.04.2 LTS (Xenial Xerus)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 16.04.2 LTS"
VERSION_ID="16.04"
HOME_URL="http://www.ubuntu.com/";
SUPPORT_URL="http://help.ubuntu.com/";
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/";
VERSION_CODENAME=xenial
UBUNTU_CODENAME=xenial
Device: NVIDIA Quadro K2200
---
#nvidia-smi
Wed May 16 15:07:23 2018   
+-+
| NVIDIA-SMI 384.111Driver Version: 384.111   |
|---+--+--+
| GPU  NamePersistence-M| Bus-IdDisp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap| Memory-Usage | GPU-Util  Compute M. |
|===+==+==|
|   0  Quadro K2200Off  | :03:00.0 Off |  N/A |
| 42%   52CP0 2W /  39W |  0MiB /  4040MiB |  0%  Default |
+---+--+--+

+---

[llvm-bugs] [Bug 37482] New: Condition that leads to __builtin_unreachable() is not propagated to other branches

2018-05-16 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=37482

Bug ID: 37482
   Summary: Condition that leads to __builtin_unreachable() is not
propagated to other branches
   Product: new-bugs
   Version: trunk
  Hardware: PC
OS: Linux
Status: NEW
  Severity: enhancement
  Priority: P
 Component: new bugs
  Assignee: unassignedb...@nondot.org
  Reporter: sergei.a.izmai...@gmail.com
CC: llvm-bugs@lists.llvm.org

Clang is unable to optimize the next code: 

#include 
const double& safe_deref(double* a) {
if (a==nullptr) { // expansion of GSL Ensures macro with
GSL_UNENFORCED_ON_CONTRACT_VIOLATION
 __builtin_unreachable();
}
if (a==nullptr) { 
throw std::runtime_error("error");
}
return *a;
}

GCC optimize out both "if" statements, see https://godbolt.org/g/4hSgAA

-- 
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