[llvm-bugs] [Bug 40755] New: Compile error occurs when -stdlib=libc++ is specified
https://bugs.llvm.org/show_bug.cgi?id=40755
Bug ID: 40755
Summary: Compile error occurs when -stdlib=libc++ is specified
Product: libc++
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: All Bugs
Assignee: unassignedclangb...@nondot.org
Reporter: ueno.masak...@jp.fujitsu.com
CC: llvm-bugs@lists.llvm.org, mclow.li...@gmail.com
If -stdlib=libc++ is specified, a compiler error occurs because there is a
const qualification bug.
* source code
#include
#include
#include
using namespace std;
class test_class {
public:
int i;
map map_a;
public:
bool is_bbb(int t) {
static map::iterator it;
if (t == 0) {
it = map_a.begin();
return true;
}
return false;
}
};
* error message
$ clang++ -O3 args_parser.cpp -c -stdlib=libc++
args_parser.cpp:16:10: error: no viable overloaded '='
it = map_a.begin();
~~ ^ ~
/opt/llvm/svn-trunk/install/bin/../include/c++/v1/map:776:28: note: candidate
function (the implicit copy assignment operator) not viable: no known
conversion from '__map_iterator<__tree_iterator<__value_type,
[...]>, std::__1::__tree, std::__1::allocator >, int>,
std::__1::__map_value_compare, std::__1::allocator >,
std::__1::__value_type, std::__1::allocator >, int>,
std::__1::less,
std::__1::allocator > >, true>,
std::__1::allocator, std::__1::allocator >, int> >
>::__node_pointer, [...]>>' to 'const
__map_iterator<__tree_iterator<__value_type,
[...]>, std::__1::__tree_node,
std::__1::allocator >, int>, void *> *, [...]>>' for 1st argument
class _LIBCPP_TEMPLATE_VIS __map_iterator
^
/opt/llvm/svn-trunk/install/bin/../include/c++/v1/map:776:28: note: candidate
function (the implicit move assignment operator) not viable: no known
conversion from '__map_iterator<__tree_iterator<__value_type,
[...]>, std::__1::__tree, std::__1::allocator >, int>,
std::__1::__map_value_compare, std::__1::allocator >,
std::__1::__value_type, std::__1::allocator >, int>,
std::__1::less,
std::__1::allocator > >, true>,
std::__1::allocator, std::__1::allocator >, int> >
>::__node_pointer, [...]>>' to
'__map_iterator<__tree_iterator<__value_type,
[...]>, std::__1::__tree_node,
std::__1::allocator >, int>, void *> *, [...]>>' for 1st argument
1 error generated.
$
* Note
There is no problem if -stdlib=libstdc++ option is valid.
$ clang++ -O3 aaa.cpp -c -stdlib=libstdc++
$
--
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 40742] Merge r354035 into 8.0
https://bugs.llvm.org/show_bug.cgi?id=40742 Hans Wennborg changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #1 from Hans Wennborg --- Merged in r354247. Thanks! -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 40331] [meta] 8.0.0 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=40331 Bug 40331 depends on bug 40742, which changed state. Bug 40742 Summary: Merge r354035 into 8.0 https://bugs.llvm.org/show_bug.cgi?id=40742 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 13174 in oss-fuzz: llvm/llvm-isel-fuzzer--x86_64-O2: ASSERT: isa(Val) && "cast() argument of incompatible type!"
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com, igm...@gmail.com, mit...@google.com, bigchees...@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-02-18 Type: Bug New issue 13174 by ClusterFuzz-External: llvm/llvm-isel-fuzzer--x86_64-O2: ASSERT: isa(Val) && "cast() argument of incompatible type!" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=13174 Detailed report: https://oss-fuzz.com/testcase?key=6264458064691200 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: isa(Val) && "cast() argument of incompatible type!" llvm::Intrinsic::getDeclaration llvm::IRBuilderBase::CreateBinaryIntrinsic 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=6264458064691200 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 40756] New: Compile error(Segmentation fault) occurs when -O2 or more is set
https://bugs.llvm.org/show_bug.cgi?id=40756
Bug ID: 40756
Summary: Compile error(Segmentation fault) occurs when -O2 or
more is set
Product: clang
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: -New Bugs
Assignee: unassignedclangb...@nondot.org
Reporter: ueno.masak...@jp.fujitsu.com
CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org,
neeil...@live.com, richard-l...@metafoo.co.uk
Created attachment 21487
--> https://bugs.llvm.org/attachment.cgi?id=21487&action=edit
BUG REPORT(bug499-2a2a42.c, bug499-2a2a42.sh)
When compiling the following program(bug499.c) with -O2 or more, Segmentation
fault occurs and output the following message.
* Tail of error message
PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT:
Preprocessed source(s) and associated run script(s) are located at:
clang-9: note: diagnostic msg: /tmp/bug499-2a2a42.c
clang-9: note: diagnostic msg: /tmp/bug499-2a2a42.sh
clang-9: note: diagnostic msg:
* source program (bug499.c)
#include
int main () {
int i=0,j=0;
int v1=1,v2=2,v3=3;
for(i=0;i<1;i++) {
for(j=0; j<29; ++j) {
v3 = (v1 + v3) *v1;
v1=v2 * v3;
}
v2=1;
}
printf("%d %d %d \n",v1,v2,v3);
return 0;
}
--
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 40734] [InstCombine] Cannot create binary operator with two operands of differing type!
https://bugs.llvm.org/show_bug.cgi?id=40734 Hans Wennborg changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #8 from Hans Wennborg --- Merged in r354252. Thanks! -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 40331] [meta] 8.0.0 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=40331 Bug 40331 depends on bug 40734, which changed state. Bug 40734 Summary: [InstCombine] Cannot create binary operator with two operands of differing type! https://bugs.llvm.org/show_bug.cgi?id=40734 What|Removed |Added Status|CONFIRMED |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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 40331] [meta] 8.0.0 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=40331 Bug 40331 depends on bug 40745, which changed state. Bug 40745 Summary: Merge r353642 to the 8.0 branch https://bugs.llvm.org/show_bug.cgi?id=40745 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 40745] Merge r353642 to the 8.0 branch
https://bugs.llvm.org/show_bug.cgi?id=40745 Hans Wennborg changed: What|Removed |Added Status|NEW |RESOLVED CC||h...@chromium.org Resolution|--- |FIXED --- Comment #1 from Hans Wennborg --- Merged in r354253. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 40593] Test case clangd/background-index.test fails when path contains special characters
https://bugs.llvm.org/show_bug.cgi?id=40593 Kadir Cetinkaya changed: What|Removed |Added Status|CONFIRMED |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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 40331] [meta] 8.0.0 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=40331 Bug 40331 depends on bug 40746, which changed state. Bug 40746 Summary: Please backport multiple LLDB fixes to 8.0.0 https://bugs.llvm.org/show_bug.cgi?id=40746 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 40746] Please backport multiple LLDB fixes to 8.0.0
https://bugs.llvm.org/show_bug.cgi?id=40746 Hans Wennborg changed: What|Removed |Added CC||h...@chromium.org Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #2 from Hans Wennborg --- Merged in r354254 and r354255, respectively. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 40757] New: Compilation does not end when -O3 or more is set.
https://bugs.llvm.org/show_bug.cgi?id=40757
Bug ID: 40757
Summary: Compilation does not end when -O3 or more is set.
Product: new-bugs
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: new bugs
Assignee: unassignedb...@nondot.org
Reporter: ueno.masak...@jp.fujitsu.com
CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org
When compiling the following program(bug498.c) with -O3 or more, compilation
does not end.
I think there is something wrong with Loop Strength Reduction Pass.
This problem can be avoided by the -mllvm -disable-lsr option.
* source program(bug498.c)
#include
int main () {
int i,j,l=0,m=3,n=40;
unsigned long v1=1,v2=2,v3=3;
int a[50][50],b[50][50];
for (i=0; i<50; i++) {
for (j=0; j<50; j++) {
a[i][j]=0;
b[i][j]=1;
}
}
for(i=0;i<10;i++) {
for (l=0; l<4; l++) {
for(m=0; m<30; m++) {
for(j=0;j<2;j++) {
v3=v2 * v2;
}
v1=v3 - v1;
v2=v1 - i;
b[i][j]=a[i][j]+b[i][j];
}
}
}
printf("%lu %lu %lu %d\n",v1,v2,v3, b[0][0]);
return 0;
}
* compile/exec log using -mllvm -disable-lsr option
$ clang -O3 bug498.c -mllvm -disable-lsr
$ ./a.out
12145924650467887591 12145924650467887582 3040934746218291456 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
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 40331] [meta] 8.0.0 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=40331 Bug 40331 depends on bug 40730, which changed state. Bug 40730 Summary: [X86][AVX] lowerShuffleAsLanePermuteAndPermute - incomplete lane shuffle mask https://bugs.llvm.org/show_bug.cgi?id=40730 What|Removed |Added Status|CONFIRMED |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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 40730] [X86][AVX] lowerShuffleAsLanePermuteAndPermute - incomplete lane shuffle mask
https://bugs.llvm.org/show_bug.cgi?id=40730 Hans Wennborg changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #7 from Hans Wennborg --- (In reply to Simon Pilgrim from comment #6) > Fixed in trunk at rL354117 > > @Hans - please give it a while and then cherry pick r354034 + r354117 Thanks! Merged them together in r354260. Please let me know if there are any follow-ups. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 40758] New: [X86][SSE] Adjust shouldFoldShiftPairToMask for btver2 targets for uniform constant shifts
https://bugs.llvm.org/show_bug.cgi?id=40758 Bug ID: 40758 Summary: [X86][SSE] Adjust shouldFoldShiftPairToMask for btver2 targets for uniform constant shifts 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: andrea.dibia...@gmail.com, craig.top...@gmail.com, llvm-bugs@lists.llvm.org, llvm-...@redking.me.uk, spatel+l...@rotateright.com As discussed on https://reviews.llvm.org/D58225, for the btver2 (Jaguar) target (and maybe some others), it would be better to use 2 uniform constant shifts than a shift and a mask loaded from constant pool (even if the mask is lifted out of a hot loop I don't think it gives any benefit). This probably means yet another Feature bit. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 36281] [clangd]Â Find definitions does not consider template specialization
https://bugs.llvm.org/show_bug.cgi?id=36281 Kadir Cetinkaya changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 38754] [DebugInfo@O2][Dexter] Illegal value appears in variable when conditional blocks folded
https://bugs.llvm.org/show_bug.cgi?id=38754 Bug 38754 depends on bug 39786, which changed state. Bug 39786 Summary: [DebugInfo@O2] InstCombine pointer type-cast sinking needlessly reduces dbg location ranges https://bugs.llvm.org/show_bug.cgi?id=39786 What|Removed |Added Status|CONFIRMED |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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 38768] [meta][DebugInfo] Umbrella bug for poor debug experiences
https://bugs.llvm.org/show_bug.cgi?id=38768 Bug 38768 depends on bug 39786, which changed state. Bug 39786 Summary: [DebugInfo@O2] InstCombine pointer type-cast sinking needlessly reduces dbg location ranges https://bugs.llvm.org/show_bug.cgi?id=39786 What|Removed |Added Status|CONFIRMED |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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 39786] [DebugInfo@O2] InstCombine pointer type-cast sinking needlessly reduces dbg location ranges
https://bugs.llvm.org/show_bug.cgi?id=39786 Jeremy Morse changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Fixed By Commit(s)||353936 -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 40759] New: [X86] Compiler wrongly emits temporal stores when vectorizing a scalar nontemporal memcpy loop.
https://bugs.llvm.org/show_bug.cgi?id=40759
Bug ID: 40759
Summary: [X86] Compiler wrongly emits temporal stores when
vectorizing a scalar nontemporal memcpy loop.
Product: libraries
Version: trunk
Hardware: PC
OS: Windows NT
Status: NEW
Severity: enhancement
Priority: P
Component: Backend: X86
Assignee: unassignedb...@nondot.org
Reporter: andrea.dibia...@gmail.com
CC: craig.top...@gmail.com, llvm-bugs@lists.llvm.org,
llvm-...@redking.me.uk, spatel+l...@rotateright.com
Example:
```
void foo(unsigned *A, unsigned *B, unsigned Elts) {
for (unsigned I = 0; I < Elts; ++I) {
unsigned X = A[I];
__builtin_nontemporal_store(X, &B[I]);
}
}
```
> clang -O2 -march=btver2 -S -o -
```
.LBB0_8:# %for.body
movl(%rdi,%rcx,4), %edx
movntil %edx, (%rsi,%rcx,4) # <<== OK. Nontemporal store.
incq%rcx
cmpq%rcx, %rax
jne .LBB0_8
retq
.LBB0_5:# %vector.ph
movl%eax, %ecx
xorl%edx, %edx
andl$-32, %ecx
.p2align4, 0x90
.LBB0_6:# %vector.body
vmovups (%rdi,%rdx,4), %ymm0
vmovups 32(%rdi,%rdx,4), %ymm1
vmovups 64(%rdi,%rdx,4), %ymm2
vmovups 96(%rdi,%rdx,4), %ymm3
vmovups %ymm0, (%rsi,%rdx,4)# <<== WRONG. Temporal vector store.
vmovups %ymm1, 32(%rsi,%rdx,4) # Same...
vmovups %ymm2, 64(%rsi,%rdx,4) # Same...
vmovups %ymm3, 96(%rsi,%rdx,4) # Same...
addq$32, %rdx
cmpq%rdx, %rcx
jne .LBB0_6
# %bb.7:# %middle.block
cmpq%rax, %rcx
jne .LBB0_8
```
On X86, (V)MOVNTPS can be used to do non-temporal vector stores.
However, VMOVNTPS requires that the memory operand for the destination is
aligned by 16-bytes (for the 128-bit stores), or 32-bytes (for the 256-bit
stores).
In this example, store instructions are marked as 4-bytes aligned.
When the loop vectorizer kicks in, it generates a vector loop body, and all
vector stores are correctly annotated with metadata flag "!nontemporal" and
aligment 4.
However, on x86 there is no support for unaligned nontemporal stores.
So, ISel falls back to selecting normal (i.e. "temporal") unaligned stores (see
the VMOVUPS from the assembly above).
When vectorizing a memcpy-like loop, we should probably check if the target has
support for unaligned nontemporal vector stores before transforming the loop.
Otherwise, we risk to accidentally introduce temporal stores that pollute the
caches.
--
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 40760] New: Make llvm-symbolizer behave close to GNU's addr2line
https://bugs.llvm.org/show_bug.cgi?id=40760 Bug ID: 40760 Summary: Make llvm-symbolizer behave close to GNU's addr2line Product: tools Version: trunk Hardware: All OS: All Status: NEW Severity: enhancement Priority: P Component: llvm-symbolizer Assignee: unassignedb...@nondot.org Reporter: ikud...@accesssoftek.com CC: llvm-bugs@lists.llvm.org We have several differences in the tool's behavior which make it hard to be a drop-in replacement for addr2line. In particular: * llvm-symbolizer has -i, -f and -C options "on" by default; * llvm-symbolizer prints line and position while addr2line prints only line. * addr2line allows more flexible usage of the "-e" option. For example "-fe " and "-e" command lines are allowed. While we probably should not change the behavior of the existing tool, which might affect parsers of its output, can we have another tool, say, "llvm-addr2line", which would behave close to GNU's one? Something similar to that we have with "llvm-readobj"/"llvm-readelf". -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 40761] New: sanitizers broken on freebsd in 8.0.0-rc2
https://bugs.llvm.org/show_bug.cgi?id=40761 Bug ID: 40761 Summary: sanitizers broken on freebsd in 8.0.0-rc2 Product: compiler-rt Version: 8.0 Hardware: PC OS: FreeBSD Status: NEW Severity: normal Priority: P Component: compiler-rt Assignee: unassignedb...@nondot.org Reporter: h...@chromium.org CC: dimi...@andric.com, llvm-bugs@lists.llvm.org Blocks: 40331 Dimitry reported that the sanitizers are broken on FreeBsd in 8.0.0-rc2: http://lists.llvm.org/pipermail/llvm-dev/2019-February/130236.html "Unfortunately I had to disable compiler-rt for this test run, as most of the sanitizers are totally broken. They get into an endless recursive loop between AsanTSDGet() and the __tls_get_addr() interceptor, and crash with DEADLYSIGNAL due to stack overflow. I haven't found the time to further diagnose this." Referenced Bugs: https://bugs.llvm.org/show_bug.cgi?id=40331 [Bug 40331] [meta] 8.0.0 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 40762] New: Clang hangs with "too many errors emitted"
https://bugs.llvm.org/show_bug.cgi?id=40762 Bug ID: 40762 Summary: Clang hangs with "too many errors emitted" Product: clang Version: 7.0 Hardware: PC OS: All Status: NEW Severity: normal Priority: P Component: -New Bugs Assignee: unassignedclangb...@nondot.org Reporter: thei...@gmail.com CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org, neeil...@live.com, richard-l...@metafoo.co.uk Created attachment 21488 --> https://bugs.llvm.org/attachment.cgi?id=21488&action=edit example *Overview* Clang hangs infinitely on a specific source code just after printing diagnostics line: fatal error: too many errors emitted, stopping now [-ferror-limit=] The reproducing example unfortunately depends on boost::test. I think a bug is actually caused by heaviness of boost::test. I checked the error with Boost 1.68 and Boost 1.62 from Debian. *Steps to Reproduce* 1. Install boost headers - 1.68 works fine, 1.62 on Debian works too (libboost-dev) 2. Compile attached file: clang++ --std=c++11 -O0 -c main.cxx *Actual Results* 1. Compiler gives an error and hangs (at least 30 minutes) *Expected Results* 1. Should give error and exit with error code *Build Date & Hardware* - Reproduced on Linux with 7.0.1 and 3.8. - Reproduced on macOS with LLVM-provided clang 7.0.0 and apple-clang 10.0.0. - GCC works fine. Stacktrace when SIGINT-ed: ``` fatal error: too many errors emitted, stopping now [-ferror-limit=] ^C Program received signal SIGINT, Interrupt. 0x77bccb0a in __waitpid (pid=32641, stat_loc=0x7fffca14, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:29 29 ../sysdeps/unix/sysv/linux/waitpid.c: No such file or directory. (gdb) bt #0 0x77bccb0a in __waitpid (pid=32641, stat_loc=0x7fffca14, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:29 #1 0x01cea90f in llvm::sys::Wait(llvm::sys::ProcessInfo const&, unsigned int, bool, std::__cxx11::basic_string, std::allocator >*) () #2 0x01ce9837 in llvm::sys::ExecuteAndWait(llvm::StringRef, llvm::ArrayRef, llvm::Optional >, llvm::ArrayRef >, unsigned int, unsigned int, std::__cxx11::basic_string, std::allocator >*, bool*) () #3 0x0216bc22 in clang::driver::Command::Execute(llvm::ArrayRef >, std::__cxx11::basic_string, std::allocator >*, bool*) const () #4 0x02141ab5 in clang::driver::Compilation::ExecuteCommand(clang::driver::Command const&, clang::driver::Command const*&) const () #5 0x02141d8a in clang::driver::Compilation::ExecuteJobs(clang::driver::JobList const&, llvm::SmallVectorImpl >&) const () #6 0x0215782b in clang::driver::Driver::ExecuteCompilation(clang::driver::Compilation&, llvm::SmallVectorImpl >&) () #7 0x009326ef in main () (gdb)% ``` -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 12979 in oss-fuzz: llvm/clang-fuzzer: Stack-overflow in processTypeAttrs
Comment #2 on issue 12979 by ClusterFuzz-External: llvm/clang-fuzzer: Stack-overflow in processTypeAttrs https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12979#c2 ClusterFuzz has detected this issue as fixed in range 201902170420:201902180416. Detailed report: https://oss-fuzz.com/testcase?key=5630788740055040 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: 0x7ffcff237e60 Crash State: processTypeAttrs ConvertDeclSpecToType GetDeclSpecTypeForDeclarator Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201902060426:201902070427 Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201902170420:201902180416 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5630788740055040 See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for instructions to reproduce this bug locally. 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 12979 in oss-fuzz: llvm/clang-fuzzer: Stack-overflow in processTypeAttrs
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #3 on issue 12979 by ClusterFuzz-External: llvm/clang-fuzzer: Stack-overflow in processTypeAttrs https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12979#c3 ClusterFuzz testcase 5630788740055040 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 37371] All tests in LinuxCoreTestCase fail on Windows
https://bugs.llvm.org/show_bug.cgi?id=37371 lab...@google.com changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED CC||lab...@google.com --- Comment #1 from lab...@google.com --- (Accidentally) fixed by r354273. The error was due to a python3 incompatibility (/-division results in floats on py3). -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 11567 in oss-fuzz: llvm/clang-fuzzer: Null-dereference READ in diagnoseBadTypeAttribute
Updates: Labels: Deadline-Approaching Comment #6 on issue 11567 by sheriff...@chromium.org: llvm/clang-fuzzer: Null-dereference READ in diagnoseBadTypeAttribute https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=11567#c6 This bug is approaching its deadline for being fixed, and will be automatically derestricted within 7 days. If a fix is planned within 2 weeks after the deadline has passed, a grace extension can be granted. - Your friendly Sheriffbot -- 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 40763] New: std::cout is more than twice as slow as libstdc++
https://bugs.llvm.org/show_bug.cgi?id=40763
Bug ID: 40763
Summary: std::cout is more than twice as slow as libstdc++
Product: libc++
Version: 7.0
Hardware: Macintosh
OS: MacOS X
Status: NEW
Keywords: performance
Severity: enhancement
Priority: P
Component: All Bugs
Assignee: unassignedclangb...@nondot.org
Reporter: husseyde...@gmail.com
CC: llvm-bugs@lists.llvm.org, mclow.li...@gmail.com
I saw a lot of people complaining about this on Stack Overflow and the like but
I didn't see any bug reports.
std::cout is at least 2x slower in libc++ than it is in libstdc++. In
libstdc++, std::cout has about the same performance as stdio (and it is faster
with sync_with_stidio(false)), but in libc++, it can be more than 2x slower
than stdio.
Clang 7.0.1 vs GCC 8.2.0 (both from Homebrew)
Source code:
#include
#include
#include
#include
int main() {
// true or false, libstdc++ is still much faster than libc++
std::ios_base::sync_with_stdio(true);
// sorry I prefer clock()
auto clock = [] () { return std::chrono::high_resolution_clock::now(); };
auto start = clock();
for (std::size_t i = 0; i < 1000; i++) {
std::cout << i << '\n';
}
auto end = clock();
std::fprintf(stderr, "%llu\n",
std::chrono::duration_cast(end - start).count());
// show printf for comparison
start = clock();
for (std::size_t i = 0; i < 1000; i++) {
std::printf("%zu\n", i);
}
end = clock();
std::fprintf(stderr, "%llu\n",
std::chrono::duration_cast(end - start).count());
}
Problem:
libc++'s std::cout is twice as slow as libstdc++'s.
~ $ clang++ -O3 bench.cpp -std=c++2a
~ $ ./a.out > /dev/null
690
265
~ $ g++-8 -O3 bench.cpp -std=c++2a
~ $ ./a.out > /dev/null
375
284
To prove it isn't a GCC optimization, I forced Clang to use libstdc++:
~ $ clang++ bench.cpp -O3 -stdlib=libstdc++ -std=c++2a -isystem
/usr/local/opt/gcc/include/c++/8.2.0/ -isystem
/usr/local/opt/gcc/include/c++/8.2.0/x86_64-apple-darwin17.7.0/ -L
/usr/local/opt/gcc/lib/gcc/8
warning: include path for stdlibc++ headers not found; pass '-stdlib=libc++' on
the command line to use the libc++ standard library instead
[-Wstdlibcxx-not-found]
1 warning generated.
~ $ ./a.out > /dev/null
320
245
Changing sync_with_stdio to false yields cout being faster than printf on
libstdc++, but the same on libc++:
clang++ with libc++:
~ $ ./a.out > /dev/null
697
290
g++ (note: varies a lot)
~ $ ./a.out > /dev/null
164
266
clang++ with libstdc++:
~ $ ./a.out > /dev/null
163
269
Something is clearly off here. Even though stdio has the same performance, the
performance difference is massive.
Note: Xcode 10's Clang has the same effect, and changing the clock printf to
cerr has no effect.
macOS 10.14.2 Mojave (Mojave Patcher)
2.0 GHz MacBook Pro (15-inch, Early 2011)
8 GB RAM
500 GB SSD
2.0 GHz Intel Core i7 "Sandy Bridge" (2635QM), quad core + HT
clang++ 7.0.2
g++ 8.2.0
--
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 40764] New: Regression: is_trivially_destructible fails with top-of-tree building Swift top-of-tree
https://bugs.llvm.org/show_bug.cgi?id=40764 Bug ID: 40764 Summary: Regression: is_trivially_destructible fails with top-of-tree building Swift top-of-tree Product: clang Version: trunk Hardware: PC OS: All Status: NEW Severity: enhancement Priority: P Component: C++ Assignee: unassignedclangb...@nondot.org Reporter: d...@znu.io CC: blitzrak...@gmail.com, dgre...@apple.com, erik.pilking...@gmail.com, llvm-bugs@lists.llvm.org, richard-l...@metafoo.co.uk is_trivially_destructible is failing with top-of-tree clang building top-of-tree swift. It seems like implicit destructors are spuriously being created when they shouldn't be. Please consider looking at this preprocessed file: http://znu.io/Type.cpp Which generates the following spurious error: /home/dave/s/uu/swift/include/swift/AST/TypeNodes.def:146:1: error: static_assert failed due to requirement 'IsTriviallyDestructible::value' "Types are BumpPtrAllocated; the destructor is never called" static_assert(IsTriviallyDestructible::value, "Types are BumpPtrAllocated; the destructor is never called"); ^ ~~~ -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 40765] New: non-ascii source files cannot be shown in scan-view
https://bugs.llvm.org/show_bug.cgi?id=40765 Bug ID: 40765 Summary: non-ascii source files cannot be shown in scan-view Product: clang Version: trunk Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: Static Analyzer Assignee: dcough...@apple.com Reporter: johan...@sipsolutions.net CC: dcough...@apple.com, llvm-bugs@lists.llvm.org We just get: INTERNAL ERROR Traceback (most recent call last): File "/usr/share/clang/scan-view-9/share/ScanView.py", line 232, in do_GET SimpleHTTPRequestHandler.do_GET(self) File "/usr/lib/python2.7/SimpleHTTPServer.py", line 45, in do_GET f = self.send_head() File "/usr/share/clang/scan-view-9/share/ScanView.py", line 712, in send_head return self.send_path(path) File "/usr/share/clang/scan-view-9/share/ScanView.py", line 727, in send_path return self.send_patched_file(path, ctype) File "/usr/share/clang/scan-view-9/share/ScanView.py", line 774, in send_patched_file return self.send_string(data, ctype, mtime=fs.st_mtime) File "/usr/share/clang/scan-view-9/share/ScanView.py", line 747, in send_string encoded_s = s.encode() UnicodeDecodeError: 'ascii' codec can't decode byte 0x92 in position 62: ordinal not in range(128) In ScanView.py line 747 we have: encoded_s = s.encode() changing that to just encoded_s = s appears to work around the problem. It's not clear what _should_ be done about this though. Clearly, C source files can be any sort of encoding, in particular in comments, and we can't really know which it is. Most files we have are UTF-8, but some older ones are ISO-8859-1 or similar encodings, depending on whatever the author wrote ... I guess ideally it's just passed through more or less, and then worst case some stuff shows up as garbage in the browser, still better than crashing. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 40766] New: Complete implementation of fewerElementsVector legalization method in GlobalISel
https://bugs.llvm.org/show_bug.cgi?id=40766 Bug ID: 40766 Summary: Complete implementation of fewerElementsVector legalization method in GlobalISel Product: libraries Version: trunk Hardware: All OS: All Status: NEW Severity: enhancement Priority: P Component: GlobalISel Assignee: unassignedb...@nondot.org Reporter: rteres...@apple.com CC: llvm-bugs@lists.llvm.org, quentin.colom...@gmail.com It looks like the current version of the fewerElementsVector legalization method in GlobalISel can handle its inputs iff originalNumberOfElements % requestedNumberOfElements is either 0 or 1 (the vector could be split into equally sized parts or the reminder is exactly a single scalar). It's hard to call such a behavior orthogonal and well expected, and it looks like it may cause subtle and hard to notice bugs and / or force people to do non-obvious work-arounds, maybe we need to improve this. See https://reviews.llvm.org/D58123#inline-516061 and around for more details. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 40767] New: crash from IRBuilder with intrinsic already declared with type alias/substitute
https://bugs.llvm.org/show_bug.cgi?id=40767
Bug ID: 40767
Summary: crash from IRBuilder with intrinsic already declared
with type alias/substitute
Product: libraries
Version: trunk
Hardware: PC
OS: All
Status: NEW
Severity: enhancement
Priority: P
Component: Scalar Optimizations
Assignee: unassignedb...@nondot.org
Reporter: spatel+l...@rotateright.com
CC: llvm-bugs@lists.llvm.org
This is the same root cause as this fuzzer bug, but I made a slightly simpler
repro for instcombine:
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=13174
; Declaration with return type alias(?)
%0 = type { i32, i1 }
declare %0 @llvm.uadd.with.overflow.i32(i32, i32)
define i32 @no_carryin_i32(i32 %x, i32 %y, i8* %p) {
%s = call { i8, i32 } @llvm.x86.addcarry.32(i8 0, i32 %x, i32 %y)
%ov = extractvalue { i8, i32 } %s, 0
store i8 %ov, i8* %p
%r = extractvalue { i8, i32 } %s, 1
ret i32 %r
}
declare { i8, i32 } @llvm.x86.addcarry.32(i8, i32, i32)
The existing intrinsic declaration causes a crash when we try to create a new
call to that intrinsic using IRBuilder.
$ opt -instcombine addcarry.ll -S
Assertion failed: (isa(Val) && "cast() argument of incompatible type!"),
function cast, file
/Users/spatel/GitHub/llvm-project/llvm/include/llvm/Support/Casting.h, line
254.
Stack dump:
0. Program arguments: ./opt -instcombine addcarry.ll -S
1. Running pass 'Function Pass Manager' on module 'addcarry.ll'.
2. Running pass 'Combine redundant instructions' on function
'@no_carryin_i32'
0 opt 0x0001035e8ab8
llvm::sys::PrintStackTrace(llvm::raw_ostream&) + 40
1 opt 0x0001035e79e8 llvm::sys::RunSignalHandlers() +
248
2 opt 0x0001035e90d8 SignalHandler(int) + 264
3 libsystem_platform.dylib 0x7fff75ac9b3d _sigtramp + 29
4 libsystem_platform.dylib 0x0020 _sigtramp + 2320721152
5 libsystem_c.dylib0x7fff759871c9 abort + 127
6 libsystem_c.dylib0x7fff7594f868 basename_r + 0
7 opt 0x000102f1d0d2
llvm::Intrinsic::getDeclaration(llvm::Module*, llvm::Intrinsic::ID,
llvm::ArrayRef) + 210
8 opt 0x000102f2713e
llvm::IRBuilderBase::CreateIntrinsic(llvm::Intrinsic::ID,
llvm::ArrayRef, llvm::ArrayRef, llvm::Instruction*,
llvm::Twine const&) + 62
9 opt 0x0001030fdc61
llvm::InstCombiner::visitCallInst(llvm::CallInst&) + 10929
--
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 40768] New: it is not, in general, safe to speculatively execute a shift
https://bugs.llvm.org/show_bug.cgi?id=40768
Bug ID: 40768
Summary: it is not, in general, safe to speculatively execute a
shift
Product: new-bugs
Version: trunk
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: new bugs
Assignee: unassignedb...@nondot.org
Reporter: reg...@cs.utah.edu
CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org
The optimization below takes a function that is defined when argument %0 is
negative and turns it into a function that returns poison when argument %0 is
negative.
Many of the UB problems that we see in LLVM require us to answer difficult
semantic questions before they can be resolved, but this one doesn't seem like
that. Rather, it's a straightforward example of something that an LLVM pass
just cannot do.
*** IR Dump Before Simplify the CFG ***
; Function Attrs: nounwind uwtable
define internal fastcc i32 @f(i32) unnamed_addr #0 {
%2 = icmp slt i32 %0, 0
br i1 %2, label %6, label %3
; :3: ; preds = %1
%4 = lshr i32 127, %0
%5 = icmp slt i32 %4, 1
br i1 %5, label %6, label %7
; :6: ; preds = %3, %1
br label %7
; :7: ; preds = %3, %6
%8 = phi i32 [ 1, %6 ], [ 0, %3 ]
ret i32 %8
}
*** IR Dump After Simplify the CFG ***
; Function Attrs: nounwind uwtable
define internal fastcc i32 @f(i32) unnamed_addr #0 {
%2 = icmp slt i32 %0, 0
%3 = lshr i32 127, %0
%4 = icmp slt i32 %3, 1
%5 = or i1 %2, %4
%6 = select i1 %5, i32 1, i32 0
ret i32 %6
}
--
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 13193 in oss-fuzz: llvm/clang-fuzzer: Stack-overflow in llvm::StringMapImpl::LookupBucketFor
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com, igm...@gmail.com, mit...@google.com, bigchees...@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-02-19 Type: Bug New issue 13193 by ClusterFuzz-External: llvm/clang-fuzzer: Stack-overflow in llvm::StringMapImpl::LookupBucketFor https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=13193 Detailed report: https://oss-fuzz.com/testcase?key=5638557312483328 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: 0x7ffcc2e9be88 Crash State: llvm::StringMapImpl::LookupBucketFor std::__1::pair, bool> llvm::Stri clang::Preprocessor::LookUpIdentifierInfo Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201804250613:201804260543 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5638557312483328 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 40769] New: stdatomic.h not C11 compliant with Objective C framework
https://bugs.llvm.org/show_bug.cgi?id=40769 Bug ID: 40769 Summary: stdatomic.h not C11 compliant with Objective C framework Product: clang Version: trunk Hardware: Macintosh OS: MacOS X Status: NEW Severity: normal Priority: P Component: Headers Assignee: unassignedclangb...@nondot.org Reporter: theboywonder2...@yahoo.co.jp CC: craig.top...@gmail.com, llvm-bugs@lists.llvm.org, richard-l...@metafoo.co.uk On Mac OSX 10.4 (Mojave) with Apple LLVM Version 10.0.0 (clang-1000.11.45.5) I have written my own for multiple platforms that don't support it. It is designed to work under all C11-compliant compilers. My own has a gate that says: #ifndef __STDC_NO_ATOMICS__ # error ... error text goes here ... #endif As my entire source repository is a shared repository, this file is visible during compilation on all platforms. I use "-idirafter" to make sure that any file provided by the hosted environment gets picked up before my file. If clang on Mac OSX is invoked on a file with ".c" extension then the hosted environment doesn't supply . In this case __STDC_NO_ATOMICS__ is defined, my custom file is called, and it compiles cleanly. However, for the Objective C framework, LLVM headers provide a . Inside this file is the following: #if __STDC_HOSTED__ && __has_include_next() # include_next #endif The extension "include_next" searches "-idirafter" and sees my and includes it, but it does *not* define __STDC_NO_ATOMICS__ so the gate within my custom is entered and the build always fails. This appears to be a violation of C2011. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 40770] New: lld error message for undefined symbol lacks information about visibility
https://bugs.llvm.org/show_bug.cgi?id=40770
Bug ID: 40770
Summary: lld error message for undefined symbol lacks
information about visibility
Product: new-bugs
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: new bugs
Assignee: unassignedb...@nondot.org
Reporter: mh+l...@glandium.org
CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org
```
$ cat foo.c
__attribute__((visibility("hidden"))) void* getdate(char*);
void* foo(char* s) {
return getdate(s);
}
$ clang -fuse-ld=lld -shared -fPIC foo.c -o foo.so
ld.lld: error: undefined symbol: getdate
>>> referenced by foo.c
>>> /tmp/foo-717a38.o:(foo)
clang: error: linker command failed with exit code 1 (use -v to see invocation)
```
GNU ld.bfd and gold both report the fact the symbol is hidden in their error
message:
```
$ clang-7 -fuse-ld=ld -shared -fPIC foo.c -o foo.so
/usr/bin/ld: /tmp/foo-8f3391.o: in function `foo':
foo.c:(.text+0x11): undefined reference to `getdate'
/usr/bin/ld: foo.so: hidden symbol `getdate' isn't defined
/usr/bin/ld: final link failed: bad value
clang: error: linker command failed with exit code 1 (use -v to see invocation)
$ LANG=C clang-7 -fuse-ld=gold -shared -fPIC foo.c -o foo.so
/usr/bin/ld.gold: error: hidden symbol 'getdate' is not defined locally
clang: error: linker command failed with exit code 1 (use -v to see invocation)
```
--
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 13195 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-strength_reduce: Floating-point-exception in LSRInstance::GenerateAllReuseFormulae
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com, igm...@gmail.com, mit...@google.com, bigchees...@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-02-19 Type: Bug New issue 13195 by ClusterFuzz-External: llvm/llvm-opt-fuzzer--x86_64-strength_reduce: Floating-point-exception in LSRInstance::GenerateAllReuseFormulae https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=13195 Detailed report: https://oss-fuzz.com/testcase?key=5675778002386944 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: Floating-point-exception Crash Address: Crash State: LSRInstance::GenerateAllReuseFormulae LSRInstance::LSRInstance ReduceLoopStrength Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201811280235:201811290236 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5675778002386944 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 40771] New: Segfault in SROA while using the overload deduction guide pattern and copy capture
https://bugs.llvm.org/show_bug.cgi?id=40771
Bug ID: 40771
Summary: Segfault in SROA while using the overload deduction
guide pattern and copy capture
Product: clang
Version: trunk
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: -New Bugs
Assignee: unassignedclangb...@nondot.org
Reporter: spyraaleksan...@gmail.com
CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org,
neeil...@live.com, richard-l...@metafoo.co.uk
Godbolt demonstrating the issue: https://godbolt.org/z/Vs3QZe
Clang options: -std=c++17 -O1
#include
template struct ctad : Ts... {};
template ctad(Ts...)->ctad;
void crash()
{
std::string s;
ctad c {[s](short){}, [s](long){}};
}
--
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
