[llvm-bugs] [Bug 39885] lld does not link clang-compiled openmp code that uses -fopenmp-targets option
https://bugs.llvm.org/show_bug.cgi?id=39885 George Rimar changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #4 from George Rimar --- The first issue fixed in r348463. The second is duplicate of https://bugs.llvm.org/show_bug.cgi?id=39434, so I am closing this 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 39901] New: clobbered return value from this-adjustment thunk returning a member pointer
https://bugs.llvm.org/show_bug.cgi?id=39901
Bug ID: 39901
Summary: clobbered return value from this-adjustment thunk
returning a member pointer
Product: clang
Version: trunk
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: LLVM Codegen
Assignee: unassignedclangb...@nondot.org
Reporter: h...@chromium.org
CC: llvm-bugs@lists.llvm.org, neeil...@live.com,
richard-l...@metafoo.co.uk
Consider the following example, targeting 32-bit x86:
struct X;
typedef void (X::*memptr)();
struct A {
virtual memptr f();
};
struct B {
virtual memptr f();
};
struct C : A, B {
C();
memptr f() override __attribute__((noinline)) { return nullptr; };
};
C::C() {}
$ clang -cc1 -triple i686 -emit-llvm -o - a.cc -O3
[...]
define linkonce_odr void @_ZThn4_N1C1fEv({ i32, i32 }* noalias sret
%agg.result, %struct.C* %this) unnamed_addr #1 comdat align 2 {
entry:
%tmp = alloca { i32, i32 }, align 4
%0 = getelementptr inbounds %struct.C, %struct.C* %this, i32 -1, i32 1
%1 = bitcast %struct.B* %0 to %struct.C*
tail call void @_ZN1C1fEv({ i32, i32 }* nonnull sret %tmp, %struct.C* nonnull
%1)
ret void
}
Note that the sret value from @_ZN1C1fEv gets dropped!
The -O0 IR looks like this:
define linkonce_odr void @_ZThn4_N1C1fEv({ i32, i32 }* noalias sret
%agg.result, %struct.C* %this) unnamed_addr #0 comdat align 2 {
entry:
%retval = alloca { i32, i32 }, align 4
%this.addr = alloca %struct.C*, align 4
%tmp = alloca { i32, i32 }, align 4
store %struct.C* %this, %struct.C** %this.addr, align 4
%this1 = load %struct.C*, %struct.C** %this.addr, align 4
%0 = bitcast %struct.C* %this1 to i8*
%1 = getelementptr inbounds i8, i8* %0, i32 -4
%2 = bitcast i8* %1 to %struct.C*
tail call void @_ZN1C1fEv({ i32, i32 }* sret %tmp, %struct.C* %2)
%3 = load { i32, i32 }, { i32, i32 }* %tmp, align 4
store { i32, i32 } %3, { i32, i32 }* %retval, align 4
%4 = load { i32, i32 }, { i32, i32 }* %retval, align 4
store { i32, i32 } %4, { i32, i32 }* %agg.result, align 4
ret void
}
Note that the thunk is passing its %tmp alloca into the tail-called function.
That's not allowed: a tail-call function is not supposed to access alloca's
from the caller. Because of that, the subsequent copy from %tmp to %agg.result
gets optimized away.
Interestingly, this doesn't happen for all sret values, such as a regular
struct. I could only reproduce with a member pointer.
--
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 39902] New: Complex double passed as an argument in c uses a spill and ldc1 rather than a pair of mtc1/mthc1 on mips32r2
https://bugs.llvm.org/show_bug.cgi?id=39902
Bug ID: 39902
Summary: Complex double passed as an argument in c uses a spill
and ldc1 rather than a pair of mtc1/mthc1 on mips32r2
Product: libraries
Version: trunk
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: Backend: MIPS
Assignee: unassignedb...@nondot.org
Reporter: cassandra.l.mcc...@gmail.com
CC: llvm-bugs@lists.llvm.org
Compiling the following code snippet using clang results in the arguments
spilling to the stack and the using ldc1 rather than a pair of mtc1/mthc1 on
mips32r2 with -mfp32.
The exact flags used during compilation -O3 -target mipsel -S -march=mips32r2
-ffast-math -mfp32 -mtune=mips32r2
#include
complex double __attribute((noinline)) square(complex double c)
{
return c * c;
}
Note that the same is true for the opposite, when calling a function like this
the fp registers are spilled to memory and then loaded back into the argument
registers.
--
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 39903] New: Vectorization generates unaligned moves for properly aligned data
https://bugs.llvm.org/show_bug.cgi?id=39903 Bug ID: 39903 Summary: Vectorization generates unaligned moves for properly aligned data Product: clang Version: trunk Hardware: PC OS: All Status: NEW Severity: enhancement Priority: P Component: LLVM Codegen Assignee: unassignedclangb...@nondot.org Reporter: jamesma...@gmail.com CC: llvm-bugs@lists.llvm.org, neeil...@live.com, richard-l...@metafoo.co.uk Created attachment 21198 --> https://bugs.llvm.org/attachment.cgi?id=21198&action=edit Code that shows the problem in compiler explorer. A simple FMA loop operating on data that is aligned with `alignas(64)` is generating `vmovups` instructions when it could, and should, be generating `vmovaps`. Since the nehalem architecture the cost of a `vmovups` relative to `vmovaps` is not as large as it once was, but it is noticeable and if the data is guaranteed to be aligned, then `vmovaps` should be the instruction used. https://www.godbolt.org/z/CCcjYu -- 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 39904] New: Ubuntu 16.04 TGZ release: clang segmentation fault in versions >=5.0.2 with `-debug-info-kind=limited`
https://bugs.llvm.org/show_bug.cgi?id=39904 Bug ID: 39904 Summary: Ubuntu 16.04 TGZ release: clang segmentation fault in versions >=5.0.2 with `-debug-info-kind=limited` Product: clang Version: 5.0 Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: -New Bugs Assignee: unassignedclangb...@nondot.org Reporter: ka...@vaghefi.org CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org, neeil...@live.com, richard-l...@metafoo.co.uk We run clang in a docker container based on Ubuntu 16.04. In it we download the tar.xz archive for clang, place it in /opt, and symlink it in using `update-alternatives` (here's the line from our Dockerfile) RUN export CLANG_VERSION=5.0.1 && \ export CLANG_PKG=clang+llvm-$CLANG_VERSION-x86_64-linux-gnu-ubuntu-16.04 && \ wget --progress=bar:force http://llvm.org/releases/$CLANG_VERSION/$CLANG_PKG.tar.xz && \ tar xvfJ $CLANG_PKG.tar.xz -C /opt && \ chmod -R 755 /opt/$CLANG_PKG && \ # make symlinks to abstract compiler version update-alternatives --install /usr/bin/clang clang /opt/$CLANG_PKG/bin/clang 100 \ --slave /usr/bin/clang++ clang++ /opt/$CLANG_PKG/bin/clang++ \ --slave /usr/bin/llvm-symbolizer llvm-symbolizer /opt/$CLANG_PKG/bin/llvm-symbolizer \ --slave /usr/bin/llvm-profdata llvm-profdata /opt/$CLANG_PKG/bin/llvm-profdata\ --slave /usr/bin/llvm-ar llvm-ar /opt/$CLANG_PKG/bin/llvm-ar \ --slave /usr/bin/lld lld /opt/$CLANG_PKG/bin/lld \ --slave /usr/bin/llvm-nm llvm-nm /opt/$CLANG_PKG/bin/llvm-nm \ --slave /usr/bin/llvm-objdump llvm-objdump /opt/$CLANG_PKG/bin/llvm-objdump \ --slave /usr/bin/clang-format clang-format /opt/$CLANG_PKG/bin/clang-format \ --slave /usr/bin/llvm-ranlib llvm-ranlib /opt/$CLANG_PKG/bin/llvm-ranlib \ --slave /lib/libc++.so libc++.so /opt/$CLANG_PKG/lib/libc++.so \ --slave /lib/libc++.so.1 libc++.so.1 /opt/$CLANG_PKG/lib/libc++.so.1 \ --slave /lib/libc++.so.1.0 libc++.so.1.0 /opt/$CLANG_PKG/lib/libc++.so.1.0 \ --slave /lib/libc++abi.so libc++abi.so /opt/$CLANG_PKG/lib/libc++abi.so \ --slave /lib/libc++abi.so.1 libc++abi.so.1 /opt/$CLANG_PKG/lib/libc++abi.so.1 \ --slave /lib/libc++abi.so.1.0 libc++abi.so.1.0 /opt/$CLANG_PKG/lib/libc++abi.so.1.0 \ --slave /lib/libomp.so libomp.so /opt/$CLANG_PKG/lib/libomp.so I'm finding that if I use any version after 5.0.1, clang exhibits a segmentation fault with the `-g` option passed in. If I remove the `-debug-info-kind=limited` command on the invocation below, the segmentation fault does not happen. I believe this is a bug that needs to be fixed, but I'd appreciate the insight of someone more knowledgable with clang. It seems to be like more recent versions might be built without the option for ZLIB compression enabled. $ /opt/clang+llvm-5.0.2-x86_64-linux-gnu-ubuntu-16.04/bin/clang-5.0 \ -cc1 \ -triple x86_64-unknown-linux-gnu \ -emit-obj \ --compress-debug-sections \ -disable-free \ -disable-llvm-verifier \ -discard-value-names \ -main-file-name buildinfo_query.cc \ -mrelocation-model static \ -mthread-model posix \ -mdisable-fp-elim \ -fmath-errno \ -masm-verbose \ -mconstructor-aliases \ -munwind-tables \ -fuse-init-array \ -target-cpu x86-64 \ -momit-leaf-frame-pointer \ -dwarf-column-info \ -debug-info-kind=limited \ -dwarf-version=4 \ -debugger-tuning=gdb \ -coverage-notes-file /proc/self/cwd/bazel-out/k8-py3-opt/bin/devtools/_objs/buildinfo_query/devtools/buildinfo_query.gcno \ -resource-dir /opt/clang+llvm-5.0.2-x86_64-linux-gnu-ubuntu-16.04/lib/clang/5.0.2 \ -dependency-file bazel-out/k8-py3-opt/bin/devtools/_objs/buildinfo_query/devtools/buildinfo_query.d \ -MT bazel-out/k8-py3-opt/bin/devtools/_objs/buildinfo_query/devtools/buildinfo_query.o \ -sys-header-deps \ -iquote . \ -iquote bazel-out/k8-py3-opt/genfiles \ -iquote external/bazel_tools \ -iquote bazel-out/k8-py3-opt/genfiles/external/bazel_tools \ -isystem external/bazel_tools/tools/cpp/gcc3 \ -D NDEBUG \ -internal-isystem /opt/clang+llvm-5.0.2-x86_64-linux-gnu-ubuntu-16.04/bin/../include/c++/v1 \ -internal-isystem /usr/local/include \ -internal-isystem /opt/clang+llvm-5.0.2-x86_64-linux-gnu-ubuntu-16.04/lib/clang/5.0.2/include \ -internal-externc-isystem /usr/include/x86_64-linux-gnu \ -internal-externc-isystem /usr/include \ -O3 \ -Wthread-safety \ -Wno-unknown-pragmas \ -Wno-inconsistent-missing-override \ -Wno-deprecated-register \ -Werror \ -Wno-sign-compare \ -Wno-invalid-partial-specialization \ -std=c++1z \ -fdeprecated-macro \ -fdebug-compilation-dir /proc/self/cwd \ -ferror-limit 19 \ -fmessage-length 0 \ -fopenmp \ -fobjc-runtime=gcc \ -fcxx-exceptions \ -fexceptions \ -fdiagnostics-show-option \ -vectorize-loops \ -vectorize-slp \ -o bazel-out/k8-py3-opt/bin/devtools/_objs/buildinfo_query/
[llvm-bugs] Issue 11773 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-indvars: Timeout in llvm_llvm-opt-fuzzer--x86_64-indvars
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 Reproducible Engine-libfuzzer Proj-llvm Reported-2018-12-06 Type: Bug New issue 11773 by ClusterFuzz-External: llvm/llvm-opt-fuzzer--x86_64-indvars: Timeout in llvm_llvm-opt-fuzzer--x86_64-indvars https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=11773 Detailed report: https://oss-fuzz.com/testcase?key=5720985035079680 Project: llvm Fuzzer: libFuzzer_llvm_llvm-opt-fuzzer--x86_64-indvars Fuzz target binary: llvm-opt-fuzzer--x86_64-indvars Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Timeout (exceeds 25 secs) Crash Address: Crash State: llvm_llvm-opt-fuzzer--x86_64-indvars Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201802210603:201802211531 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5720985035079680 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 39172] [NVPTX] Wrong results or hang on GPU when using lastprivate() on SPMD construct with full runtime
https://bugs.llvm.org/show_bug.cgi?id=39172 Alexey Bataev changed: What|Removed |Added Status|NEW |RESOLVED Fixed By Commit(s)||r345991, r345978 Resolution|--- |FIXED --- Comment #2 from Alexey Bataev --- 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 39905] New: Merge r340125 into 7.0.1
https://bugs.llvm.org/show_bug.cgi?id=39905 Bug ID: 39905 Summary: Merge r340125 into 7.0.1 Product: new-bugs Version: 7.0 Hardware: PC OS: All Status: NEW Severity: release blocker Priority: P Component: new bugs Assignee: unassignedb...@nondot.org Reporter: s...@continuum.io CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org Blocks: 39106 Hope this is not too late. It took our team a while to isolate the problem. r340125 fixes allocation for common symbols in loading object code. The bug is doubling the allocation size per symbol and it will request way too much memory with a few dozens of common symbols. We are seeing it trying to allocating >64GB of memory. Referenced Bugs: https://bugs.llvm.org/show_bug.cgi?id=39106 [Bug 39106] [meta] 7.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] Issue 11774 in oss-fuzz: llvm/llvm-isel-fuzzer--x86_64-O2: ASSERT: (DeferredFunctionInfo[Fn] == 0 || DeferredFunctionInfo[Fn] == CurBit) && "Mismat
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-12-06 Type: Bug New issue 11774 by ClusterFuzz-External: llvm/llvm-isel-fuzzer--x86_64-O2: ASSERT: (DeferredFunctionInfo[Fn] == 0 || DeferredFunctionInfo[Fn] == CurBit) && "Mismat https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=11774 Detailed report: https://oss-fuzz.com/testcase?key=5755537006788608 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: (DeferredFunctionInfo[Fn] == 0 || DeferredFunctionInfo[Fn] == CurBit) && "Mismat BitcodeReader::rememberAndSkipFunctionBody 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=5755537006788608 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 39873] Merge r348181 into the 7.0 branch : [InstCombine] foldICmpWithLowBitMaskedVal(): disable 2 faulty folds.
https://bugs.llvm.org/show_bug.cgi?id=39873 Tom Stellard changed: What|Removed |Added Fixed By Commit(s)|r348181 r348461 r348462 |r348181 r348461 r348462 ||r348528 r348535 r348538 Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #4 from Tom Stellard --- Merged: r348528 r348535 r348538 -- 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 39106] [meta] 7.0.1 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=39106 Bug 39106 depends on bug 39873, which changed state. Bug 39873 Summary: Merge r348181 into the 7.0 branch : [InstCombine] foldICmpWithLowBitMaskedVal(): disable 2 faulty folds. https://bugs.llvm.org/show_bug.cgi?id=39873 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] Issue 11775 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-earlycse: Abrt in llvm-opt-fuzzer.cpp
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-12-06 Type: Bug New issue 11775 by ClusterFuzz-External: llvm/llvm-opt-fuzzer--x86_64-earlycse: Abrt in llvm-opt-fuzzer.cpp https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=11775 Detailed report: https://oss-fuzz.com/testcase?key=5681380671881216 Project: llvm Fuzzer: libFuzzer_llvm_llvm-opt-fuzzer--x86_64-earlycse Fuzz target binary: llvm-opt-fuzzer--x86_64-earlycse Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Abrt Crash Address: 0x0001 Crash State: llvm-opt-fuzzer.cpp Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201801240651:201801250632 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5681380671881216 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 39173] Merge r340386 into the 7.0 branch
https://bugs.llvm.org/show_bug.cgi?id=39173 Tom Stellard changed: What|Removed |Added Fixed By Commit(s)|r340386 r344190 |r340386 r344190 r348554 Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #7 from Tom Stellard --- Merged: r348554 -- 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 39106] [meta] 7.0.1 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=39106 Bug 39106 depends on bug 39173, which changed state. Bug 39173 Summary: Merge r340386 into the 7.0 branch https://bugs.llvm.org/show_bug.cgi?id=39173 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 39905] Merge r340125 into 7.0.1
https://bugs.llvm.org/show_bug.cgi?id=39905 Tom Stellard changed: What|Removed |Added Fixed By Commit(s)|r340125 |r340125 r348555 Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #4 from Tom Stellard --- Merged: r348555 -- 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 39106] [meta] 7.0.1 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=39106 Bug 39106 depends on bug 39905, which changed state. Bug 39905 Summary: Merge r340125 into 7.0.1 https://bugs.llvm.org/show_bug.cgi?id=39905 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] Issue 11776 in oss-fuzz: llvm/clang-fuzzer: Stack-overflow in GetFullTypeForDeclarator
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-12-07 Type: Bug New issue 11776 by ClusterFuzz-External: llvm/clang-fuzzer: Stack-overflow in GetFullTypeForDeclarator https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=11776 Detailed report: https://oss-fuzz.com/testcase?key=5765470997708800 Project: llvm Fuzzer: libFuzzer_llvm_clang-fuzzer Fuzz target binary: clang-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Stack-overflow Crash Address: 0x7ffc0cfb4eb8 Crash State: GetFullTypeForDeclarator clang::Sema::GetTypeForDeclarator clang::Sema::ActOnBlockArguments Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201812050231:201812060233 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5765470997708800 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 39906] New: Cannot build builtins on ARMv6 (unsupported instructions)
https://bugs.llvm.org/show_bug.cgi?id=39906 Bug ID: 39906 Summary: Cannot build builtins on ARMv6 (unsupported instructions) Product: compiler-rt Version: unspecified Hardware: Other OS: Linux Status: NEW Severity: normal Priority: P Component: builtins Assignee: unassignedb...@nondot.org Reporter: lizar...@gmail.com CC: llvm-bugs@lists.llvm.org Created attachment 21199 --> https://bugs.llvm.org/attachment.cgi?id=21199&action=edit Build log for gcc and clang and Dockerfile Compiler-rt cannot be built on ARMv6 architectures such as ARM1176JZF-S, there are some memory barrier instructions in `compiler-rt/lib/builtins/arm/sync-ops.h` that are not supported (namely `dmb`). This means it can't be truly build for Raspbian or on a Raspberry Pi, but the error occurs also when trying to cross compile with `-march=armv6`. Indeed the library `libclang_rt.builtins-armhf.a` is completely missing from Raspbian (package `libclang-common-3.8-dev`). I also found that the problem has already been mentioned in the llvm-dev mailing list at http://lists.llvm.org/pipermail/llvm-dev/2016-May/099780.html. I'm attaching the logfile of the errors when building `compiler-rt/lib/builtins/arm/sync_fetch_and_add_4.S` on a Raspberry Pi with Raspbian Stretch (kernel 4.14.79+) both with gcc (Raspbian 6.3.0-18+rpi1+deb9u1) 6.3.0 20170516 and clang (version 3.8.1-24+rpi1 tags/RELEASE_381/final). I am also attaching a Dockerfile which tries to cross-compile compiler-rt for armv6, and also triggers the same error. On the ARM1176JZF-S with Raspbian, I cloned the release 7.0 of llvm and compiler-rt, and then ran `cmake` with no extra define. I ignored the errors from CMake and I then ran `make builtins --trace` to extract the command line used to build `sync_fetch_and_add_4.S`. The command line computed by CMake for that file wrongly specified `-march=armv7-a`: /usr/bin/cc -DVISIBILITY_HIDDEN -D_DEBUG -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -D_LARGEFILE_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -I/home/pi/build/projects/compiler-rt/lib/builtins -I/home/pi/llvm/projects/compiler-rt/lib/builtins -I/home/pi/build/include -I/home/pi/llvm/include -fPIC -g-march=armv7-a -mfloat-abi=hard -fno-lto -std=c11 -fomit-frame-pointer -DCOMPILER_RT_ARMHF_TARGET -o CMakeFiles/clang_rt.builtins-armhf.dir/arm/sync_fetch_and_add_4.S.o -c /home/pi/llvm/projects/compiler-rt/lib/builtins/arm/sync_fetch_and_add_4.S When crosscompiling, I had manually specified `-march=armv6`, and that triggered the error. When replacing the architecture on the command line, I observed the same error on the real hardware. The command line specified above is sufficient to reproduce. It seems the architecture is not set correctly at `compiler-rt/cmake/base-config-ix.cmake:201` by using `test_target_arch` from `compiler-rt/cmake/Modules/CompilerRTUtils.cmake`. I tried to build all the targets in the Makefiles of compiler-rt in Docker to see whether the issue is limited to that instruction, and (at least with clang) it seems to be the case, all the other sources compiled correctly, failing only at linking because of the missing `sync_fetch_*.S.o`. -- 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 11778 in oss-fuzz: llvm/clang-fuzzer: Stack-overflow in clang::FunctionProtoType::getExtProtoInfo
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-12-07 Type: Bug New issue 11778 by ClusterFuzz-External: llvm/clang-fuzzer: Stack-overflow in clang::FunctionProtoType::getExtProtoInfo https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=11778 Detailed report: https://oss-fuzz.com/testcase?key=5638360400396288 Project: llvm Fuzzer: libFuzzer_llvm_clang-fuzzer Fuzz target binary: clang-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Stack-overflow Crash Address: 0x7ffd5bf79b88 Crash State: clang::FunctionProtoType::getExtProtoInfo clang::FunctionProtoType::Profile llvm::ContextualFoldingSetclang::ASTContext&>::NodeEq Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201806300739:201807010808 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5638360400396288 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
