[llvm-bugs] [Bug 34888] PowerPC64: Code hits assert in MachineOperand.h:280 - This is not a register operand!
https://bugs.llvm.org/show_bug.cgi?id=34888 Nemanja Ivanovic changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #2 from Nemanja Ivanovic --- Fixed in https://reviews.llvm.org/rL315285. -- 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 34901] New: fatal error: error in backend: Wasm COMDATs only support SelectionKind:Any, 'function' cannot be lowered
https://bugs.llvm.org/show_bug.cgi?id=34901 Bug ID: 34901 Summary: fatal error: error in backend: Wasm COMDATs only support SelectionKind:Any, 'function' cannot be lowered Product: clang Version: trunk Hardware: PC OS: Windows NT Status: NEW Severity: enhancement Priority: P Component: -New Bugs Assignee: unassignedclangb...@nondot.org Reporter: m...@chavfreezone.me.uk CC: llvm-bugs@lists.llvm.org Created attachment 19258 --> https://bugs.llvm.org/attachment.cgi?id=19258&action=edit preprocessed source and associated run script Testing the wasm32-unknown-unknown-wasm target in an attempt to see how stable the wasm backend is with a test case, but get the following error: fatal error: error in backend: Wasm COMDATs only support SelectionKind::Any, '_ZN16PermutationTable7SetSeedEi' cannot be lowered. clang.exe: error: clang frontend command failed with exit code 70 (use -v to see invocation) clang version is 6.0.0 (trunk 314790) (llvm/trunk 315211) Context: The test case I wrote was in relation to the issue I raised here: https://github.com/WebAssembly/binaryen/issues/1215 in relation to the startup functions being exported with periods in their names which rendered them unaccessible in the browser. The code is stable when I add a main function and compile to it an exe on windows, and if I have clang output the bitcode and pass it through llc, s2wasm and wat2wasm I get a usable .wasm file (ignoring the fact that the startup function isn't accessible so all the GetPermAt function returns is 0s). Commands to produce the .wasm file from bitcode are below: > clang -c -v --target=wasm32 -std=c++14 -emit-llvm -Oz main.cpp > llc -O2 main.bc -o main.s > s2wasm main.s > main.wat > wat2wasm main.wat -o main.wasm -- 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 34902] New: [ARM]Improve switch-case lowering when optimizing for code size
https://bugs.llvm.org/show_bug.cgi?id=34902
Bug ID: 34902
Summary: [ARM]Improve switch-case lowering when optimizing for
code size
Product: new-bugs
Version: trunk
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: new bugs
Assignee: gab...@inf.u-szeged.hu
Reporter: gab...@inf.u-szeged.hu
CC: eas...@yandex.ru, kristof.be...@arm.com,
llvm-bugs@lists.llvm.org
GCC compiles to smaller switch-cases than LLVM when targeting ARM.
Example:
* Source
void func (int);
void foo (int a)
{
switch(a)
{
case 15:
func(5);
case 16:
func(59);
case 17:
func(515);
case 18:
func(65);
case 19:
func(8);
case 20:
func(15);
}
}
#
* GCC v7.1 generated assembly
#
** Options: -Os -marm -march=armv7-a
foo:
@ args = 0, pretend = 0, frame = 0
@ frame_needed = 0, uses_anonymous_args = 0
sub r0, r0, #15
push{r4, lr}
cmp r0, #5
ldrls pc, [pc, r0, asl #2]
b .L1
.L4:
.word .L3
.word .L5
.word .L6
.word .L7
.word .L8
.word .L9
.L3:
mov r0, #5
bl func
.L5:
mov r0, #59
bl func
.L6:
movwr0, #515
bl func
.L7:
mov r0, #65
bl func
.L8:
mov r0, #8
bl func
.L9:
mov r0, #15
pop {r4, lr}
b func
.L1:
pop {r4, pc}
#
* LLVM 6.0 generated assembly
#
** Options: -Oz -marm -march=armv7-a
foo:
.fnstart
@ BB#0: @ %entry
sub r0, r0, #15
cmp r0, #5
bxhilr
.save {r11, lr}
push{r11, lr}
.setfp r11, sp
mov r11, sp
adr r1, .LJTI0_0
lsl r0, r0, #2
ldr pc, [r0, r1]
@ BB#1:
.p2align2
.LJTI0_0:
.long .LBB0_2
.long .LBB0_3
.long .LBB0_4
.long .LBB0_5
.long .LBB0_6
.long .LBB0_7
.LBB0_2:@ %sw.bb
mov r0, #5
bl func
.LBB0_3:@ %sw.bb1
mov r0, #59
bl func
.LBB0_4:@ %sw.bb2
movwr0, #515
bl func
.LBB0_5:@ %sw.bb3
mov r0, #65
bl func
.LBB0_6:@ %sw.bb4
mov r0, #8
bl func
.LBB0_7:@ %sw.bb5
mov r0, #15
pop {r11, lr}
b func
--
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 34903] New: X86CallFrameOptimization wrongly assumes '= COPY %esp' is right after ADJCALLSTACKDOWN
https://bugs.llvm.org/show_bug.cgi?id=34903 Bug ID: 34903 Summary: X86CallFrameOptimization wrongly assumes '= COPY %esp' is right after ADJCALLSTACKDOWN Product: libraries Version: trunk Hardware: PC OS: Windows NT Status: NEW Severity: enhancement Priority: P Component: Backend: X86 Assignee: unassignedb...@nondot.org Reporter: zvi.racko...@intel.com CC: llvm-bugs@lists.llvm.org SelectionDAG inserts a copy of ESP into a virtual register. X86CallFrameOptimization assumes that the COPY, if present, is always right after the call-frame setup instruction (ADJCALLSTACKDOWN). This is a wrong assumption as the COPY can be located anywhere between the call-frame setup instruction and its first use. If the COPY happened to be located in a different location than what X86CallFrameOptimization assumed, visiting it while processing the call chain would lead to a conservative bail-out. Here's an example of .mir captured from movtopush.ll, function 'test9'. You can see that the instruction '%3 = copy %esp' is *not* located immediately after the adjcallstackdown32 instruction: callstackdown32 16, 0, 0, implicit-def dead %esp, implicit-def dead %eflags, implicit %esp %0 = copy %esp mov32mi %0, 1, _, 12, _, 4 :: (store 4 into stack + 12) mov32mi %0, 1, _, 8, _, 3 :: (store 4 into stack + 8) mov32mi %0, 1, _, 4, _, 2 :: (store 4 into stack + 4) mov32mi %0, 1, _, 0, _, 1 :: (store 4 into stack) callpcrel32 @good, csr_32, implicit %esp, implicit-def %esp adjcallstackup32 16, 0, implicit-def dead %esp, implicit-def dead %eflags, implicit %esp adjcallstackdown32 20, 0, 0, implicit-def dead %esp, implicit-def dead %eflags, implicit %esp %1 = mov32rm %stack.2.s, 1, _, 0, _ :: (load 4 from %stack.2.s, align 8) %2 = mov32rm %stack.2.s, 1, _, 4, _ :: (load 4 from %stack.2.s + 4) %3 = copy %esp mov32mr %3, 1, _, 4, _, killed %2 :: (store 4) mov32mr %3, 1, _, 0, _, killed %1 :: (store 4) %4 = lea32r %stack.0.p, 1, _, 0, _ mov32mr %3, 1, _, 16, _, killed %4 :: (store 4 into stack + 16) %5 = lea32r %stack.1.q, 1, _, 0, _ mov32mr %3, 1, _, 12, _, killed %5 :: (store 4 into stack + 12) mov32mi %3, 1, _, 8, _, 6 :: (store 4 into stack + 8) callpcrel32 @struct, csr_32, implicit %esp, implicit-def %esp adjcallstackup32 20, 0, implicit-def dead %esp, implicit-def dead %eflags, implicit %esp ret 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 http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 3134 in oss-fuzz: llvm: ASSERT: ParmVarDeclBits.ScopeDepthOrObjCQuals == scopeDepth && "truncation!"
Updates: Cc: v...@apple.com Comment #7 on issue 3134 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm: ASSERT: ParmVarDeclBits.ScopeDepthOrObjCQuals == scopeDepth && "truncation!" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3134#c7 (No comment was entered for this change.) -- 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 3133 in oss-fuzz: llvm: ASSERT: DelayedTypos.empty() && "Uncorrected typos!"
Updates: Cc: v...@apple.com Comment #8 on issue 3133 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm: ASSERT: DelayedTypos.empty() && "Uncorrected typos!" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3133#c8 (No comment was entered for this change.) -- 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 3135 in oss-fuzz: llvm: Stack-overflow in clang::Parser::ParseCastExpression
Updates: Cc: v...@apple.com Comment #6 on issue 3135 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm: Stack-overflow in clang::Parser::ParseCastExpression https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3135#c6 (No comment was entered for this change.) -- 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 3138 in oss-fuzz: llvm: Stack-overflow in clang::Parser::ParseDeclaratorInternal
Updates: Cc: v...@apple.com Comment #6 on issue 3138 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm: Stack-overflow in clang::Parser::ParseDeclaratorInternal https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3138#c6 (No comment was entered for this change.) -- 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 3145 in oss-fuzz: llvm: Stack-buffer-overflow in clang::Lexer::SkipLineComment
Updates: Cc: v...@apple.com Comment #7 on issue 3145 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm: Stack-buffer-overflow in clang::Lexer::SkipLineComment https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3145#c7 (No comment was entered for this change.) -- 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 3137 in oss-fuzz: llvm: ASSERT: CurPtr[-1] == '<' && CurPtr[0] == '#' && "Not a placeholder!"
Updates: Cc: v...@apple.com Comment #7 on issue 3137 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm: ASSERT: CurPtr[-1] == '<' && CurPtr[0] == '#' && "Not a placeholder!" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3137#c7 (No comment was entered for this change.) -- 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 3141 in oss-fuzz: llvm: ASSERT: !isTokenSpecial() && "Should consume special tokens with Consume*Token"
Updates: Cc: v...@apple.com Comment #6 on issue 3141 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm: ASSERT: !isTokenSpecial() && "Should consume special tokens with Consume*Token" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3141#c6 (No comment was entered for this change.) -- 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 3146 in oss-fuzz: llvm: ASSERT: Access != AS_none && "Access specifier is AS_none inside a record decl"
Updates: Cc: v...@apple.com Comment #6 on issue 3146 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm: ASSERT: Access != AS_none && "Access specifier is AS_none inside a record decl" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3146#c6 (No comment was entered for this change.) -- 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 3157 in oss-fuzz: llvm: ASSERT: !isNull() && "Cannot retrieve a NULL type pointer"
Updates: Cc: v...@apple.com Comment #6 on issue 3157 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm: ASSERT: !isNull() && "Cannot retrieve a NULL type pointer" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3157#c6 (No comment was entered for this change.) -- 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 3155 in oss-fuzz: llvm: ASSERT: CachedTokens[CachedLexPos-1].getLastLoc() == Tok.getAnnotationEndLoc() && "The a
Updates: Cc: v...@apple.com Comment #6 on issue 3155 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm: ASSERT: CachedTokens[CachedLexPos-1].getLastLoc() == Tok.getAnnotationEndLoc() && "The a https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3155#c6 (No comment was entered for this change.) -- 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 3176 in oss-fuzz: llvm: Stack-overflow in clang::StmtVisitorBase::Visit
Updates: Cc: v...@apple.com Comment #6 on issue 3176 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm: Stack-overflow in clang::StmtVisitorBasebool>::Visit https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3176#c6 (No comment was entered for this change.) -- 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 3192 in oss-fuzz: llvm: ASSERT: Result.isInvalid() && "C++ binary operator overloading is missing candidates!"
Updates: Cc: v...@apple.com Comment #6 on issue 3192 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm: ASSERT: Result.isInvalid() && "C++ binary operator overloading is missing candidates!" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3192#c6 (No comment was entered for this change.) -- 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 3178 in oss-fuzz: llvm: ASSERT: !CodeSynthesisContexts.empty()
Updates: Cc: v...@apple.com Comment #6 on issue 3178 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm: ASSERT: !CodeSynthesisContexts.empty() https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3178#c6 (No comment was entered for this change.) -- 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 3213 in oss-fuzz: llvm: ASSERT: !Prev.isAmbiguous() && "Cannot have an ambiguity in previous-declaration lookup"
Updates: Cc: v...@apple.com Comment #6 on issue 3213 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm: ASSERT: !Prev.isAmbiguous() && "Cannot have an ambiguity in previous-declaration lookup" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3213#c6 (No comment was entered for this change.) -- 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 3173 in oss-fuzz: llvm: Stack-overflow in clang::Parser::SkipUntil
Updates: Cc: v...@apple.com Comment #5 on issue 3173 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm: Stack-overflow in clang::Parser::SkipUntil https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3173#c5 (No comment was entered for this change.) -- 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 3194 in oss-fuzz: llvm: Abrt in llvm::llvm_unreachable_internal
Updates: Cc: v...@apple.com Comment #6 on issue 3194 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm: Abrt in llvm::llvm_unreachable_internal https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3194#c6 (No comment was entered for this change.) -- 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 3195 in oss-fuzz: llvm: Direct-leak in clang::Parser::ParseParameterDeclarationClause
Updates: Cc: v...@apple.com Comment #6 on issue 3195 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm: Direct-leak in clang::Parser::ParseParameterDeclarationClause https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3195#c6 (No comment was entered for this change.) -- 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 3211 in oss-fuzz: llvm: Stack-overflow in clang::StmtVisitorBase::Visit
Updates: Cc: v...@apple.com Comment #6 on issue 3211 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm: Stack-overflow in clang::StmtVisitorBase::Visit https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3211#c6 (No comment was entered for this change.) -- 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 3171 in oss-fuzz: llvm: ASSERT: RHS.U.VAL != 0 && "Divide by zero?"
Updates: Cc: v...@apple.com Comment #6 on issue 3171 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm: ASSERT: RHS.U.VAL != 0 && "Divide by zero?" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3171#c6 (No comment was entered for this change.) -- 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 3152 in oss-fuzz: llvm: Stack-overflow in clang::Lexer::Lex
Updates: Cc: v...@apple.com Comment #6 on issue 3152 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm: Stack-overflow in clang::Lexer::Lex https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3152#c6 (No comment was entered for this change.) -- 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 3169 in oss-fuzz: llvm: ASSERT: RHS.U.VAL != 0 && "Divide by zero?"
Updates: Cc: v...@apple.com Comment #6 on issue 3169 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm: ASSERT: RHS.U.VAL != 0 && "Divide by zero?" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3169#c6 (No comment was entered for this change.) -- 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 3161 in oss-fuzz: llvm: ASSERT: ResultKind != Found || Decls.size() == 1
Updates: Cc: v...@apple.com Comment #6 on issue 3161 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm: ASSERT: ResultKind != Found || Decls.size() == 1 https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3161#c6 (No comment was entered for this change.) -- 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 3168 in oss-fuzz: llvm: ASSERT: Access == AS_private || Access == AS_protected
Updates: Cc: v...@apple.com Comment #6 on issue 3168 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm: ASSERT: Access == AS_private || Access == AS_protected https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3168#c6 (No comment was entered for this change.) -- 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 3163 in oss-fuzz: llvm: ASSERT: Tok.is(tok::eof) && Tok.getEofData() == AttrEnd.getEofData()
Updates: Cc: v...@apple.com Comment #6 on issue 3163 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm: ASSERT: Tok.is(tok::eof) && Tok.getEofData() == AttrEnd.getEofData() https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3163#c6 (No comment was entered for this change.) -- 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 3222 in oss-fuzz: llvm: ASSERT: sizeof(Elf_Ehdr) <= Buf.size() && "Invalid buffer"
Updates: Cc: v...@apple.com Comment #5 on issue 3222 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm: ASSERT: sizeof(Elf_Ehdr) <= Buf.size() && "Invalid buffer" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3222#c5 (No comment was entered for this change.) -- 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 3219 in oss-fuzz: llvm: Heap-buffer-overflow in llvm::StringMapImpl::LookupBucketFor
Updates: Cc: v...@apple.com Comment #5 on issue 3219 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm: Heap-buffer-overflow in llvm::StringMapImpl::LookupBucketFor https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3219#c5 (No comment was entered for this change.) -- 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 3217 in oss-fuzz: llvm: Heap-buffer-overflow in llvm::object::WasmObjectFile::parseCustomSection
Updates: Cc: v...@apple.com Comment #7 on issue 3217 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm: Heap-buffer-overflow in llvm::object::WasmObjectFile::parseCustomSection https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3217#c7 (No comment was entered for this change.) -- 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 3227 in oss-fuzz: llvm: Heap-buffer-overflow in readInitExpr
Updates: Cc: v...@apple.com Comment #5 on issue 3227 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm: Heap-buffer-overflow in readInitExpr https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3227#c5 (No comment was entered for this change.) -- 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 3239 in oss-fuzz: llvm: ASSERT: getContainingDC(DC) == CurContext && "The next DeclContext should be lexically c
Updates: Cc: v...@apple.com Comment #6 on issue 3239 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm: ASSERT: getContainingDC(DC) == CurContext && "The next DeclContext should be lexically c https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3239#c6 (No comment was entered for this change.) -- 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 3216 in oss-fuzz: llvm: ASSERT: result <= UINT32_MAX
Updates: Cc: v...@apple.com Comment #6 on issue 3216 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm: ASSERT: result <= UINT32_MAX https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3216#c6 (No comment was entered for this change.) -- 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 3260 in oss-fuzz: llvm: ASSERT: (OtherT->isIntegerType() && ConstantT->isIntegerType()) && "comparison with non-
Updates: Cc: v...@apple.com Comment #4 on issue 3260 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm: ASSERT: (OtherT->isIntegerType() && ConstantT->isIntegerType()) && "comparison with non- https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3260#c4 (No comment was entered for this change.) -- 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 3236 in oss-fuzz: llvm: Abrt in llvm::report_bad_alloc_error
Updates: Cc: v...@apple.com Comment #6 on issue 3236 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm: Abrt in llvm::report_bad_alloc_error https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3236#c6 (No comment was entered for this change.) -- 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 3224 in oss-fuzz: llvm: Out-of-memory in llvm_llvm-dwarfdump-fuzzer
Updates: Cc: v...@apple.com Comment #5 on issue 3224 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm: Out-of-memory in llvm_llvm-dwarfdump-fuzzer https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3224#c5 (No comment was entered for this change.) -- 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 3286 in oss-fuzz: llvm: Stack-overflow in clang::Sema::GetNameFromUnqualifiedId
Updates: Cc: v...@apple.com Comment #2 on issue 3286 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm: Stack-overflow in clang::Sema::GetNameFromUnqualifiedId https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3286#c2 (No comment was entered for this change.) -- 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 3294 in oss-fuzz: llvm: Stack-overflow in AnalyzeImplicitConversions
Updates: Cc: v...@apple.com Comment #1 on issue 3294 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm: Stack-overflow in AnalyzeImplicitConversions https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3294#c1 (No comment was entered for this change.) -- 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 3296 in oss-fuzz: llvm: Stack-overflow in clang::StmtVisitorBase::Visit
Updates: Cc: v...@apple.com Comment #3 on issue 3296 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm: Stack-overflow in clang::StmtVisitorBasebool>::Visit https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3296#c3 (No comment was entered for this change.) -- 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 3264 in oss-fuzz: llvm: ASSERT: Ancestor->getEntity() == CurContext && "ancestor context mismatch"
Updates: Cc: v...@apple.com Comment #4 on issue 3264 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm: ASSERT: Ancestor->getEntity() == CurContext && "ancestor context mismatch" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3264#c4 (No comment was entered for this change.) -- 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 3283 in oss-fuzz: llvm: Abrt in llvm::llvm_unreachable_internal
Updates: Cc: v...@apple.com Comment #2 on issue 3283 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm: Abrt in llvm::llvm_unreachable_internal https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3283#c2 (No comment was entered for this change.) -- 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 3330 in oss-fuzz: llvm: Stack-overflow in clang::DeclContext::lookup
Updates: Cc: v...@apple.com Comment #3 on issue 3330 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm: Stack-overflow in clang::DeclContext::lookup https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3330#c3 (No comment was entered for this change.) -- 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 3337 in oss-fuzz: llvm: Heap-buffer-overflow in llvm::DataExtractor::getU32
Updates: Cc: v...@apple.com Comment #2 on issue 3337 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm: Heap-buffer-overflow in llvm::DataExtractor::getU32 https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3337#c2 (No comment was entered for this change.) -- 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 3243 in oss-fuzz: llvm: ASSERT: result <= INT32_MAX && result >= INT32_MIN
Updates: Cc: v...@apple.com Comment #3 on issue 3243 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm: ASSERT: result <= INT32_MAX && result >= INT32_MIN https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3243#c3 (No comment was entered for this change.) -- 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 3351 in oss-fuzz: llvm: Stack-overflow in clang::FunctionProtoType::getExtProtoInfo
Updates: Cc: v...@apple.com Comment #2 on issue 3351 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm: Stack-overflow in clang::FunctionProtoType::getExtProtoInfo https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3351#c2 (No comment was entered for this change.) -- 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 3238 in oss-fuzz: llvm: ASSERT: DD && "queried property of class with no definition"
Updates: Cc: v...@apple.com Comment #6 on issue 3238 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm: ASSERT: DD && "queried property of class with no definition" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3238#c6 (No comment was entered for this change.) -- 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 3302 in oss-fuzz: llvm: Stack-overflow in clang::Parser::ParseStatementOrDeclarationAfterAttributes
Updates: Cc: v...@apple.com Comment #3 on issue 3302 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm: Stack-overflow in clang::Parser::ParseStatementOrDeclarationAfterAttributes https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3302#c3 (No comment was entered for this change.) -- 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 3298 in oss-fuzz: llvm: Stack-overflow in IntExprEvaluator::VisitBinaryOperator
Updates: Cc: v...@apple.com Comment #3 on issue 3298 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm: Stack-overflow in IntExprEvaluator::VisitBinaryOperator https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3298#c3 (No comment was entered for this change.) -- 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 3299 in oss-fuzz: llvm: Stack-overflow in GetFullTypeForDeclarator
Updates: Cc: v...@apple.com Comment #3 on issue 3299 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm: Stack-overflow in GetFullTypeForDeclarator https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3299#c3 (No comment was entered for this change.) -- 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 3345 in oss-fuzz: llvm: Stack-overflow in llvm::SmallVectorBase::grow_pod
Updates: Cc: v...@apple.com Comment #2 on issue 3345 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm: Stack-overflow in llvm::SmallVectorBase::grow_pod https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3345#c2 (No comment was entered for this change.) -- 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 3353 in oss-fuzz: llvm: ASSERT: CodeDC && !CodeDC->isFileContext() && "statement expr not in code context"
Updates: Cc: v...@apple.com Comment #2 on issue 3353 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm: ASSERT: CodeDC && !CodeDC->isFileContext() && "statement expr not in code context" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3353#c2 (No comment was entered for this change.) -- 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 3358 in oss-fuzz: llvm: Stack-overflow in DiagnoseUninitializedReference
Updates: Cc: v...@apple.com Comment #2 on issue 3358 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm: Stack-overflow in DiagnoseUninitializedReference https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3358#c2 (No comment was entered for this change.) -- 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 3369 in oss-fuzz: llvm: Out-of-memory in llvm_clang-format-fuzzer
Updates: Cc: v...@apple.com Comment #2 on issue 3369 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm: Out-of-memory in llvm_clang-format-fuzzer https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3369#c2 (No comment was entered for this change.) -- 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 3368 in oss-fuzz: llvm: ASSERT: BT->isInteger()
Updates: Cc: v...@apple.com Comment #2 on issue 3368 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm: ASSERT: BT->isInteger() https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3368#c2 (No comment was entered for this change.) -- 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 3495 in oss-fuzz: llvm: Timeout in llvm_clang-format-fuzzer
Updates: Cc: v...@apple.com Comment #2 on issue 3495 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm: Timeout in llvm_clang-format-fuzzer https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3495#c2 (No comment was entered for this change.) -- 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 3506 in oss-fuzz: llvm: Stack-overflow in clang::RecursiveASTVisitor::dataTraverseNode
Updates: Cc: v...@apple.com Comment #2 on issue 3506 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm: Stack-overflow in clang::RecursiveASTVisitor::dataTraverseNode https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3506#c2 (No comment was entered for this change.) -- 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 3382 in oss-fuzz: llvm: Null-dereference READ in clang::format::AnnotatingParser::consumeToken
Updates: Cc: v...@apple.com Comment #2 on issue 3382 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm: Null-dereference READ in clang::format::AnnotatingParser::consumeToken https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3382#c2 (No comment was entered for this change.) -- 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 3434 in oss-fuzz: llvm: Heap-buffer-overflow in llvm::DataExtractor::getUnsigned
Updates: Cc: v...@apple.com Comment #2 on issue 3434 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm: Heap-buffer-overflow in llvm::DataExtractor::getUnsigned https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3434#c2 (No comment was entered for this change.) -- 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 3519 in oss-fuzz: llvm: Abrt in llvm::llvm_unreachable_internal
Updates: Cc: v...@apple.com Comment #2 on issue 3519 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm: Abrt in llvm::llvm_unreachable_internal https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3519#c2 (No comment was entered for this change.) -- 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 3450 in oss-fuzz: llvm: Stack-overflow in clang::format::TokenAnnotator::annotate
Updates: Cc: v...@apple.com Comment #3 on issue 3450 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm: Stack-overflow in clang::format::TokenAnnotator::annotate https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3450#c3 (No comment was entered for this change.) -- 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 3500 in oss-fuzz: llvm: Stack-overflow in llvm::APInt::tcShiftLeft
Updates: Cc: v...@apple.com Comment #1 on issue 3500 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm: Stack-overflow in llvm::APInt::tcShiftLeft https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3500#c1 (No comment was entered for this change.) -- 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 3390 in oss-fuzz: llvm: ASSERT: IndentPrefix.startswith("//")
Updates:
Cc: v...@apple.com
Comment #2 on issue 3390 by
monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm: ASSERT:
IndentPrefix.startswith("//")
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3390#c2
(No comment was entered for this change.)
--
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 3417 in oss-fuzz: llvm: Heap-buffer-overflow in llvm::DataExtractor::getU32
Updates: Cc: v...@apple.com Comment #2 on issue 3417 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm: Heap-buffer-overflow in llvm::DataExtractor::getU32 https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3417#c2 (No comment was entered for this change.) -- 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 3549 in oss-fuzz: ASSERT: Changes[i - 1].OriginalWhitespaceRange.getBegin() != C.OriginalWhitespaceRange.g
Updates: Cc: v...@apple.com Comment #2 on issue 3549 by monor...@clusterfuzz-external.iam.gserviceaccount.com: ASSERT: Changes[i - 1].OriginalWhitespaceRange.getBegin() != C.OriginalWhitespaceRange.g https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3549#c2 (No comment was entered for this change.) -- 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 3545 in oss-fuzz: llvm: Heap-buffer-overflow in llvm::DataExtractor::getCStr
Updates: Cc: v...@apple.com Comment #1 on issue 3545 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm: Heap-buffer-overflow in llvm::DataExtractor::getCStr https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3545#c1 (No comment was entered for this change.) -- 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 3370 in oss-fuzz: llvm: ASSERT: getClient() && "DiagnosticClient not set!"
Updates: Cc: v...@apple.com Comment #3 on issue 3370 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm: ASSERT: getClient() && "DiagnosticClient not set!" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3370#c3 (No comment was entered for this change.) -- 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 3374 in oss-fuzz: llvm: Stack-overflow in clang::format::AnnotatingParser::parseAngle
Updates: Cc: v...@apple.com Comment #2 on issue 3374 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm: Stack-overflow in clang::format::AnnotatingParser::parseAngle https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3374#c2 (No comment was entered for this change.) -- 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 3399 in oss-fuzz: llvm: Heap-buffer-overflow in llvm::raw_svector_ostream::write_impl
Updates: Cc: v...@apple.com Comment #2 on issue 3399 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm: Heap-buffer-overflow in llvm::raw_svector_ostream::write_impl https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3399#c2 (No comment was entered for this change.) -- 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 3386 in oss-fuzz: llvm: Stack-overflow in clang::DiagnosticIDs::isUnrecoverable
Updates: Cc: v...@apple.com Comment #2 on issue 3386 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm: Stack-overflow in clang::DiagnosticIDs::isUnrecoverable https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3386#c2 (No comment was entered for this change.) -- 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 3409 in oss-fuzz: llvm: Heap-buffer-overflow in llvm::DataExtractor::getCStr
Updates: Cc: v...@apple.com Comment #2 on issue 3409 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm: Heap-buffer-overflow in llvm::DataExtractor::getCStr https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3409#c2 (No comment was entered for this change.) -- 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 34849] clang-cl fails to dllexport specialization of class template member function when the class template is dllexport
https://bugs.llvm.org/show_bug.cgi?id=34849 Hans Wennborg changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #3 from Hans Wennborg --- Re-commited with fix in r315330. -- 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 3379 in oss-fuzz: llvm: Stack-overflow in clang::DeclSpec::Finish
Updates: Cc: v...@apple.com Comment #2 on issue 3379 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm: Stack-overflow in clang::DeclSpec::Finish https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3379#c2 (No comment was entered for this change.) -- 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 34904] New: Linking fails on C programs with xray instrumentation enabled
https://bugs.llvm.org/show_bug.cgi?id=34904
Bug ID: 34904
Summary: Linking fails on C programs with xray instrumentation
enabled
Product: clang
Version: trunk
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P
Component: -New Bugs
Assignee: unassignedclangb...@nondot.org
Reporter: jbulow-l...@jongel.net
CC: llvm-bugs@lists.llvm.org
According to documentation it should be possible to use xray instrumentation on
C program by specifying the flags -fxray-instrument.
Linking fails when compiling the following program:
8<- (minimal.c)
int main ()
{
return 0;
}
8<-
$ clang --version
clang version 6.0.0 (trunk 315272)
Target: x86_64-unknown-linux-gnu
Thread model: posix
InstalledDir: /home/jonasbu/local/bin
$ clang -fxray-instrument minimal.c
/home/jonasbu/local/lib/clang/6.0.0/lib/linux/libclang_rt.xray-x86_64.a(xray_inmemory_log.cc.o):
In function `getGlobalFd()':
/home/jonasbu/llvm-clang/llvm/projects/compiler-rt/lib/xray/xray_inmemory_log.cc:123:
undefined reference to `__cxa_guard_acquire'
/home/jonasbu/llvm-clang/llvm/projects/compiler-rt/lib/xray/xray_inmemory_log.cc:123:
undefined reference to `__cxa_guard_release'
/home/jonasbu/local/lib/clang/6.0.0/lib/linux/libclang_rt.xray-x86_64.a(xray_inmemory_log.cc.o):
In function `__xray_InMemoryRawLog<__xray_InMemoryEmulateTSC(int32_t,
XRayEntryType):: >':
/home/jonasbu/llvm-clang/llvm/projects/compiler-rt/lib/xray/xray_inmemory_log.cc:136:
undefined reference to `__cxa_thread_atexit'
/home/jonasbu/local/lib/clang/6.0.0/lib/linux/libclang_rt.xray-x86_64.a(xray_inmemory_log.cc.o):
In function `__xray_OpenLogFile':
/home/jonasbu/llvm-clang/llvm/projects/compiler-rt/lib/xray/xray_inmemory_log.cc:85:
undefined reference to `__cxa_guard_acquire'
/home/jonasbu/llvm-clang/llvm/projects/compiler-rt/lib/xray/xray_inmemory_log.cc:85:
undefined reference to `__cxa_guard_release'
/home/jonasbu/llvm-clang/llvm/projects/compiler-rt/lib/xray/xray_inmemory_log.cc:87:
undefined reference to `__cxa_guard_acquire'
/home/jonasbu/llvm-clang/llvm/projects/compiler-rt/lib/xray/xray_inmemory_log.cc:87:
undefined reference to `__cxa_guard_release'
...
...
...
As expected, the same program compiles and links fine as a C++ program:
$ clang++ -xc++ -fxray-instrument minimal.c
$
--
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 34905] New: [fuzz] tautological comparison warning asserts on comparison between _Complex and enum
https://bugs.llvm.org/show_bug.cgi?id=34905
Bug ID: 34905
Summary: [fuzz] tautological comparison warning asserts on
comparison between _Complex and enum
Product: clang
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: -New Bugs
Assignee: unassignedclangb...@nondot.org
Reporter: richard-l...@metafoo.co.uk
CC: llvm-bugs@lists.llvm.org
Found by oss-fuzz: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3368
Here's a cleaned-up version of the testcase:
enum { t };
bool b = 3.i < t;
There are two bugs here. First, we should never have built a relational
comparison expression between a _Complex double and an enumerator at all.
But the assert is also bogus; it fires for this (valid) code:
enum { t };
bool b = 3.i == t;
--
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 3368 in oss-fuzz: llvm: ASSERT: BT->isInteger()
Comment #3 on issue 3368 by richardsm...@google.com: llvm: ASSERT: BT->isInteger() https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3368#c3 This can manifest as a rejects-valid. Cleaned-up testcase filed as https://bugs.llvm.org/show_bug.cgi?id=34905 -- 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 34906] New: vector::insert(pos, iter, iter) incorrectly requires value-assignment for forward_iterators.
https://bugs.llvm.org/show_bug.cgi?id=34906
Bug ID: 34906
Summary: vector::insert(pos, iter, iter) incorrectly requires
value-assignment for forward_iterators.
Product: libc++
Version: unspecified
Hardware: PC
OS: Windows NT
Status: NEW
Severity: enhancement
Priority: P
Component: All Bugs
Assignee: unassignedclangb...@nondot.org
Reporter: e...@efcs.ca
CC: llvm-bugs@lists.llvm.org, mclow.li...@gmail.com
According to the spec, this overload of `insert` doesn't require that the
elements in the vector be assignable from the iterator value_type. However
libc++ currently requires this.
Example:
// clang++ -stdlib=libc++ -std=c++11 test.cpp
#include
template
struct EmplaceConstructibleAndMoveable {
explicit EmplaceConstructibleAndMoveable(T) {}
EmplaceConstructibleAndMoveable(EmplaceConstructibleAndMoveable&&) =
default;
EmplaceConstructibleAndMoveable&
operator=(EmplaceConstructibleAndMoveable&&) = default;
};
int main() {
using T = EmplaceConstructibleAndMoveable;
std::vector v;
int Inits[] = {1, 2, 3};
v.insert(v.end(), std::begin(Inits), std::end(Inits));
}
--
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 34780] Merge r314513 into the 5.0 branch
https://bugs.llvm.org/show_bug.cgi?id=34780 Tom Stellard changed: What|Removed |Added Status|NEW |RESOLVED Fixed By Commit(s)|r314513 |r314513 r315353 Resolution|--- |FIXED --- Comment #2 from Tom Stellard --- Merged: r315353 -- 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 34492] [meta] 5.0.1 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=34492 Bug 34492 depends on bug 34780, which changed state. Bug 34780 Summary: Merge r314513 into the 5.0 branch https://bugs.llvm.org/show_bug.cgi?id=34780 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 34907] New: IA64 ABI: RTTI name for class in anonymous namespace lacks '*', breaks dynamic_cast and type_info::operator== on GNU/Linux
https://bugs.llvm.org/show_bug.cgi?id=34907
Bug ID: 34907
Summary: IA64 ABI: RTTI name for class in anonymous namespace
lacks '*', breaks dynamic_cast and
type_info::operator== on GNU/Linux
Product: clang
Version: 5.0
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: LLVM Codegen
Assignee: unassignedclangb...@nondot.org
Reporter: ryan.prich...@gmail.com
CC: llvm-bugs@lists.llvm.org
libstdc++ apparently has a convention where the typeinfo name for a class
declared in an anonymous namespace begins with an asterisk ('*'), which tells
std::type_info::operator== to consider two type_info objects unequal even if
their names are equal. Clang is not outputting this asterisk on GNU/Linux.
Because it's omitted, if I declare two classes with the same name, in two
different anonymous namespaces, the two class types are considered equal
according to std::type_info::operator==, and I can cast from one type to
another with dynamic_cast. G++ outputs the asterisk, so the types are treated
as unequal.
The asterisk is stripped off in GNU's std::type_info::name(), so it's not user
visible.
AFAICT, libc++ doesn't have this convention, but for ARM64 iOS, there is a
different convention of setting the highest(?) bit of the type_info's
__type_name pointer to indicate that string comparison *should* be performed.
(Look for the _LIBCPP_HAS_NONUNIQUE_TYPEINFO and _LIBCPP_NONUNIQUE_RTTI_BIT
flags in libc++. I wonder if ARM64 iOS also sets _LIBCXX_DYNAMIC_FALLBACK for
libc++abi?)
I'm wondering whether there's a compatibility concern here w.r.t. previous
versions of Clang. My first guess is that compatibility with
G++/libstdc++/libsupc++ (and correctness) is sufficient to motivate changing
Clang. I guess Clang would have to generate different code for
-stdlib=libstdc++ and -stdlib=libc++?
Test case:
test.h
#include
#include
#include
struct Base {
virtual ~Base() {}
};
namespace def {
Base *alloc();
const std::type_info &type();
}
test-def.cc
#include "test.h"
namespace {
struct A : Base {};
}
namespace def {
Base *alloc() {
return new A;
}
const std::type_info &type() {
return typeid(A);
}
}
test-run.cc
#include "test.h"
namespace {
struct A : Base {
void func() {
printf("ERROR: run func called, field=%d\n", field);
}
private:
int field = 42;
};
}
__attribute__((noinline))
static A *do_cast(Base *b) {
return dynamic_cast(b);
}
__attribute__((noinline))
static bool types_eq(const std::type_info &x, const std::type_info &y) {
return x == y;
}
int main() {
printf("def A == run A: %d\n", types_eq(def::type(),
typeid(A)));
printf("&def A == &run A: %d\n", &def::type() == &typeid(A));
printf("name of def A:%s\n", def::type().name());
printf("name of run A:%s\n", typeid(A).name());
printf("def A name == run A name: %d\n", def::type().name() ==
typeid(A).name());
Base *b = def::alloc();
auto *p = do_cast(b);
if (p == nullptr) {
printf("SUCCESS: dynamic_cast returned nullptr\n");
} else {
p->func();
}
#ifdef __GXX_TYPEINFO_EQUALITY_INLINE
printf("__GXX_TYPEINFO_EQUALITY_INLINE = %d\n",
__GXX_TYPEINFO_EQUALITY_INLINE);
#endif
#ifdef __GXX_MERGED_TYPEINFO_NAMES
printf("__GXX_MERGED_TYPEINFO_NAMES= %d\n",
__GXX_MERGED_TYPEINFO_NAMES);
#endif
}
$ cat /etc/issue
Ubuntu 14.04.5 LTS \n \l
$ uname -m
x86_64
$ g++ test-def.cc test-run.cc -std=c++11 && ./a.out
def A == run A: 0
&def A == &run A: 0
name of def A:N12_GLOBAL__N_11AE
name of run A:N12_GLOBAL__N_11AE
def A name == run A name: 0
SUCCESS: dynamic_cast returned nullptr
__GXX_TYPEINFO_EQUALITY_INLINE = 1
__GXX_MERGED_TYPEINFO_NAMES= 0
$ ~/clang+llvm-5.0.0-linux-x86_64-ubuntu14.04/bin/clang++ test-def.cc
test-run.cc -std=c++11 && ./a.out
def A == run A: 1
&def A == &run A: 0
name of def A:N12_GLOBAL__N_11AE
name of run A:N12_GLOBAL__N_11AE
def A name == run A name: 0
ERROR: run func called, field=0
__GXX_TYPEINFO_EQUALITY_INLINE = 1
__GXX_MERGED_TYPEINFO_NAMES= 0
$ g++ test-def.cc -S && cat test-def.s
...
_ZTSN12_GLOBAL__N_11AE:
.string "*N12_GLOBAL__N_11AE"
...
$ ~/clang+llvm-5.0.0-linux-x86_64-ubuntu14.04/bin/clang++ test-def.cc -S && cat
test-def.s
...
_ZTSN12_GLOBAL__N_11AE:
.asciz "N12_GLOBAL__N_11AE"
...
--
You are receiving thi
[llvm-bugs] [Bug 34908] New: Assertion tripped in GVN: "Replacing constants with constants is inval"
https://bugs.llvm.org/show_bug.cgi?id=34908
Bug ID: 34908
Summary: Assertion tripped in GVN: "Replacing constants with
constants is inval"
Product: libraries
Version: trunk
Hardware: PC
OS: All
Status: NEW
Severity: enhancement
Priority: P
Component: Scalar Optimizations
Assignee: unassignedb...@nondot.org
Reporter: a...@crichton.co
CC: llvm-bugs@lists.llvm.org
When compiling the following IR
define i1 @foo() {
call void @llvm.assume(i1 undef)
ret i1 undef
}
declare void @llvm.assume(i1)
The GVN pass will crash with an assertion when assertions are enabled
$ opt -S foo.ll -gvn
opt: /home/alex/code/rust2/src/llvm/lib/Transforms/Scalar/GVN.cpp:1509: bool
llvm::GVN::replaceOperandsWithConsts(llvm::Instruction*) const: Assertion
`!isa(Operand) && "Replacing constants with constants is invalid"'
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] [Bug 34909] New: ThinLTO on windows produces invalid code.
https://bugs.llvm.org/show_bug.cgi?id=34909 Bug ID: 34909 Summary: ThinLTO on windows produces invalid code. Product: new-bugs Version: unspecified Hardware: PC OS: Windows NT Status: NEW Severity: enhancement Priority: P Component: new bugs Assignee: unassignedb...@nondot.org Reporter: ztur...@google.com CC: llvm-bugs@lists.llvm.org, l...@inglorion.net, pe...@pcc.me.uk 1. Build an x86 Release version of clang using the standard MSVC compiler and linker. > (From an x86 MSVC build environment) > cmake -G Ninja -DCMAKE_BUILD_TYPE=Release -DLLVM_TARGETS_TO_BUILD=X86 > -DLLVM_ENABLE_PROJECTS=clang > ninja clang 2. Build an x64 Release version of lld using the standard MSVC compiler and linker. > (From an x64 MSVC build environment) > cmake -G Ninja -DCMAKE_BUILD_TYPE=Release -DLLVM_TARGETS_TO_BUILD=X86 > -DLLVM_ENABLE_PROJECTS=lld > ninja lld Because clang-cl uses the default target triple based on its bitness, in order to build and link an x86 binary with clang-cl + lld, the compiler has to be built x86, and the linker has to be built x64 (or it runs out of memory). This is really lame and the compiler should detect the MSVC environment that is configured, but that isn't the way it works today. So, continuing... 3. Configure a third build directory that uses the compiler from step 1 and the linker from step 2, and that uses -DLLVM_ENABLE_LTO=Thin. > (From an x86 MSVC build environment) > cmake -G Ninja -DLLVM_ENABLE_LTO=Thin > -DCMAKE_C_COMPILER= > -DCMAKE_CXX_COMPILER= > -DCMAKE_LINKER= -DCMAKE_BUILD_TYPE=Release > -DLLVM_TARGETS_TO_BUILD=X86 -DLLVM_ENABLE_PROJECTS="clang;lld" > ..\..\..\..\llvm-mono\llvm 4. Build your LTO'ed tblgen > ninja llvm-tblgen 5. Run tblgen. > bin\llvm-tblgen.exe -gen-attrs -I D:/src/llvm-mono/llvm/include/llvm/IR -I > D:/src/llvm-mono/llvm/include > D:/src/llvm-mono/llvm/include/llvm/IR/Attributes.td -o > include/llvm/IR/Attributes.gen.tmp -d include/llvm/IR/Attributes.gen.d 6. Print the value of ERRORLEVEL > echo %ERRORLEVEL% -1073741819 This corresponds to 0xC005 which is access violation. -- 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 3137 in oss-fuzz: llvm: ASSERT: CurPtr[-1] == '<' && CurPtr[0] == '#' && "Not a placeholder!"
Comment #8 on issue 3137 by arpha...@gmail.com: llvm: ASSERT: CurPtr[-1] == '<' && CurPtr[0] == '#' && "Not a placeholder!" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3137#c8 Fixed in r315398. -- 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 34306] Odd PC rel for thread local
https://bugs.llvm.org/show_bug.cgi?id=34306 Peter Collingbourne changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #7 from Peter Collingbourne --- Fix landed in r315400. -- 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 34910] New: debugging source and symbols are lost when linking
https://bugs.llvm.org/show_bug.cgi?id=34910
Bug ID: 34910
Summary: debugging source and symbols are lost when linking
Product: lld
Version: unspecified
Hardware: PC
OS: Windows NT
Status: NEW
Severity: enhancement
Priority: P
Component: COFF
Assignee: unassignedb...@nondot.org
Reporter: superjo...@gmail.com
CC: llvm-bugs@lists.llvm.org
This is with LLVM/Clang/LLD 5.0.0.
hello.ll
; ModuleID = 'hello'
source_filename = "hello"
target datalayout = "e-m:w-i64:64-f80:128-n8:16:32:64-S128"
target triple = "x86_64-pc-windows-msvc"
%"[]u8" = type { i8*, i64 }
@link_libc = internal unnamed_addr constant i1 false, align 1
@os = internal unnamed_addr constant i6 15, align 1
@is_windows = internal unnamed_addr constant i1 true, align 1
@want_start_symbol = internal unnamed_addr constant i1 false, align 1
@want_WinMainCRTStartup = internal unnamed_addr constant i1 true, align 1
@user_main_fn = internal unnamed_addr global i16 ()* null, align 8
@0 = internal unnamed_addr constant i8* getelementptr inbounds ([24 x i8], [24
x i8]* @1, i64 0, i64 0), align 8
@1 = internal unnamed_addr constant [24 x i8] c"reached unreachable code",
align 1
@2 = internal unnamed_addr constant { i8*, i64 } { i8* getelementptr inbounds
([24 x i8], [24 x i8]* @1, i64 0, i64 0), i64 24 }, align 8
@3 = internal unnamed_addr constant i16 ()** @user_main_fn, align 8
; Function Attrs: nobuiltin noreturn nounwind
define internal fastcc void @panic(%"[]u8"* byval nonnull readonly)
unnamed_addr #0 !dbg !62 {
Entry:
call void @llvm.dbg.declare(metadata %"[]u8"* %0, metadata !76, metadata
!77), !dbg !78
br label %WhileCond, !dbg !79
WhileCond:; preds = %WhileCond, %Entry
br label %WhileCond, !dbg !79
}
; Function Attrs: naked nobuiltin noreturn nounwind
define internal void @_start.0() unnamed_addr #1 !dbg !82 {
Entry:
call fastcc void @panic(%"[]u8"* bitcast ({ i8*, i64 }* @2 to %"[]u8"*)),
!dbg !86
unreachable, !dbg !86
}
; Function Attrs: nobuiltin noinline noreturn nounwind alignstack(16)
define void @WinMainCRTStartup() #2 !dbg !89 {
Entry:
%0 = alloca i16, align 2
store i16 ()* @main.0.1, i16 ()** @user_main_fn, align 8, !dbg !90
%1 = call fastcc i16 @main.0.1(), !dbg !92
store i16 %1, i16* %0, align 2, !dbg !92
%2 = load i16, i16* %0, align 2, !dbg !93
%3 = icmp ne i16 %2, 0, !dbg !93
br i1 %3, label %UnwrapErrError, label %UnwrapErrOk, !dbg !93
UnwrapErrError: ; preds = %Entry
call void @ExitProcess(i32 1), !dbg !94
unreachable, !dbg !94
UnwrapErrOk: ; preds = %Entry
%4 = load i16, i16* %0, align 2, !dbg !93
br label %UnwrapErrEnd, !dbg !93
UnwrapErrEnd: ; preds = %UnwrapErrOk
call void @ExitProcess(i32 0), !dbg !95
unreachable, !dbg !95
}
; Function Attrs: nobuiltin nounwind
define internal i32 @main.0(i32, i8** nonnull, i8** nonnull) unnamed_addr #3
!dbg !96 {
Entry:
%c_argc = alloca i32, align 4
%c_argv = alloca i8**, align 8
%c_envp = alloca i8**, align 8
store i32 %0, i32* %c_argc, align 4
call void @llvm.dbg.declare(metadata i32* %c_argc, metadata !103, metadata
!77), !dbg !108
store i8** %1, i8*** %c_argv, align 8
call void @llvm.dbg.declare(metadata i8*** %c_argv, metadata !104, metadata
!77), !dbg !109
store i8** %2, i8*** %c_envp, align 8
call void @llvm.dbg.declare(metadata i8*** %c_envp, metadata !106, metadata
!77), !dbg !110
call fastcc void @panic(%"[]u8"* bitcast ({ i8*, i64 }* @2 to %"[]u8"*)),
!dbg !111
unreachable, !dbg !111
}
; Function Attrs: nobuiltin nounwind
define internal fastcc i16 @main.0.1() unnamed_addr #3 !dbg !115 {
Entry:
call void @llvm.debugtrap(), !dbg !119
ret i16 0, !dbg !121
}
; Function Attrs: nobuiltin noreturn nounwind
declare void @ExitProcess(i32) #0
; Function Attrs: nounwind readnone speculatable
declare void @llvm.dbg.declare(metadata, metadata, metadata) #4
; Function Attrs: nounwind
declare void @llvm.debugtrap() #5
; Function Attrs: nounwind
declare void @llvm.stackprotector(i8*, i8**) #5
attributes #0 = { nobuiltin noreturn nounwind "no-frame-pointer-elim"="true"
"no-frame-pointer-elim-non-leaf" }
attributes #1 = { naked nobuiltin noreturn nounwind
"no-frame-pointer-elim"="true" "no-frame-pointer-elim-non-leaf" }
attributes #2 = { nobuiltin noinline noreturn nounwind alignstack=16
"no-frame-pointer-elim"="true" "no-frame-pointer-elim-non-leaf" }
attributes #3 = { nobuiltin nounwind "no-frame-pointer-elim"="true"
"no-frame-pointer-elim-non-leaf" }
attributes #4 = { nounwind readnone speculatable }
attributes #5 = { nounwind }
!llvm.module.flags = !{!0}
!llvm.dbg.cu = !{!1}
!0 = !{i32 2, !"CodeView", i32 1}
!1 = distinct !DICompileUnit(language: DW_LANG_C99, file: !2, producer: "zig
0.0.0.15635747", isOptimized: fals
[llvm-bugs] [Bug 34911] New: Redundant comparisons are not eliminated
https://bugs.llvm.org/show_bug.cgi?id=34911
Bug ID: 34911
Summary: Redundant comparisons are not eliminated
Product: libraries
Version: trunk
Hardware: PC
OS: All
Status: NEW
Severity: enhancement
Priority: P
Component: Scalar Optimizations
Assignee: unassignedb...@nondot.org
Reporter: jmuizel...@mozilla.com
CC: llvm-bugs@lists.llvm.org
#include
int f(int x) {
if (x < 4)
exit(1);
if (x < 8)
exit(1);
if (x < 12)
exit(1);
if (x < 16)
exit(1);
return x + 5;
}
compiles to:
f(int): # @f(int)
pushq %rax
cmpl$3, %edi
jle .LBB0_5
cmpl$7, %edi
jle .LBB0_5
cmpl$11, %edi
jle .LBB0_5
cmpl$15, %edi
jle .LBB0_5
addl$5, %edi
movl%edi, %eax
popq%rcx
retq
.LBB0_5:
movl$1, %edi
callq exit
compared to gcc's
f(int):
cmpl$15, %edi
jle .L7
leal5(%rdi), %eax
ret
.L7:
subq$8, %rsp
movl$1, %edi
callexit
--
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 34912] New: Brace-init of const type to non-const reference produces error message with missing/incorrect types
https://bugs.llvm.org/show_bug.cgi?id=34912
Bug ID: 34912
Summary: Brace-init of const type to non-const reference
produces error message with missing/incorrect types
Product: clang
Version: 4.0
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: C++14
Assignee: unassignedclangb...@nondot.org
Reporter: anthonym.lee...@gmail.com
CC: llvm-bugs@lists.llvm.org
int main() {
const int i{0};
int& ref{i};
return 0;
}
The above code produces the error message:
error: binding value of type 'void' to reference to type 'int' drops <>
qualifiers
int& ref{f.value};
^ ~
While the following produces the correct error message:
int main() {
const int i{0};
int& ref = i;
return 0;
}
error: binding value of type 'const int' to reference to type 'int' drops
'const' qualifier
int& ref = i;
Brace-initialization seems to cause an error in the error reporting, unable to
access the correct types for the message to display. I'm not familiar with
clang internals so I'm not much help here.
--
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 34913] New: Clang crashes while building swift code.
https://bugs.llvm.org/show_bug.cgi?id=34913 Bug ID: 34913 Summary: Clang crashes while building swift code. Product: clang Version: 5.0 Hardware: PC OS: Linux Status: NEW Severity: normal Priority: P Component: C++ Assignee: unassignedclangb...@nondot.org Reporter: sow...@gmail.com CC: dgre...@apple.com, llvm-bugs@lists.llvm.org While building swift code Clang crashes. The code it's trying to build is a casting function implemented in C++. The crash produced a C++ file and a shell script in /tmp which is attached, along with actual crash information which got printed in console. Attached file contains 3 sections (easy to search with word "Section "). Section A: The information which got printed in console. Section B: The C++ file which got created in /tmp. Section C: The shell script which got created in /tmp. -- 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
