[llvm-bugs] [Bug 40201] New: regression: can't build from source: The dependency target "cxx" of target "check-all" does not exist
https://bugs.llvm.org/show_bug.cgi?id=40201 Bug ID: 40201 Summary: regression: can't build from source: The dependency target "cxx" of target "check-all" does not exist Product: lldb Version: unspecified Hardware: Macintosh OS: MacOS X Status: NEW Severity: release blocker Priority: P Component: All Bugs Assignee: lldb-...@lists.llvm.org Reporter: thelastmamm...@gmail.com CC: llvm-bugs@lists.llvm.org instructions from https://lldb.llvm.org/build.html used to work, but is currently broken: ``` git clone https://git.llvm.org/git/llvm.git/ cd llvm/tools git clone https://git.llvm.org/git/clang.git/ git clone https://git.llvm.org/git/lldb.git/ cd ../.. mkdir build cd build cmake .. -G Ninja ``` ``` ... -- Performing Test HAVE_STEADY_CLOCK -- Performing Test HAVE_STEADY_CLOCK -- Performing Test HAVE_STEADY_CLOCK -- success -- Configuring done CMake Error at cmake/modules/AddLLVM.cmake:1362 (add_dependencies): The dependency target "cxx" of target "check-all" does not exist. Call Stack (most recent call first): CMakeLists.txt:928 (add_lit_target) CMake Error at cmake/modules/AddLLVM.cmake:1362 (add_dependencies): The dependency target "cxx" of target "check-lldb-tools-lldb-mi-target-inputs" does not exist. Call Stack (most recent call first): cmake/modules/AddLLVM.cmake:1414 (add_lit_target) tools/lldb/lit/CMakeLists.txt:93 (add_lit_testsuites) CMake Error at cmake/modules/AddLLVM.cmake:1362 (add_dependencies): The dependency target "cxx" of target "check-lldb-tools-lldb-mi-target" does not exist. Call Stack (most recent call first): cmake/modules/AddLLVM.cmake:1414 (add_lit_target) tools/lldb/lit/CMakeLists.txt:93 (add_lit_testsuites) CMake Error at cmake/modules/AddLLVM.cmake:1362 (add_dependencies): The dependency target "cxx" of target ... ``` not sure whether https://bugs.llvm.org/show_bug.cgi?id=39910 is related I'm on OSX mojave 10.14.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] Issue 12361 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-strength_reduce: Timeout in llvm_llvm-opt-fuzzer--x86_64-strength_reduce
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-2019-01-02 Type: Bug New issue 12361 by ClusterFuzz-External: llvm/llvm-opt-fuzzer--x86_64-strength_reduce: Timeout in llvm_llvm-opt-fuzzer--x86_64-strength_reduce https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12361 Detailed report: https://oss-fuzz.com/testcase?key=5719246435254272 Project: llvm Fuzzer: libFuzzer_llvm_llvm-opt-fuzzer--x86_64-strength_reduce Fuzz target binary: llvm-opt-fuzzer--x86_64-strength_reduce Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Timeout (exceeds 25 secs) Crash Address: Crash State: llvm_llvm-opt-fuzzer--x86_64-strength_reduce 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=5719246435254272 Issue filed automatically. See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for instructions to reproduce this bug locally. 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 40086] llvm-objdump failed to compute relocation: R_X86_64_DTPOFF64
https://bugs.llvm.org/show_bug.cgi?id=40086 James Henderson changed: What|Removed |Added Resolution|--- |INVALID Status|NEW |RESOLVED --- Comment #2 from James Henderson --- Oops... I think I may have built the Release build in Visual Studio, but tested using the Debug version (which was stale). Sorry! -- 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 39101] llvm-objdump does not support --demangle
https://bugs.llvm.org/show_bug.cgi?id=39101 James Henderson changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #3 from James Henderson --- (In reply to George Rimar from comment #2) > PR40009 was fixed (r349613 + r349614 and r349617). Seems we can close this? I don't see why not. @emaste, please let us know if you find any issues with the latest version. -- 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 40202] New: LTO COMDAT elimination can eliminate prevailing symbols
https://bugs.llvm.org/show_bug.cgi?id=40202 Bug ID: 40202 Summary: LTO COMDAT elimination can eliminate prevailing symbols Product: libraries Version: 7.0 Hardware: PC OS: Linux Status: NEW Severity: normal Priority: P Component: Linker Assignee: unassignedb...@nondot.org Reporter: cfswo...@gmail.com CC: llvm-bugs@lists.llvm.org Created attachment 21283 --> https://bugs.llvm.org/attachment.cgi?id=21283&action=edit A minimal example project that crashes Clang I've attached an example project that demonstrates this bug. When building it (w/ make), the following error is reported: Alias must point to a definition void (%class.X*)* @_ZN1XIiED1Ev LLVM ERROR: Broken module found, compilation aborted! --- As I understand it, what's happening is: common.h contains a template class X (which, being a template, is subject to instantiation in multiple translation units under the ODR) with a virtual destructor and a base class with a destructor of its own. This means that the class would contain the complete set of D0, D1, and D2 destructors. b.cpp performs an explicit instantiation of X - so b.o contains all 3 destructors (grouped under the D5 COMDAT). a.cpp contains an inline (due to -O1) copy of the X constructor, which means a.o contains a copy of X's vtable and X's D0 destructor. When it comes time to link, if a.o's D0 symbol prevails over b.o's copy of the same, https://reviews.llvm.org/D34803 means that the entire D5 COMDAT from b.o must be eliminated. This happens by converting all affected symbols to available_externally linkage and deleting the COMDAT. The crash, as seen, is caused by the fact that D1 is an alias of D2, and the logic that eliminates the COMDAT doesn't check if D2 is an aliasee first. However, just handling aliased symbols isn't good enough here: even if D1 was a full definition rather than an alias, then COMDAT elimination would mean that the prevailing copies of the D1/D2 destructors aren't getting included in the output binary. This negates the whole purpose of the explicit instantiation in b.cpp (a user of the shared library might be relying on that instantiation), and could even result in a broken binary if b.cpp contained a non-inline call to D1/D2. -- 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 40203] New: [X86][SSE] Remove shift-by-immediate llvm x86 intrinsics
https://bugs.llvm.org/show_bug.cgi?id=40203 Bug ID: 40203 Summary: [X86][SSE] Remove shift-by-immediate llvm x86 intrinsics Product: libraries Version: trunk Hardware: PC OS: Windows NT Status: NEW Severity: enhancement Priority: P Component: Backend: X86 Assignee: unassignedb...@nondot.org Reporter: llvm-...@redking.me.uk CC: craig.top...@gmail.com, llvm-bugs@lists.llvm.org, llvm-...@redking.me.uk, spatel+l...@rotateright.com The SSE SLLI/SRLI/SRAI vector uniform shift by immediate intrinsics still exist due to a gcc compatibility issue requiring us to support non-immediate values in the '_mm_slli_epi32' style C/C++ intrinsics. What would be better is if CGBuiltin could promote the non-immediate cases to use the uniform variable equivalent intrinsics (__builtin_ia32_pslldi128 -> __builtin_ia32_pslld128 etc.) and the 'normal' cases replaced with generic shifts (or zero for out of range logical shifts). This would allow us to remove all the existing slli intrinsics and their handling. -- 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 6587 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-instcombine: ASSERT: isStatepoint(Token)
Comment #6 on issue 6587 by f...@fhahn.com: llvm/llvm-opt-fuzzer--x86_64-instcombine: ASSERT: isStatepoint(Token) https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=6587#c6 I would like to have a look at this failure, but it seems like I do not have permissions to view the detailed report or the reproducer. Is there a reason why this bug was not de-restricted? -- 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 40204] New: [WebAssembly] SDL2_mixer crash on linking with --relocatable
https://bugs.llvm.org/show_bug.cgi?id=40204 Bug ID: 40204 Summary: [WebAssembly] SDL2_mixer crash on linking with --relocatable Product: lld Version: unspecified Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: All Bugs Assignee: unassignedb...@nondot.org Reporter: alonza...@gmail.com CC: llvm-bugs@lists.llvm.org, peter.sm...@linaro.org Created attachment 21284 --> https://bugs.llvm.org/attachment.cgi?id=21284&action=edit libSDL2_mixer.a Original report in https://github.com/kripken/emscripten/issues/7702 Simplified STR: wasm-ld --export-dynamic -z stack-size=5242880 --global-base=1024 --initial-memory=16777216 -o playwave --no-entry --allow-undefined --import-memory --import-table --export __wasm_call_ctors --export __data_end --lto-O0 playwave.o libSDL2_mixer.a --max-memory=16777216 -mllvm -combiner-global-alias-analysis=false -mllvm -enable-emscripten-sjlj -mllvm -disable-lsr --export main --export malloc --export free --export setThrew --export __errno_location --export fflush --relocatable Crash: wasm-ld: /home/username/Dev/llvm/tools/lld/wasm/Symbols.cpp:78: uint32_t lld::wasm::Symbol::getOutputSymbolIndex() const: Assertion `OutputSymbolIndex != INVALID_INDEX' failed. Stack dump: 0. Program arguments: /home/username/Dev/llvm/build/bin/wasm-ld --export-dynamic -z stack-size=5242880 --global-base=1024 --initial-memory=16777216 -o playwave --no-entry --allow-undefined --import-memory --import-table --export __wasm_call_ctors --export __data_end --lto-O0 playwave.o libSDL2_mixer.a --max-memory=16777216 -mllvm -combiner-global-alias-analysis=false -mllvm -enable-emscripten-sjlj -mllvm -disable-lsr --export main --export malloc --export free --export setThrew --export __errno_location --export fflush --relocatable #0 0x558a870103fa llvm::sys::PrintStackTrace(llvm::raw_ostream&) (/home/username/Dev/llvm/build/bin/wasm-ld+0x5313fa) #1 0x558a8700e924 llvm::sys::RunSignalHandlers() (/home/username/Dev/llvm/build/bin/wasm-ld+0x52f924) #2 0x558a8700ea52 SignalHandler(int) (/home/username/Dev/llvm/build/bin/wasm-ld+0x52fa52) #3 0x7f329486e0c0 __restore_rt (/lib/x86_64-linux-gnu/libpthread.so.0+0x110c0) #4 0x7f3293489fcf gsignal (/lib/x86_64-linux-gnu/libc.so.6+0x32fcf) #5 0x7f329348b3fa abort (/lib/x86_64-linux-gnu/libc.so.6+0x343fa) #6 0x7f3293482e37 (/lib/x86_64-linux-gnu/libc.so.6+0x2be37) #7 0x7f3293482ee2 (/lib/x86_64-linux-gnu/libc.so.6+0x2bee2) #8 0x558a873c64a5 lld::wasm::Symbol::getOutputSymbolIndex() const (/home/username/Dev/llvm/build/bin/wasm-ld+0x8e74a5) #9 0x558a873adf55 lld::wasm::ObjFile::calcNewIndex(llvm::wasm::WasmRelocation const&) const (/home/username/Dev/llvm/build/bin/wasm-ld+0x8cef55) #10 0x558a873abd33 lld::wasm::InputChunk::writeRelocations(llvm::raw_ostream&) const (/home/username/Dev/llvm/build/bin/wasm-ld+0x8ccd33) #11 0x558a873e989a lld::wasm::CodeSection::writeRelocations(llvm::raw_ostream&) const (/home/username/Dev/llvm/build/bin/wasm-ld+0x90a89a) #12 0x558a873cb8ba (anonymous namespace)::Writer::createRelocSections() (/home/username/Dev/llvm/build/bin/wasm-ld+0x8ec8ba) #13 0x558a873ce1bd (anonymous namespace)::Writer::createSections() (/home/username/Dev/llvm/build/bin/wasm-ld+0x8ef1bd) #14 0x558a873d1426 (anonymous namespace)::Writer::run() (/home/username/Dev/llvm/build/bin/wasm-ld+0x8f2426) #15 0x558a873d1b3b lld::wasm::writeResult() (/home/username/Dev/llvm/build/bin/wasm-ld+0x8f2b3b) #16 0x558a873a4ef4 (anonymous namespace)::LinkerDriver::link(llvm::ArrayRef) (/home/username/Dev/llvm/build/bin/wasm-ld+0x8c5ef4) #17 0x558a873a17d9 lld::wasm::link(llvm::ArrayRef, bool, llvm::raw_ostream&) (/home/username/Dev/llvm/build/bin/wasm-ld+0x8c27d9) #18 0x558a86ff70d9 main (/home/username/Dev/llvm/build/bin/wasm-ld+0x5180d9) #19 0x7f32934772b1 __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x202b1) #20 0x558a86ff505a _start (/home/username/Dev/llvm/build/bin/wasm-ld+0x51605a) Aborted -- 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 40205] New: Misleading carat in fixit hint for constexpr-not-const
https://bugs.llvm.org/show_bug.cgi?id=40205
Bug ID: 40205
Summary: Misleading carat in fixit hint for constexpr-not-const
Product: clang
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: Frontend
Assignee: unassignedclangb...@nondot.org
Reporter: jykni...@google.com
CC: llvm-bugs@lists.llvm.org, neeil...@live.com,
richard-l...@metafoo.co.uk
Given this:
clang -std=c++11 -fsyntax-only -c -Wconstexpr-not-const test.cc
test.cc:
class Foo {
constexpr int operator()() { return 0; }
};
You get:
test.cc:2:17: warning: 'constexpr' non-static member function will not be
implicitly 'const' in C++14; add 'const' to avoid a change in behavior
[-Wconstexpr-not-const]
constexpr int operator()() { return 0; }
^
const
The carat points before/to the function name -- which makes it seem like that's
where it wants you to add "const". However, you really need to add it at the
end -- where the text "const" is printed, rather than where the carat points
to.
That's confusing.
--
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 39910] Libcxx should be a dependency of check-lldb target
https://bugs.llvm.org/show_bug.cgi?id=39910 Jonas Devlieghere changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED CC||jdevliegh...@apple.com --- Comment #1 from Jonas Devlieghere --- This was added in r349539. -- 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 40206] New: After r329339, loop unrolling with long doubles seems to be incorrect
https://bugs.llvm.org/show_bug.cgi?id=40206
Bug ID: 40206
Summary: After r329339, loop unrolling with long doubles seems
to be incorrect
Product: new-bugs
Version: 7.0
Hardware: PC
OS: All
Status: NEW
Severity: normal
Priority: P
Component: new bugs
Assignee: unassignedb...@nondot.org
Reporter: dimi...@andric.com
CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org
As reported in https://bugs.freebsd.org/234040, after the import of clang 7.0 a
few math library tests started failing.
Bisection over llvm trunk showed that these failures were introduced via
https://reviews.llvm.org/rL329339 ("[X86] Remove some InstRWs for plain store
instructions on Sandy Bridge. We were forcing the latency of these instructions
to 5 cycles, but every other scheduler model had them as 1 cycle. I'm sure I
didn't get everything, but this gets a big portion.")
Test case, minimized from the loop here:
https://github.com/freebsd/freebsd/blob/master/lib/msun/ld80/e_rem_pio2l.h#L131
// clang -O2 rempio-min.c -o rempio-min
long double __attribute__((noinline)) rem_pio2l_min(long double z)
{
int i;
double tx[2];
for (i = 0; i < 2; ++i) {
tx[i] = (double)((int)(z));
z = (z - tx[i]) * 1.6777216e+07;
}
return z;
}
int main(void)
{
const long double test1 = 0x1.b2f3ee96e7600326p+23L;
const long double check1 = 0x1.93p+16;
long double res;
res = rem_pio2l_min(test1);
return res == check1 ? 0 : 1;
}
Side-by-side diff of clang r329338 (left) and r329339 (right) assembly output,
hoping that bugzilla won't mess it up too badly:
rem_pio2l_min:rem_pio2l_min:
.cfi_startproc.cfi_startproc
pushq %rbp pushq %rbp
.cfi_def_cfa_offset 16.cfi_def_cfa_offset 16
.cfi_offset %rbp, -16 .cfi_offset %rbp, -16
movq%rsp, %rbpmovq%rsp, %rbp
.cfi_def_cfa_register %rbp.cfi_def_cfa_register %rbp
fnstcw -4(%rbp) fnstcw -4(%rbp)
fldt16(%rbp)<
movzwl -4(%rbp), %eaxmovzwl -4(%rbp), %eax
movw$3199, -4(%rbp) movw$3199, -4(%rbp)
fldcw -4(%rbp) fldcw -4(%rbp)
> fldt16(%rbp)
movw%ax, -4(%rbp) movw%ax, -4(%rbp)
fistl -8(%rbp) fistl -8(%rbp)
fldcw -4(%rbp) fldcw -4(%rbp)
cvtsi2sdl -8(%rbp), %xmm0 cvtsi2sdl -8(%rbp), %xmm0
movsd %xmm0, -32(%rbp) movsd %xmm0, -32(%rbp)
fsubl -32(%rbp) fsubl -32(%rbp)
flds.LCPI0_0(%rip) <
fnstcw -2(%rbp) fnstcw -2(%rbp)
fmul%st(0), %st(1) | flds.LCPI0_0(%rip)
movzwl -2(%rbp), %eaxmovzwl -2(%rbp), %eax
movw$3199, -2(%rbp) movw$3199, -2(%rbp)
fldcw -2(%rbp) fldcw -2(%rbp)
> fmul%st(0), %st(1)
movw%ax, -2(%rbp) movw%ax, -2(%rbp)
fxch%st(1)fxch%st(1)
fistl -12(%rbp) fistl -12(%rbp)
fldcw -2(%rbp) fldcw -2(%rbp)
xorps %xmm0, %xmm0 xorps %xmm0, %xmm0
cvtsi2sdl -12(%rbp), %xmm0 cvtsi2sdl -12(%rbp), %xmm0
movsd %xmm0, -24(%rbp) movsd %xmm0, -24(%rbp)
fsubl -24(%rbp) fsubl -24(%rbp)
fmulp %st(1)fmulp %st(1)
popq%rbp popq%rbp
retq retq
--
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 40201] regression: can't build from source: The dependency target "cxx" of target "check-all" does not exist
https://bugs.llvm.org/show_bug.cgi?id=40201 Jonas Devlieghere changed: What|Removed |Added CC||jdevliegh...@apple.com Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #2 from Jonas Devlieghere --- Yup, this is intentional, as per PR39910 you referred. It doesn't make sense to build LLDB without libcxx on Darwin. -- 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 40134] __executable_start doesn't get added to executables
https://bugs.llvm.org/show_bug.cgi?id=40134 Thomas Anderson changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #11 from Thomas Anderson --- Should be fixed by https://reviews.llvm.org/rL350251 -- 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 40207] New: Accepts program with invalid abstract-declarator grammar.
https://bugs.llvm.org/show_bug.cgi?id=40207
Bug ID: 40207
Summary: Accepts program with invalid abstract-declarator
grammar.
Product: clang
Version: trunk
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P
Component: -New Bugs
Assignee: unassignedclangb...@nondot.org
Reporter: anders.granlun...@gmail.com
CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org,
neeil...@live.com, richard-l...@metafoo.co.uk
Test case (prog.c):
void f(int [const *]);
int main() {}
Compilation command line:
clang prog.c -Wall -Wextra -std=c11 -pedantic-errors
Observed behaviour:
No error messages outputed.
Expected behaviour:
An error message outputed.
[const *] is an valid abstract-declarator according to the grammar in
6.7.7/1
(no type qualifiers allowed in [*]).
--
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 40197] c11: Rejects valid program dereferencing pointer with incomplete reference type.
https://bugs.llvm.org/show_bug.cgi?id=40197 Anders Granlund changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #1 from Anders Granlund --- Nevermind. The program is invalid because of 6.3.2.1/2. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 40207] c11: Accepts program with invalid abstract-declarator grammar.
https://bugs.llvm.org/show_bug.cgi?id=40207 Anders Granlund changed: What|Removed |Added Resolution|--- |WONTFIX Status|NEW |RESOLVED --- Comment #2 from Anders Granlund --- Seems to be a defect in the standard, see: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88667 -- 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 39385] block/loop/try signature is not supported in WebAssemblyAsmParser
https://bugs.llvm.org/show_bug.cgi?id=39385 Wouter van Oortmerssen changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #1 from Wouter van Oortmerssen --- Fixed: https://reviews.llvm.org/D56092 -- 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 39816] lldb doesn't show a file of line entry for big project.
https://bugs.llvm.org/show_bug.cgi?id=39816 Adrian Prantl changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #4 from Adrian Prantl --- Landed in r350274. -- 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 40208] New: failed cross compiling ffmpeg's av_sscanf (libavutil/avstring.h)
https://bugs.llvm.org/show_bug.cgi?id=40208 Bug ID: 40208 Summary: failed cross compiling ffmpeg's av_sscanf (libavutil/avstring.h) Product: clang Version: trunk Hardware: PC OS: Linux Status: NEW Severity: normal Priority: P Component: C++ Assignee: unassignedclangb...@nondot.org Reporter: chcunning...@google.com CC: blitzrak...@gmail.com, dgre...@apple.com, erik.pilking...@gmail.com, llvm-bugs@lists.llvm.org, richard-l...@metafoo.co.uk Created attachment 21286 --> https://bugs.llvm.org/attachment.cgi?id=21286&action=edit preprocessed source Encountered while rolling latest ffmpeg into chromium. Cross compile info: Host OS : linux Target OS : android Host arch : x64 Target arch : x64 Error output: fatal error: error in backend: Cannot select: t81: ch = store<(store 8 into %stack.6), trunc to f64> t0, t38, FrameIndex:i64<6>, undef:i64 t38: f128,ch,glue = CopyFromReg t36, Register:f128 $xmm0, t36:1 t37: f128 = Register $xmm0 t36: ch,glue = callseq_end t35, TargetConstant:i64<0>, TargetConstant:i64<0>, t35:1 t7: i64 = TargetConstant<0> t7: i64 = TargetConstant<0> t35: ch,glue = X86ISD::CALL t33, TargetExternalSymbol:i64'__floatsitf' [TF=6], Register:i32 $edi, RegisterMask:Untyped, t33:1 t34: i64 = TargetExternalSymbol'__floatsitf' [TF=6] t11: i32 = Register $edi t14: Untyped = RegisterMask t33: ch,glue = CopyToReg t32, Register:i32 $edi, t22 t11: i32 = Register $edi t22: i32 = AssertSext t20, ValueType:ch:i4 t20: i32,ch = CopyFromReg t0, Register:i32 %260 t19: i32 = Register %260 t80: i64 = FrameIndex<6> t53: i64 = undef In function: av_sscanf clang: error: clang frontend command failed with exit code 70 (use -v to see invocation) clang version 8.0.0 (trunk 349417) Target: x86_64-unknown-linux-android Thread model: posix InstalledDir: /ssd/blink3/src/third_party/llvm-build/Release+Asserts/bin clang: note: diagnostic msg: PLEASE submit a bug report to https://bugs.llvm.org/ and include the crash backtrace, preprocessed source, and associated run script. clang: note: diagnostic msg: PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT: Preprocessed source(s) and associated run script(s) are located at: clang: note: diagnostic msg: /tmp/avsscanf-6714ad.c clang: note: diagnostic msg: /tmp/avsscanf-6714ad.sh clang: note: diagnostic msg: /ssd/blink3/src/third_party/ffmpeg/ffbuild/common.mak:60: recipe for target 'libavutil/avsscanf.o' failed -- 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 12368 in oss-fuzz: llvm/clang-fuzzer: Stack-overflow in llvm::SmallVectorBase::grow_pod
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-2019-01-03 Type: Bug New issue 12368 by ClusterFuzz-External: llvm/clang-fuzzer: Stack-overflow in llvm::SmallVectorBase::grow_pod https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12368 Detailed report: https://oss-fuzz.com/testcase?key=5714767858106368 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: 0x7ffdc3b73d88 Crash State: llvm::SmallVectorBase::grow_pod clang::CharLiteralParser::CharLiteralParser clang::Sema::ActOnCharacterConstant Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201802020657:201802030042 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5714767858106368 Issue filed automatically. See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for instructions to reproduce this bug locally. 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 40209] New: Problems in DBG_VALUE handling in RegStackify
https://bugs.llvm.org/show_bug.cgi?id=40209
Bug ID: 40209
Summary: Problems in DBG_VALUE handling in RegStackify
Product: libraries
Version: trunk
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P
Component: Backend: WebAssembly
Assignee: unassignedb...@nondot.org
Reporter: ahee...@gmail.com
CC: llvm-bugs@lists.llvm.org
Created attachment 21289
--> https://bugs.llvm.org/attachment.cgi?id=21289&action=edit
Test case with multiple defs within a BB
It looks DBG_VALUE instruction handling in RegStackify, which was added in
https://reviews.llvm.org/D49034 (https://reviews.llvm.org/rL343007) has several
problems.
1. `MoveDebugValues` and `UpdateDebugValuesReg` do not seem to consider the
case where there are multiple defs to a single register within a BB. Currently
they treat all `DBG_VALUE` instruction to a register as a group and move /
update them together whenever any one of the definitions of the register in a
BB is stackified. A sample test case with multiple defs within a BB that fails
is attached.
2. In `UpdateDebugValuesReg` function,
```
static void UpdateDebugValuesReg(unsigned Reg, unsigned NewReg,
MachineBasicBlock &MBB,
MachineRegisterInfo &MRI) {
for (auto &Op : MRI.reg_operands(Reg)) {
MachineInstr *MI = Op.getParent();
assert(MI != nullptr);
if (MI->isDebugValue() && MI->getParent() == &MBB)
Op.setReg(NewReg);
}
}
```
Here `Op.setReg(NewReg)` modifies the iterator `MRI.reg_operands(Reg)` while
traversing it. So this ends up hitting only the first element and bailing out.
This function has problems even without this bug because of the 1 above though.
3. `CloneDebugValues` function does not consider a case that an instruction to
be rematerialized is in another BB. Even though RegStackify mostly work within
a BB, when a def is trivially rematerializable, i.e., `const_i32` instruction,
that instruction can be another BB and can be copied to this BB. But
`CloneDebugValues` limit the search within this BB by `MI->getParent() == &MBB`
clause, so in that case the debug value for the rematerialized instruction will
not be cloned. A test case can be made trivially, so I'm not gonna attach an
mir file for that, but it should look like this:
```
bb1:
%3 = const_i32 3 ; This is trivially rematerializable
...
bb2:
...
use %3
```
--
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
