[llvm-bugs] Issue 4729 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-instcombine: ASSERT: !isNonNegative() && "Can't make a non-negative value negative"

2017-12-29 Thread ClusterFuzz-External via monorail via llvm-bugs


Comment #2 on issue 4729 by ClusterFuzz-External:  
llvm/llvm-opt-fuzzer--x86_64-instcombine: ASSERT: !isNonNegative()  
&& "Can't make a non-negative value negative"

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

ClusterFuzz has detected this issue as fixed in range  
201712280611:201712282031.


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

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

Crash Type: ASSERT
Crash Address:
Crash State:
  !isNonNegative() && "Can't make a non-negative value negative"
  llvm::KnownBits::makeNegative
  computeKnownBitsFromAssume

Sanitizer: address (ASAN)

Regressed:  
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201712190608:201712210617
Fixed:  
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201712280611:201712282031


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


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


[llvm-bugs] Issue 4788 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-instcombine: ASSERT: isa(Val) && "cast() argument of incompatible type!"

2017-12-29 Thread ClusterFuzz-External via monorail via llvm-bugs


Comment #3 on issue 4788 by ClusterFuzz-External:  
llvm/llvm-opt-fuzzer--x86_64-instcombine: ASSERT: isa(Val)  
&& "cast() argument of incompatible type!"

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

ClusterFuzz has detected this issue as fixed in range  
201712280611:201712282031.


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

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

Crash Type: ASSERT
Crash Address:
Crash State:
  isa(Val) && "cast() argument of incompatible type!"
  llvm::InstCombiner::visitCallInst
  llvm::InstCombiner::run

Sanitizer: address (ASAN)

Regressed:  
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201711130743:201711140614
Fixed:  
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201712280611:201712282031


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


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


[llvm-bugs] Issue 4729 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-instcombine: ASSERT: !isNonNegative() && "Can't make a non-negative value negative"

2017-12-29 Thread ClusterFuzz-External via monorail via llvm-bugs

Updates:
Labels: ClusterFuzz-Verified
Status: Verified

Comment #3 on issue 4729 by ClusterFuzz-External:  
llvm/llvm-opt-fuzzer--x86_64-instcombine: ASSERT: !isNonNegative()  
&& "Can't make a non-negative value negative"

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

ClusterFuzz testcase 5896781238894592 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 4788 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-instcombine: ASSERT: isa(Val) && "cast() argument of incompatible type!"

2017-12-29 Thread ClusterFuzz-External via monorail via llvm-bugs

Updates:
Labels: ClusterFuzz-Verified
Status: Verified

Comment #4 on issue 4788 by ClusterFuzz-External:  
llvm/llvm-opt-fuzzer--x86_64-instcombine: ASSERT: isa(Val)  
&& "cast() argument of incompatible type!"

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

ClusterFuzz testcase 6319261761929216 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] [Bug 35771] New: [AMDGPU][MC][GFX9] Enable inline constants for SDWA operands

2017-12-29 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=35771

Bug ID: 35771
   Summary: [AMDGPU][MC][GFX9] Enable inline constants for SDWA
operands
   Product: libraries
   Version: trunk
  Hardware: PC
OS: All
Status: NEW
  Severity: enhancement
  Priority: P
 Component: Backend: AMDGPU
  Assignee: unassignedb...@nondot.org
  Reporter: dpreobrazhen...@luxoft.com
CC: llvm-bugs@lists.llvm.org

SDWA should enable inline constants as operands. SP3 seems to support these.

An example of a valid test:

v_sub_f32_sdwa v5, -4.0, v2 dst_sel:DWORD dst_unused:UNUSED_PAD src0_sel:DWORD
src1_sel:DWORD

-- 
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 35772] New: Function pointer to __declspec(dllimport) function not constant in /std:c++latest, works in /std:c++14

2017-12-29 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=35772

Bug ID: 35772
   Summary: Function pointer to __declspec(dllimport) function not
constant in /std:c++latest, works in /std:c++14
   Product: clang
   Version: 5.0
  Hardware: PC
OS: Windows NT
Status: NEW
  Severity: enhancement
  Priority: P
 Component: C++
  Assignee: unassignedclangb...@nondot.org
  Reporter: jva...@gmail.com
CC: dgre...@apple.com, llvm-bugs@lists.llvm.org

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

The following code compiles with MSVC2015 (/std:c++14), MSVC2017 (/std:c++17),
Clang-cl 5.0 /std:c++14 though fails to compile with Clang-cl 5.0
/std:c++latest (c++17)

__declspec(dllimport) int toInt(int i);

namespace {
template
struct A {};
}

int main(int, char **)
{
   A a{};
   return 0;
}

As soon as the __declspec(dllimport) is removed, the code compiles again.
This issue seems to be the only problem we are encountering upgrading to
MSVC2017 (/std:c++17) and keeping Clang-cl as alternative for parsing.

-- 
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 35688] PowerPC backend crashes when printing assembly

2017-12-29 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=35688

Nemanja Ivanovic  changed:

   What|Removed |Added

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

--- Comment #12 from Nemanja Ivanovic  ---
The fix was committed in r321551.

-- 
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 35773] New: clang crashes at -O2 and above: : Assertion `!hasVectorValue(Key, Part) && "Vector value already set for part"' failed.

2017-12-29 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=35773

Bug ID: 35773
   Summary: clang crashes at -O2 and above: : Assertion
`!hasVectorValue(Key, Part) && "Vector value already
set for part"' failed.
   Product: clang
   Version: trunk
  Hardware: PC
OS: All
Status: NEW
  Severity: enhancement
  Priority: P
 Component: LLVM Codegen
  Assignee: unassignedclangb...@nondot.org
  Reporter: helloqi...@gmail.com
CC: llvm-bugs@lists.llvm.org

$ clang-trunk -v
clang version 6.0.0 (trunk 321550)
Target: x86_64-unknown-linux-gnu
Thread model: posix
InstalledDir: /usr/local/bin


$ clang-trunk -O2 abc.c
abc.c:6:19: warning: unsequenced modification and access to 'c' [-Wunsequenced]
(b += c) > (c += 9);
  ~   ^
abc.c:6:14: warning: relational comparison result unused [-Wunused-comparison]
(b += c) > (c += 9);
~^~
clang-6.0: /home/absozero/trunk/llvm/lib/Transforms/Vectorize/VPlan.h:167: void
llvm::VectorizerValueMap::setVectorValue(llvm::Value*, unsigned int,
llvm::Value*): Assertion `!hasVectorValue(Key, Part) && "Vector value already
set for part"' failed.
#0 0x0216e94a llvm::sys::PrintStackTrace(llvm::raw_ostream&)
(/home/absozero/trunk/root-clang/bin/clang-6.0+0x216e94a)
#1 0x0216c7ee llvm::sys::RunSignalHandlers()
(/home/absozero/trunk/root-clang/bin/clang-6.0+0x216c7ee)
#2 0x0216c942 SignalHandler(int)
(/home/absozero/trunk/root-clang/bin/clang-6.0+0x216c942)
#3 0x7f31803c9330 __restore_rt
(/lib/x86_64-linux-gnu/libpthread.so.0+0x10330)
#4 0x7f317ef46c37 gsignal
/build/eglibc-oGUzwX/eglibc-2.19/signal/../nptl/sysdeps/unix/sysv/linux/raise.c:56:0
#5 0x7f317ef4a028 abort
/build/eglibc-oGUzwX/eglibc-2.19/stdlib/abort.c:91:0
#6 0x7f317ef3fbf6 __assert_fail_base
/build/eglibc-oGUzwX/eglibc-2.19/assert/assert.c:92:0
#7 0x7f317ef3fca2 (/lib/x86_64-linux-gnu/libc.so.6+0x2fca2)
#8 0x0228ba0d llvm::VectorizerValueMap::setVectorValue(llvm::Value*,
unsigned int, llvm::Value*)
(/home/absozero/trunk/root-clang/bin/clang-6.0+0x228ba0d)
#9 0x022af04e
llvm::InnerLoopVectorizer::recordVectorLoopValueForInductionCast(llvm::InductionDescriptor
const&, llvm::Value*, unsigned int, unsigned int)
(/home/absozero/trunk/root-clang/bin/clang-6.0+0x22af04e)
#10 0x022af2cc
llvm::InnerLoopVectorizer::createVectorIntOrFpInductionPHI(llvm::InductionDescriptor
const&, llvm::Value*, llvm::Instruction*)
(/home/absozero/trunk/root-clang/bin/clang-6.0+0x22af2cc)
#11 0x022a
llvm::InnerLoopVectorizer::widenIntOrFpInduction(llvm::PHINode*,
llvm::TruncInst*) (/home/absozero/trunk/root-clang/bin/clang-6.0+0x22a)
#12 0x022df2a2 llvm::VPBasicBlock::execute(llvm::VPTransformState*)
(/home/absozero/trunk/root-clang/bin/clang-6.0+0x22df2a2)
#13 0x022e072d llvm::VPlan::execute(llvm::VPTransformState*)
(/home/absozero/trunk/root-clang/bin/clang-6.0+0x22e072d)
#14 0x0229fe3e
llvm::LoopVectorizationPlanner::executePlan(llvm::InnerLoopVectorizer&,
llvm::DominatorTree*) (/home/absozero/trunk/root-clang/bin/clang-6.0+0x229fe3e)
#15 0x022acb3e llvm::LoopVectorizePass::processLoop(llvm::Loop*)
(/home/absozero/trunk/root-clang/bin/clang-6.0+0x22acb3e)
#16 0x022ad927 llvm::LoopVectorizePass::runImpl(llvm::Function&,
llvm::ScalarEvolution&, llvm::LoopInfo&, llvm::TargetTransformInfo&,
llvm::DominatorTree&, llvm::BlockFrequencyInfo&, llvm::TargetLibraryInfo*,
llvm::DemandedBits&, llvm::AAResults&, llvm::AssumptionCache&,
std::function&,
llvm::OptimizationRemarkEmitter&)
(/home/absozero/trunk/root-clang/bin/clang-6.0+0x22ad927)
#17 0x022adfad (anonymous
namespace)::LoopVectorize::runOnFunction(llvm::Function&)
(/home/absozero/trunk/root-clang/bin/clang-6.0+0x22adfad)
#18 0x01c851c3 llvm::FPPassManager::runOnFunction(llvm::Function&)
(/home/absozero/trunk/root-clang/bin/clang-6.0+0x1c851c3)
#19 0x01c8528c llvm::FPPassManager::runOnModule(llvm::Module&)
(/home/absozero/trunk/root-clang/bin/clang-6.0+0x1c8528c)
#20 0x01c84d5d llvm::legacy::PassManagerImpl::run(llvm::Module&)
(/home/absozero/trunk/root-clang/bin/clang-6.0+0x1c84d5d)
#21 0x0232c2ae clang::EmitBackendOutput(clang::DiagnosticsEngine&,
clang::HeaderSearchOptions const&, clang::CodeGenOptions const&,
clang::TargetOptions const&, clang::LangOptions const&, llvm::DataLayout
const&, llvm::Module*, clang::BackendAction,
std::unique_ptr >)
(/home/absozero/trunk/root-clang/bin/clang-6.0+0x232c2ae)
#22 0x02b6c017
clang::BackendConsumer::HandleTranslationUnit(clang::ASTContext&)
(/home/absozero/trunk/root-clang/bin/clang-6.0+0x2b6c017)
#23 0x02d4d3b8 clang::ParseAST(clang::Sema&, bool, bool)
(/home/absozero/trunk/root-clang/bin/clang-6.0+0x2d4d3b8)
#24 0x02b6b3cc clang::CodeGenAction::ExecuteAction()
(/home/absozero/trunk/root-clang/bin/clang

[llvm-bugs] [Bug 34686] [X86][SSE] extra pshufhw generated in simple shuffle code

2017-12-29 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=34686

Simon Pilgrim  changed:

   What|Removed |Added

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

--- Comment #3 from Simon Pilgrim  ---
rL321553

-- 
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 35774] New: "Simplify the CFG" pass moves musttail call from tail position

2017-12-29 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=35774

Bug ID: 35774
   Summary: "Simplify the CFG" pass moves musttail call from tail
position
   Product: libraries
   Version: 5.0
  Hardware: PC
OS: Linux
Status: NEW
  Severity: normal
  Priority: P
 Component: Transformation Utilities
  Assignee: unassignedb...@nondot.org
  Reporter: ben...@gmail.com
CC: llvm-bugs@lists.llvm.org

Created attachment 19611
  --> https://bugs.llvm.org/attachment.cgi?id=19611&action=edit
Files mentioned in the description

The attached file `musttail.ll` branches before making a call. The callee is
the same in both branches, but it is a non-tail call in one branch and a
`musttail` call in the other. The optimizer mistakenly merges the two calls
into a single one before the branch, resulting in incorrect output. Running
`clang -O1 -S -emit-llvm musttail.ll -o musttail_O1.ll` produces an attached
malformed file which is rejected by `llc` for containing a `musttail` call in
non-tail position. I have also attached the output of `opt -O1 -S
-print-after-all musttail.ll`.

-- 
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 35775] New: libllvm5.0:amd64 changelog file conflicts with libllvm5.0:i386

2017-12-29 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=35775

Bug ID: 35775
   Summary: libllvm5.0:amd64 changelog file conflicts with
libllvm5.0:i386
   Product: Packaging
   Version: unspecified
  Hardware: PC
OS: Linux
Status: NEW
  Severity: normal
  Priority: P
 Component: deb packages
  Assignee: unassignedb...@nondot.org
  Reporter: abo...@systemsaviour.com
CC: llvm-bugs@lists.llvm.org

On a Debian Stretch multiarch system with both i386 and amd64
llvm-toolchain-stretch-5.0 packages installed, upgrading now gives the
following error:

$ sudo apt-get dist-upgrade
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
  libllvm5.0 libllvm5.0:i386
2 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/28.5 MB of archives.
After this operation, 2,048 B of additional disk space will be used.
Do you want to continue? [Y/n] 
Retrieving bug reports... Done
Parsing Found/Fixed information... Done
Reading changelogs... Done
(Reading database ... 739971 files and directories currently installed.)
Preparing to unpack .../libllvm5.0_1%3a5.0.1~svn319952-1~exp1_amd64.deb ...
Unpacking libllvm5.0:amd64 (1:5.0.1~svn319952-1~exp1) over
(1:5.0.1~svn319952-1~exp1) ...
dpkg: error processing archive
/var/cache/apt/archives/libllvm5.0_1%3a5.0.1~svn319952-1~exp1_amd64.deb
(--unpack):
 trying to overwrite shared '/usr/share/doc/libllvm5.0/changelog.Debian.gz',
which is different from other instances of package libllvm5.0:amd64
Preparing to unpack .../libllvm5.0_1%3a5.0.1~svn319952-1~exp1_i386.deb ...
Unpacking libllvm5.0:i386 (1:5.0.1~svn319952-1~exp1) over
(1:5.0.1~svn319952-1~exp1) ...
dpkg: error processing archive
/var/cache/apt/archives/libllvm5.0_1%3a5.0.1~svn319952-1~exp1_i386.deb
(--unpack):
 trying to overwrite shared '/usr/share/doc/libllvm5.0/changelog.Debian.gz',
which is different from other instances of package libllvm5.0:i386
Errors were encountered while processing:
 /var/cache/apt/archives/libllvm5.0_1%3a5.0.1~svn319952-1~exp1_amd64.deb
 /var/cache/apt/archives/libllvm5.0_1%3a5.0.1~svn319952-1~exp1_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (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