[llvm-bugs] Issue 11064 in oss-fuzz: llvm: Build failure
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: Proj-llvm Type: Build-Failure New issue 11064 by ClusterFuzz-External: llvm: Build failure https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=11064 The last 2 builds for llvm have been failing. Build log: https://oss-fuzz-build-logs.storage.googleapis.com/log-f8d760d0-2cb6-4370-9a04-a0b2b465b3c0.txt Build type: fuzzing To reproduce locally, please see: https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md#reproducing-build-failures If you have any questions, please file a bug on https://github.com/google/oss-fuzz/issues/new. **This bug will be automatically closed within a day once it is fixed.** -- 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 39366] New: LLVM IR generation of compound statement ('{}') crash
https://bugs.llvm.org/show_bug.cgi?id=39366
Bug ID: 39366
Summary: LLVM IR generation of compound statement ('{}') crash
Product: OpenMP
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: Clang Compiler Support
Assignee: unassignedclangb...@nondot.org
Reporter: lebedev...@gmail.com
CC: llvm-bugs@lists.llvm.org
Created attachment 21022
--> https://bugs.llvm.org/attachment.cgi?id=21022&action=edit
/tmp/VC5Decompressor-3e2f2e.cpp
[1/3 0.2/sec] Building CXX object
src/CMakeFiles/rawspeed.dir/librawspeed/decompressors/VC5Decompressor.cpp.o
FAILED:
src/CMakeFiles/rawspeed.dir/librawspeed/decompressors/VC5Decompressor.cpp.o
/usr/bin/cmake -E __run_co_compile --tidy=/usr/local/bin/clang-tidy
--source=../src/librawspeed/decompressors/VC5Decompressor.cpp --
/usr/local/bin/clang++ -DDEBUG -D_GLIBCXX_SANITIZE_VECTOR -Isrc
-I../src/librawspeed -isystem ../src/external -std=c++14 -Wall -Wextra
-Weverything -Wno-c++98-compat -Wno-c++98-compat-pedantic -Wno-conversion
-Wno-covered-switch-default -Wno-deprecated -Wno-double-promotion
-Wno-exit-time-destructors -Wno-global-constructors
-Wno-gnu-zero-variadic-macro-arguments -Wno-old-style-cast -Wno-padded
-Wno-switch-enum -Wno-unused-macros -Wno-unused-parameter -Wno-weak-vtables
-Wno-zero-as-null-pointer-constant -Wextra-semi -O3 -fno-optimize-sibling-calls
-fsanitize=address -fno-omit-frame-pointer -fno-common -U_FORTIFY_SOURCE
-fsanitize-address-use-after-scope -fsanitize=undefined
-fno-sanitize-recover=undefined -fsanitize=integer
-fno-sanitize-recover=integer -fPIC -march=native -g3 -ggdb3 -Werror -pthread
-fopenmp=libomp -std=c++14 -MD -MT
src/CMakeFiles/rawspeed.dir/librawspeed/decompressors/VC5Decompressor.cpp.o -MF
src/CMakeFiles/rawspeed.dir/librawspeed/decompressors/VC5Decompressor.cpp.o.d
-o src/CMakeFiles/rawspeed.dir/librawspeed/decompressors/VC5Decompressor.cpp.o
-c ../src/librawspeed/decompressors/VC5Decompressor.cpp
Stack dump:
0. Program arguments: /usr/lib/llvm-8/bin/clang -cc1 -triple
x86_64-pc-linux-gnu -emit-obj -disable-free -disable-llvm-verifier
-discard-value-names -main-file-name VC5Decompressor.cpp -mrelocation-model pic
-pic-level 2 -mthread-model posix -mdisable-fp-elim -mdisable-tail-calls
-fmath-errno -masm-verbose -mconstructor-aliases -munwind-tables
-fuse-init-array -target-cpu bdver2 -target-feature +sse2 -target-feature +cx16
-target-feature +sahf -target-feature +tbm -target-feature -avx512ifma
-target-feature -sha -target-feature -gfni -target-feature +fma4
-target-feature -vpclmulqdq -target-feature +prfchw -target-feature -bmi2
-target-feature -cldemote -target-feature -fsgsbase -target-feature -ptwrite
-target-feature -xsavec -target-feature +popcnt -target-feature +aes
-target-feature -avx512bitalg -target-feature -movdiri -target-feature -xsaves
-target-feature -avx512er -target-feature -avx512vnni -target-feature
-avx512vpopcntdq -target-feature -pconfig -target-feature -clwb -target-feature
-avx512f -target-feature -clzero -target-feature -pku -target-feature +mmx
-target-feature -lwp -target-feature -rdpid -target-feature +xop
-target-feature -rdseed -target-feature -waitpkg -target-feature -movdir64b
-target-feature +sse4a -target-feature -avx512bw -target-feature -clflushopt
-target-feature +xsave -target-feature -avx512vbmi2 -target-feature +64bit
-target-feature -avx512vl -target-feature -invpcid -target-feature -avx512cd
-target-feature +avx -target-feature -vaes -target-feature -rtm -target-feature
+fma -target-feature +bmi -target-feature -rdrnd -target-feature -mwaitx
-target-feature +sse4.1 -target-feature +sse4.2 -target-feature -avx2
-target-feature -wbnoinvd -target-feature +sse -target-feature +lzcnt
-target-feature +pclmul -target-feature -prefetchwt1 -target-feature +f16c
-target-feature +ssse3 -target-feature -sgx -target-feature -shstk
-target-feature +cmov -target-feature -avx512vbmi -target-feature -movbe
-target-feature -xsaveopt -target-feature -avx512dq -target-feature -adx
-target-feature -avx512pf -target-feature +sse3 -dwarf-column-info
-debug-info-kind=limited -dwarf-version=4 -debugger-tuning=gdb
-momit-leaf-frame-pointer -coverage-notes-file
/home/lebedevri/rawspeed/build-Clang-SANITIZE/src/CMakeFiles/rawspeed.dir/librawspeed/decompressors/VC5Decompressor.cpp.gcno
-resource-dir /usr/lib/llvm-8/lib/clang/8.0.0 -dependency-file
src/CMakeFiles/rawspeed.dir/librawspeed/decompressors/VC5Decompressor.cpp.o.d
-sys-header-deps -MT
src/CMakeFiles/rawspeed.dir/librawspeed/decompressors/VC5Decompressor.cpp.o
-isystem ../src/external -D DEBUG -D _GLIBCXX_SANITIZE_VECTOR -I src -I
../src/librawspeed -U _FORTIFY_SOURCE -internal-isystem
/usr/lib64/gcc/x86_64-linux-gnu/8/../../../../include/c++/8 -internal-isystem
/usr/lib64/gcc/x86_64-linux-gnu/8/../../../../include/x86_64-linux-gnu/c++/8
-internal-isystem
[llvm-bugs] [Bug 39367] New: Warn-unused-results warnings with expression statements dependent on whether the expr-stmt was typed or generated by the preprocessor
https://bugs.llvm.org/show_bug.cgi?id=39367
Bug ID: 39367
Summary: Warn-unused-results warnings with expression
statements dependent on whether the expr-stmt was
typed or generated by the preprocessor
Product: clang
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: Frontend
Assignee: unassignedclangb...@nondot.org
Reporter: psko...@gmail.com
CC: llvm-bugs@lists.llvm.org
Hi, my problem appears related to https://bugs.llvm.org/show_bug.cgi?id=8218
and
https://bugs.llvm.org/show_bug.cgi?id=13747
I'm getting some very weird behavior out clang regarding the unused-value
warnings.
This compiles without a warning with `clang -c file.c`:
void fail(void); long f(void); void g(void);
#define CHK(X) (__extension__ ({ long CHK=X; if(0>CHK) fail(); else{;}
(void)CHK; CHK; }))
int main()
{
int n = 0;
f();
CHK(f());
switch(n){case 0: CHK(f()); }
#define SWITCH(...) switch(n){ __VA_ARGS__ }
SWITCH(case 0: f(); )
#if OOPS
SWITCH(case 0: CHK(f()); )
#endif
}
but enabling the last swith with the pasted block generates an unused-value
warning.
`clang -DOOPS file.c -c`. Perhaps even more shockingly even without the `OOPS`
macro being truthy,
the program generates two warnings (or 3 `#if !!OOPS`) if compiled with `clang
file.c -E |clang -xc - -c`,
which ought to give the same result as `clang file.c -c`.
Complete set of examples (creates file.c in the $PWD):
#!/bin/sh -eu
cat > file.c &1 |head -n1
echo NO WUR
clang -Wall file.c -c
echo WUR ON OOPS=1
clang -Wall -DOOPS=1 file.c -c
echo WUR ON SEPARATE PREPROCESSING "(NO OOPS)"
clang -E -Wall file.c |clang -xc - -o /dev/null -c
My output:
clang version 6.0.0-1ubuntu2 (tags/RELEASE_600/final)
NO WUR
WUR ON OOPS=1
file.c:13:17: warning: expression result unused [-Wunused-value]
SWITCH(case 0: CHK(f()); )
^~~~
file.c:2:83: note: expanded from macro 'CHK'
#define CHK(X) (__extension__ ({ long CHK=X; if(0>CHK) fail(); else{;}
(void)CHK; CHK; }))
^~~
file.c:9:33: note: expanded from macro 'SWITCH'
#define SWITCH(...) switch(n){ __VA_ARGS__ }
^~~
1 warning generated.
WUR ON SEPARATE PREPROCESSING (NO OOPS)
file.c:8:89: warning: expression result unused [-Wunused-value]
switch(n){case 0: (__extension__ ({ long CHK=f(); if(0>CHK) fail();
else{;} (void)CHK; CHK; })); }
^~~
file.c:7:71: warning: expression result unused [-Wunused-value]
(__extension__ ({ long CHK=f(); if(0>CHK) fail(); else{;} (void)CHK;
CHK; }));
^~~
2 warnings generated.
Suggestion:
Either disable unused-value warnings for expression statements like gcc does it
or (better)
allow __attribute((warn_unused_result)) on variables and if that variable is
used for the "return" value of
an expression statement, treat that expression statement like a function call
to a function with the
`warn-unused-result` attribute.
In my opinion, expr statements are kind of like function calls anyway, so it'd
make sense to be able to somehow stick a warn-unused-result attribute to them.
Another idea, if clang wants to warn on unused expr-stmts by default, might be
to suppres the warning if the expr-stmt evaluates to a variable mark with the
unused attribute.
E.g., perhaps:
#define CHK(X) (__extension__ ({ long __attribute__((unused))
/*<-ADDED*/ CHK=X; if(0>CHK) fail(); else{;} (void)CHK; CHK; /*UNUSED ATTR*/}))
should never genera
[llvm-bugs] [Bug 36890] [X86] WriteRMW should require a AGU port for the store on Intel CPUs
https://bugs.llvm.org/show_bug.cgi?id=36890 Simon Pilgrim changed: What|Removed |Added Status|NEW |RESOLVED Fixed By Commit(s)||329415 Resolution|--- |FIXED --- Comment #1 from Simon Pilgrim --- Craig fixed this in rL329415 for the Sandy Bridge/Broadwell/Haswell/Skylake models We confirmed in D52740/rL343670 that Atom/SLM is setup correctly and doesn't need an extra port cycle to recompute the address. -- 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 32325] [META][X86] Improve implementation and use of X86 scheduler models
https://bugs.llvm.org/show_bug.cgi?id=32325 Bug 32325 depends on bug 36890, which changed state. Bug 36890 Summary: [X86] WriteRMW should require a AGU port for the store on Intel CPUs https://bugs.llvm.org/show_bug.cgi?id=36890 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 39217] error: use of unknown builtin '__builtin_ia32_cvtdq2ps'
https://bugs.llvm.org/show_bug.cgi?id=39217 Simon Pilgrim changed: What|Removed |Added Component|-New Bugs |LLVM Codegen Resolution|--- |INVALID Status|NEW |RESOLVED CC||llvm-...@redking.me.uk --- Comment #3 from Simon Pilgrim --- Resolving - as Craig said, the official intrinsic _mm_cvtepi32_ps should be used instead. Direct dependency on target specific builtin intrinsics such as __builtin_ia32_cvtdq2ps should be avoided wherever possible as they are not guaranteed. -- 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 39368] New: Add EXTRACT/INSERT_SUBVECTOR support to TTI::getShuffleCost
https://bugs.llvm.org/show_bug.cgi?id=39368 Bug ID: 39368 Summary: Add EXTRACT/INSERT_SUBVECTOR support to TTI::getShuffleCost Product: libraries Version: trunk Hardware: PC OS: Windows NT Status: NEW Severity: enhancement Priority: P Component: Common Code Generator Code Assignee: unassignedb...@nondot.org Reporter: llvm-...@redking.me.uk CC: a.bat...@hotmail.com, llvm-bugs@lists.llvm.org, spatel+l...@rotateright.com The default horizontal reduction costs depend on EXTRACT_SUBVECTOR shuffle costs, but we barely have support for these in the TTIs. Several issues need to be addressed: 1 - correct identification of EXTRACT/INSERT_SUBVECTOR shufflevector patterns in ShuffleVectorInst - we've ignored length changing shuffles so far. EXTRACT is easy, just look for an unary sequential shuffle (I don't think we need it to be subvector aligned - just include it in the getShuffleCost index argument). INSERT is trickier as we need to determine what the size of the subvector was, so we need to search the IR for the source. 2 - Fix use of Index and SubTy in getShuffleCost calls - AFAICT the Index should indicate the extraction/insertion point of the subvector and SubTy should always refer to the subvector type (and Ty should refer to the larger vector type - which for EXTRACT isn't the destination type). 3 - Add SK_InsertSubvector/SK_ExtractSubvector support to BasicTTIImpl::getShuffleCosts similar to getPermuteShuffleOverhead. 4 - Add SK_InsertSubvector/SK_ExtractSubvector support to targets - X86 in particular as the XMM/YMM/ZMM instructions have the most use for 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] [Bug 39369] New: -Wformat + typed enum class - difference with gcc
https://bugs.llvm.org/show_bug.cgi?id=39369
Bug ID: 39369
Summary: -Wformat + typed enum class - difference with gcc
Product: clang
Version: trunk
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: -New Bugs
Assignee: unassignedclangb...@nondot.org
Reporter: lebedev...@gmail.com
CC: llvm-bugs@lists.llvm.org
https://godbolt.org/z/GX-Fqv
#include
enum class Enum : unsigned short {
One,
};
void test(Enum e) {
printf("0x%04hx", e);
}
gcc:
: In function 'void test(Enum)':
:8:12: warning: format '%hx' expects argument of type 'int', but
argument 2 has type 'Enum' [-Wformat=]
printf("0x%04hx", e);
^ ~
Compiler returned: 0
Clang is fine with that.
Who is wrong?
--
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 39370] New: [X86] Merge r344824 into 7.0.1
https://bugs.llvm.org/show_bug.cgi?id=39370 Bug ID: 39370 Summary: [X86] Merge r344824 into 7.0.1 Product: clang Version: 7.0 Hardware: PC OS: All Status: NEW Severity: enhancement Priority: P Component: LLVM Codegen Assignee: unassignedclangb...@nondot.org Reporter: craig.top...@gmail.com CC: llvm-bugs@lists.llvm.org This fixes a bug in attribute target multiversion which was a new feature for the 7.0 release. -- 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 39363] Cannot construct unique_ptr with pointer to incomplete type
https://bugs.llvm.org/show_bug.cgi?id=39363 Eric Fiselier changed: What|Removed |Added Resolution|--- |WORKSFORME Status|NEW |RESOLVED --- Comment #2 from Eric Fiselier --- libc++ supports this use case, we have tests for it, and it works. The godbolt link you provided is using libstdc++, not libc++. Adding -stdlib=libc++ makes the example compile as expected (https://godbolt.org/z/pHpTlH) -- 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 39371] New: No definition emitted for template class static variable
https://bugs.llvm.org/show_bug.cgi?id=39371 Bug ID: 39371 Summary: No definition emitted for template class static variable Product: clang Version: trunk Hardware: PC OS: All Status: NEW Severity: enhancement Priority: P Component: Modules Assignee: unassignedclangb...@nondot.org Reporter: andrew...@gmail.com CC: dgre...@apple.com, llvm-bugs@lists.llvm.org In some cases (seemingly involving namespaces, and use of the static variable in a function within the module), a definition for a template class's static variable isn't emitted. Simplified repro at https://reviews.llvm.org/differential/diff/170323/. -- 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 39354] Potential undefined behaviour in the ctor for vector
https://bugs.llvm.org/show_bug.cgi?id=39354 Eric Fiselier changed: What|Removed |Added Resolution|--- |INVALID Status|NEW |RESOLVED --- Comment #2 from Eric Fiselier --- Also, can you provide which line specifically the static analyzer is warning about? -- 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 11071 in oss-fuzz: llvm/clang-fuzzer: Stack-overflow in clang::NumericLiteralParser::GetFloatValue
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-21 Type: Bug New issue 11071 by ClusterFuzz-External: llvm/clang-fuzzer: Stack-overflow in clang::NumericLiteralParser::GetFloatValue https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=11071 Detailed report: https://oss-fuzz.com/testcase?key=5761401843351552 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: 0x7ffd0dd0cd58 Crash State: clang::NumericLiteralParser::GetFloatValue BuildFloatingLiteral clang::Sema::ActOnNumericConstant Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201810140231:201810150227 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5761401843351552 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] Issue 11075 in oss-fuzz: llvm/llvm-dwarfdump-fuzzer: Timeout in llvm_llvm-dwarfdump-fuzzer
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-10-21 Type: Bug New issue 11075 by ClusterFuzz-External: llvm/llvm-dwarfdump-fuzzer: Timeout in llvm_llvm-dwarfdump-fuzzer https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=11075 Detailed report: https://oss-fuzz.com/testcase?key=5687995936538624 Project: llvm Fuzzer: libFuzzer_llvm_llvm-dwarfdump-fuzzer Fuzz target binary: llvm-dwarfdump-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Timeout (exceeds 25 secs) Crash Address: Crash State: llvm_llvm-dwarfdump-fuzzer Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201803210523:201803220523 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5687995936538624 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
