[llvm-bugs] Issue 10686 in oss-fuzz: llvm/llvm-special-case-list-fuzzer: Timeout in llvm_llvm-special-case-list-fuzzer
Comment #2 on issue 10686 by ClusterFuzz-External: llvm/llvm-special-case-list-fuzzer: Timeout in llvm_llvm-special-case-list-fuzzer https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=10686#c2 ClusterFuzz has detected this issue as fixed in range 201810060232:201810070231. Detailed report: https://oss-fuzz.com/testcase?key=5199973671501824 Project: llvm Fuzzer: libFuzzer_llvm_llvm-special-case-list-fuzzer Fuzz target binary: llvm-special-case-list-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Timeout (exceeds 25 secs) Crash Address: Crash State: llvm_llvm-special-case-list-fuzzer Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201711070608:201711090621 Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201810060232:201810070231 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5199973671501824 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 10686 in oss-fuzz: llvm/llvm-special-case-list-fuzzer: Timeout in llvm_llvm-special-case-list-fuzzer
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #3 on issue 10686 by ClusterFuzz-External: llvm/llvm-special-case-list-fuzzer: Timeout in llvm_llvm-special-case-list-fuzzer https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=10686#c3 ClusterFuzz testcase 5199973671501824 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 39207] New: Loop hoisting
https://bugs.llvm.org/show_bug.cgi?id=39207
Bug ID: 39207
Summary: Loop hoisting
Product: libraries
Version: trunk
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: Loop Optimizer
Assignee: unassignedb...@nondot.org
Reporter: david.bolvan...@gmail.com
CC: llvm-bugs@lists.llvm.org
Not sure how often this happens in the real world apps but anyway idea is..
int foo(void)
{
double *array = calloc(ARRAY_SIZE, sizeof(double));
double sum = 0;
int i;
for (i = 0; i < N_TIMES; i++) {
// lot of code
// well, this loop does not even depend on "i", hoist it?
for (int j = 0; j < ARRAY_SIZE; j += 8) {
sum += array[j] + array[j+1] + array[j+2] + array[j+3] + array[j+4]
+ array[j+5] + array[j+6] + array[j+7];
}
}
return sum;
}
Let's say we have the big outer loop with many inner loops. Can LLVM check if
these loops really depend on the outer loop and if not, hoist them?
--
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 10250 in oss-fuzz: llvm: Build failure
Comment #8 on issue 10250 by ClusterFuzz-External: llvm: Build failure https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=10250#c8 Friendly reminder that the the build is still failing. Please try to fix this failure to ensure that fuzzing remains productive. Latest build log: https://oss-fuzz-build-logs.storage.googleapis.com/log-66d766a8-444b-4315-91a0-9a9187ec93d5.txt -- 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 39208] New: IMAGE_SUPPORT macro should not be automatically defined for spir
https://bugs.llvm.org/show_bug.cgi?id=39208 Bug ID: 39208 Summary: IMAGE_SUPPORT macro should not be automatically defined for spir Product: clang Version: trunk Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: OpenCL Assignee: unassignedclangb...@nondot.org Reporter: omer.paparo.bi...@intel.com CC: llvm-bugs@lists.llvm.org, yaxun@amd.com The differential revision https://reviews.llvm.org/D40252 introduced an automatic definition of the macro IMAGE_SUPPORT when "spir" or "spir64" is present in the triple, forcing that macro to be present. I'm working on a non-published device which follows the 1.2 spec and does not support images (i.e. when queried using https://www.khronos.org/registry/OpenCL/sdk/1.2/docs/man/xhtml/clGetDeviceInfo.html for CL_DEVICE_IMAGE_SUPPORT it returns false). spir is my default target, and when compiling the IMAGE_SUPPORT is defined although the device does not support images. This causes some conformance tests to fail, most notably the test "kernel_preprocessor_macros" from the basic suite, with the message "FAILURE: __IMAGE_SUPPORT__ defined to value 1 even though images aren't supported". I believe that this macro should not be added in the manner it is done today. -- 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 39209] New: std::uniform_int_distribution erroneously rejects generator values
https://bugs.llvm.org/show_bug.cgi?id=39209 Bug ID: 39209 Summary: std::uniform_int_distribution erroneously rejects generator values Product: libc++ Version: 6.0 Hardware: All OS: All Status: NEW Severity: normal Priority: P Component: All Bugs Assignee: unassignedclangb...@nondot.org Reporter: l...@christoph-conrads.name CC: llvm-bugs@lists.llvm.org, mclow.li...@gmail.com Created attachment 20974 --> https://bugs.llvm.org/attachment.cgi?id=20974&action=edit Demonstration of bug Given a generator returning values in the interval [0, r] and `std::uniform_int_distribution(0, b)`, let r,b such that r+1 multiple of b+1. In this case `std::uniform_int_distribution` may erroneously reject generator values although no rejection sampling is needed. In the demonstration program in the attachment, r=19, b=9 so that half of all generator values are rejected. The bug does not occur if r+1 and b+1 are powers of two. Note that the GNU C++ Library contains a similar bug: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80977 $ clang++ --version clang version 6.0.1 (tags/RELEASE_601/final) Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/lib/llvm/6/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 39210] New: [AVR] uint32_t is incorrectly compiled to i16
https://bugs.llvm.org/show_bug.cgi?id=39210
Bug ID: 39210
Summary: [AVR] uint32_t is incorrectly compiled to i16
Product: clang
Version: 7.0
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P
Component: Headers
Assignee: unassignedclangb...@nondot.org
Reporter: aykevanlaet...@gmail.com
CC: llvm-bugs@lists.llvm.org
When compiling this function for avr:
#include
uint32_t size32() {
return 3;
}
With the following options:
clang-7 --target=avr-atmel-none -emit-llvm -S -o intsize.ll -c intsize.c
I get the following IR (cut down to the essential parts):
target datalayout = "e-P1-p:16:8-i8:8-i16:8-i32:8-i64:8-f32:8-f64:8-n8-a:8"
target triple = "avr-atmel-none"
; Function Attrs: noinline nounwind optnone
define dso_local i16 @size32() #0 {
ret i16 3
}
In other words, uint32_t is compiled to i16 instead of i32 as it should.
I hit this problem while trying to build compiler-rt for AVR and hitting lots
of "shift count >= width of type" warnings which are probably caused by this
problem.
I'm running Debian stable (stretch) with clang-7 from apt.llvm.org.
--
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 10849 in oss-fuzz: llvm/llvm-isel-fuzzer--x86_64-O2: ASSERT: isValidElementType(ElementType) && "Element type of a VectorType must " "be an i
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com, igm...@gmail.com, eney...@google.com, llvm-b...@lists.llvm.org, j...@chromium.org, v...@apple.com, mitchphi...@outlook.com, xpl...@gmail.com, akils...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible Engine-libfuzzer Proj-llvm Reported-2018-10-07 Type: Bug New issue 10849 by ClusterFuzz-External: llvm/llvm-isel-fuzzer--x86_64-O2: ASSERT: isValidElementType(ElementType) && "Element type of a VectorType must " "be an i https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=10849 Detailed report: https://oss-fuzz.com/testcase?key=5678889012035584 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: isValidElementType(ElementType) && "Element type of a VectorType must " "be an i llvm::VectorType::get BitcodeReader::parseModule Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201710160455:201710190451 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5678889012035584 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 need to contact the OSS-Fuzz team with a question, concern, or any other feedback, 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 39210] [AVR] uint32_t is incorrectly compiled to i16
https://bugs.llvm.org/show_bug.cgi?id=39210 Ayke van Laethem changed: What|Removed |Added Resolution|--- |INVALID Status|NEW |RESOLVED --- Comment #2 from Ayke van Laethem --- Yeah, I was just about to post a comment saying I found the issue (that it includes /usr/include/stdint.h from the host). With -nostdlibinc this problem appears to be fixed. Maybe it's an idea to add this option to https://clang.llvm.org/docs/CrossCompilation.html? Offtopic: with this extra flag most of compiler-rt compiles (some files still report an invalid shift count), however it doesn't seem to work well and not all required functions are implemented so I'll keep using libgcc for now. -- 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 39160] Assertion failure /home/mkazantsev/work/llvm/include/llvm/IR/Instructions.h:3123: llvm::Value* llvm::PHINode::getIncomingValueForBlock(const llvm::BasicBlock*) const: Assertion
https://bugs.llvm.org/show_bug.cgi?id=39160 Max Kazantsev changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #12 from Max Kazantsev --- Fixed by https://reviews.llvm.org/rL343954 -- 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 39211] New: clang crashed with SIGSEGV in llvm:ManagedStaticBase::destroy()
https://bugs.llvm.org/show_bug.cgi?id=39211 Bug ID: 39211 Summary: clang crashed with SIGSEGV in llvm:ManagedStaticBase::destroy() Product: clang Version: 6.0 Hardware: PC OS: Linux Status: NEW Severity: normal Priority: P Component: -New Bugs Assignee: unassignedclangb...@nondot.org Reporter: doublem...@qq.com CC: llvm-bugs@lists.llvm.org Created attachment 20975 --> https://bugs.llvm.org/attachment.cgi?id=20975&action=edit compile file,dmesg.txt,file created by ltrace and strace. System details: ubuntu 18.04 linux 4.15.0-34.37-generic 4.15.18 clang 6.0 Bug details: when compile one c file with "-Xclang -load -Xclang" option to load a custom llvm-pass.so, clang crash with eip point to an unexpected address. StackTrace ??() ??() from /usr/lib/llvm-6.0/bin/../lib/libLLVM-6.0.so.1 llvm::ManagedStaticBase:destroy() const() from /usr/lib/llvm-6.0/bin/../lib/libLLVM-6.0.so.1 llvm::llvm_shutdown() () from /usr/lib/llvm-6.0/bin/../lib/libLLVM-6.0.s0.1 main() Compile cmd: clang -Xclang -load -Xclang llvm-pass.so test-instr.c -o test-instr Check the attachment with trace log and compiled file. -- 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
