[llvm-bugs] [Bug 38544] [enableSubRegLiveness] Crashes on SPEC / SystemZ
https://bugs.llvm.org/show_bug.cgi?id=38544 Jonas Paulsson changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED -- 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 9833 in oss-fuzz: llvm/clang-fuzzer: Stack-overflow in clang::DeclContext::lookup
Comment #2 on issue 9833 by ClusterFuzz-External: llvm/clang-fuzzer: Stack-overflow in clang::DeclContext::lookup https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=9833#c2 ClusterFuzz has detected this issue as fixed in range 201808190139:201808200140. Detailed report: https://oss-fuzz.com/testcase?key=5205394178703360 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: 0x7fffad2eed18 Crash State: clang::DeclContext::lookup clang::DeclContext::using_directives UnqualUsingDirectiveSet::addUsingDirectives Sanitizer: address (ASAN) Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201808190139:201808200140 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5205394178703360 See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for more information. 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 http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 9833 in oss-fuzz: llvm/clang-fuzzer: Stack-overflow in clang::DeclContext::lookup
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #3 on issue 9833 by ClusterFuzz-External: llvm/clang-fuzzer: Stack-overflow in clang::DeclContext::lookup https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=9833#c3 ClusterFuzz testcase 5205394178703360 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 http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 38633] New: [Formatter/Cpp] Comments before conditions in if else statment are misalligned
https://bugs.llvm.org/show_bug.cgi?id=38633
Bug ID: 38633
Summary: [Formatter/Cpp] Comments before conditions in if else
statment are misalligned
Product: clang
Version: trunk
Hardware: PC
OS: All
Status: NEW
Severity: enhancement
Priority: P
Component: Formatter
Assignee: unassignedclangb...@nondot.org
Reporter: joles...@google.com
CC: djas...@google.com, kli...@google.com,
llvm-bugs@lists.llvm.org
I'm not sure whether current behavior is intended, but I think it could be
improved considering how common this pattern is:
Could be:
// description of the condition
if (true) {
x = 42;
// description of another condition
} else if (true) {
x = 42;
// description of else
} else {
x = 42;
}
Current formatting:
// description of the condition
if (true) {
x = 42;
// description of another condition
} else if (true) {
x = 42;
// description of else
} else {
x = 42;
}
One drawback, I can think of, of this change would be an incorrect indentation
in the following situation:
Base version:
if (...) {
x = 42;
// Assign 43 to x
x = 43;
} else if (...) {
}
Developer changed to:
if (...) {
x = 42;
// Assign 43 to x
// x = 43; - temporarily comment this line
} else if (...) {
}
After running clang-format on above code:
if (...) {
x = 42;
// Assign 43 to x
// x = 43; - temporarily comment this line
} else if (...) {
}
This would go back to the correct formatting after uncommenting the line, so I
don't think this should be an issue.
--
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 38634] New: Merge r340158 to 7.0 branch: Add SVE System registers
https://bugs.llvm.org/show_bug.cgi?id=38634 Bug ID: 38634 Summary: Merge r340158 to 7.0 branch: Add SVE System registers Product: new-bugs Version: 7.0 Hardware: PC OS: All Status: NEW Severity: enhancement Priority: P Component: new bugs Assignee: unassignedb...@nondot.org Reporter: sander.desma...@arm.com CC: llvm-bugs@lists.llvm.org This patch was missing from the assembler/disassembler support for SVE. It would be great if this could still be cherry-picked onto the llvm 7 release branch. -- 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 38482] AVX512 error in backend: unknown codeview register
https://bugs.llvm.org/show_bug.cgi?id=38482 Alexander Neumann changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #25 from Alexander Neumann --- good work! Code compiles without crash. 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 http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 37327] Stmt::IgnoreImplicit() should ignore non-trailing ImplicitCastExpr
https://bugs.llvm.org/show_bug.cgi?id=37327 Stephen Kelly changed: 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 38635] New: llc doesn't generate correct addresses in .debug_addr table for 64bit addresses
https://bugs.llvm.org/show_bug.cgi?id=38635
Bug ID: 38635
Summary: llc doesn't generate correct addresses in .debug_addr
table for 64bit addresses
Product: new-bugs
Version: trunk
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P
Component: new bugs
Assignee: unassignedb...@nondot.org
Reporter: vlesc...@gmail.com
CC: llvm-bugs@lists.llvm.org
Created attachment 20742
--> https://bugs.llvm.org/attachment.cgi?id=20742&action=edit
source ll and produced asm
When trying to generate a 64bit object file from simple code:
void foo() {}
void bar() {}
An ll is attached. llc produces correct asm (looks good to me):
.section .debug_addr,"",@progbits
.quad .Lfunc_begin0
.quad .Lfunc_begin1
However if we try to generate an object file:
./bin/llc -split-dwarf-file=test.dwo -dwarf-version=4 test.ll -filetype=obj
-mtriple=x86_64-unknown-linux-gnu -o test.o
And check it with llvm-dwarfdump, we see correct addresses for functions in
debug_info section:
0x0019: DW_TAG_subprogram
DW_AT_low_pc( indexed () address =
0x)
0x0024: DW_TAG_subprogram
DW_AT_low_pc( indexed (0001) address =
0x0010)
But zero addresses in .debug_addr section:
.debug_addr contents:
Addr Section: length = 0x, version = 0x0004, addr_size = 0x08, seg_size
= 0x00
Addrs: [
0x
0x
]
Does anyone have an idea where to start looking at?
PS: It looks like llvm-dwarfdump does read 64bit contents of .debug_addr
section: see test/tools/llvm-dwarfdump/X86/debug_addr_64bit_address.s
PPS: there is no such problem with 32bit addresses.
--
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 38636] New: [Formatter/ObjC] Break after return statement worsen readability
https://bugs.llvm.org/show_bug.cgi?id=38636
Bug ID: 38636
Summary: [Formatter/ObjC] Break after return statement worsen
readability
Product: clang
Version: trunk
Hardware: PC
OS: All
Status: NEW
Severity: enhancement
Priority: P
Component: Formatter
Assignee: unassignedclangb...@nondot.org
Reporter: joles...@google.com
CC: djas...@google.com, kli...@google.com,
llvm-bugs@lists.llvm.org
Current formatting (works fine when there is many elements):
return @{
: a,
: a
};
Current formatting (works suboptimal when there is one element; lack of spaces
is a different bug: https://bugs.llvm.org/show_bug.cgi?id=36919):
return
@{ :
a};
Should be (more readable and consistent with case when there is many elements):
return @{
: a
};
The same problem with array literals:
return
@[ aa
];
instead of:
return @[
aa
];
Maybe it makes sense to increase the penalty for breaking after "return" as I
believe it may touch other constructions as well.
--
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 38637] New: Merge r340171 into LLVM 7.0
https://bugs.llvm.org/show_bug.cgi?id=38637 Bug ID: 38637 Summary: Merge r340171 into LLVM 7.0 Product: new-bugs Version: 7.0 Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: new bugs Assignee: unassignedb...@nondot.org Reporter: samuel.pitoi...@gmail.com CC: llvm-bugs@lists.llvm.org Please merge r340171 into 7.0: https://llvm.org/viewvc/llvm-project?view=revision&revision=340171 To avoid compilation failures with some buildbot slaves, you will need to backport r340172 as well (or squash them). 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 http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 36923] R_X86_64_32S: error while loading shared libraries: unexpected reloc type 0x0b
https://bugs.llvm.org/show_bug.cgi?id=36923 George Rimar changed: What|Removed |Added Status|NEW |RESOLVED CC||gri...@accesssoftek.com Resolution|--- |WORKSFORME --- Comment #1 from George Rimar --- Unable to reproduce using fresh clang and lld: ~/LLVM/build/bin/clang++ -v clang version 8.0.0 (trunk 339680) ~/LLVM/build/bin/ld.lld -v LLD 8.0.0 (trunk 340163) (compatible with GNU linkers) readelf -WDr a.out 'RELA' relocation section at offset 0x4d0 contains 216 bytes: Offset Info Type Symbol's Value Symbol's Name + Addend 2008 0008 R_X86_64_RELATIVE 2008 3000 0008 R_X86_64_RELATIVE 10c0 3008 0008 R_X86_64_RELATIVE 1100 1112 0008 R_X86_64_RELATIVE 68c 1161 0008 R_X86_64_RELATIVE 68f 3200 00020006 R_X86_64_GLOB_DAT __gmon_start__ + 0 3208 00030006 R_X86_64_GLOB_DAT _ITM_deregisterTMCloneTable + 0 3210 00040006 R_X86_64_GLOB_DAT _ITM_registerTMCloneTable + 0 3218 00050006 R_X86_64_GLOB_DAT __cxa_finalize@GLIBC_2.2.5 + 0 'PLT' relocation section at offset 0x5a8 contains 192 bytes: Offset Info Type Symbol's Value Symbol's Name + Addend 2028 00010007 R_X86_64_JUMP_SLOT __libc_start_main@GLIBC_2.2.5 + 0 2030 00020007 R_X86_64_JUMP_SLOT __gmon_start__ + 0 2038 00050007 R_X86_64_JUMP_SLOT __cxa_finalize@GLIBC_2.2.5 + 0 2040 00060007 R_X86_64_JUMP_SLOT opendir@GLIBC_2.2.5 + 0 2048 00080007 R_X86_64_JUMP_SLOT puts@GLIBC_2.2.5 + 0 2050 00090007 R_X86_64_JUMP_SLOT readdir@GLIBC_2.2.5 + 0 2058 000a0007 R_X86_64_JUMP_SLOT 12a0 closedir@GLIBC_2.2.5 + 0 2060 00070007 R_X86_64_JUMP_SLOT perror@GLIBC_2.2.5 + 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] [Bug 38638] New: Wrong constraint for std::optional
https://bugs.llvm.org/show_bug.cgi?id=38638
Bug ID: 38638
Summary: Wrong constraint for std::optional::operator=(U&&)
Product: libc++
Version: 6.0
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P
Component: All Bugs
Assignee: unassignedclangb...@nondot.org
Reporter: zi...@kayari.org
CC: llvm-bugs@lists.llvm.org, mclow.li...@gmail.com
The following should compile:
#include
constexpr int foo(int i) {
std::optional o;
o = i;
return *o;
}
Wandbox tells me:
prog.cc:2:15: error: constexpr function never produces a constant expression
[-Winvalid-constexpr]
constexpr int foo(int i) {
^
prog.cc:4:5: note: non-constexpr function 'operator=' cannot be
used in a constant expression
o = i;
^
/opt/wandbox/clang-6.0.0/include/c++/v1/optional:773:5: note: declared here
operator=(_Up&& __v)
^
https://wandbox.org/permlink/OrXOqTuQHDSddHod
The note shows that operator=(U&&) is being used, but that should not
participate in overload resolution unless conjunction_v,
is_same>> is false.
In my code is_scalar is true, and is_same> is true.
--
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 8605 in oss-fuzz: llvm/llvm-isel-fuzzer--x86_64-O2: ASSERT: (Known.Zero & Known.One) == 0 && "Bits known to be one AND zero?"
Updates: Labels: Deadline-Approaching Comment #4 on issue 8605 by sheriff...@chromium.org: llvm/llvm-isel-fuzzer--x86_64-O2: ASSERT: (Known.Zero & Known.One) == 0 && "Bits known to be one AND zero?" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=8605#c4 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 http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 8599 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-loop_unroll: Out-of-memory in llvm_llvm-opt-fuzzer--x86_64-loop_unroll
Updates: Labels: Deadline-Approaching Comment #4 on issue 8599 by sheriff...@chromium.org: llvm/llvm-opt-fuzzer--x86_64-loop_unroll: Out-of-memory in llvm_llvm-opt-fuzzer--x86_64-loop_unroll https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=8599#c4 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 http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 38639] New: lowerVectorShuffleByMerging128BitLanes - Detected cycle in SelectionDAG
https://bugs.llvm.org/show_bug.cgi?id=38639
Bug ID: 38639
Summary: lowerVectorShuffleByMerging128BitLanes - Detected
cycle in SelectionDAG
Product: libraries
Version: trunk
Hardware: PC
OS: Windows NT
Status: NEW
Severity: enhancement
Priority: P
Component: Backend: X86
Assignee: unassignedb...@nondot.org
Reporter: llvm-...@redking.me.uk
CC: craig.top...@gmail.com,
douglas_y...@playstation.sony.com,
greg.bedw...@sony.com, llvm-bugs@lists.llvm.org
D41794 is causing this fuzz test regression:
define <8 x double> @test(<4 x double> %a, <4 x double> %b) {
%1 = shufflevector <4 x double> %a, <4 x double> , <8 x
i32>
ret <8 x double> %1
}
llc -mcpu=btver2
Detected cycle in SelectionDAG
Offending node:
t27: v4f64 = vector_shuffle<0,5,2,7> t27, t26
t27: v4f64 = vector_shuffle<0,5,2,7> t27, t26
t27: v4f64 = vector_shuffle<0,5,2,7> t27, t26
t27: v4f64 = vector_shuffle<0,5,2,7> t27, t26
t27: v4f64 = vector_shuffle<0,5,2,7> t27, t26
t27: v4f64 = vector_shuffle<0,5,2,7> t27, t26
t27: v4f64 = vector_shuffle<0,5,2,7> t27, t26
t27: v4f64 = vector_shuffle<0,5,2,7> t27, t26
t27: v4f64 = vector_shuffle<0,5,2,7> t27, t26
t27: v4f64 = vector_shuffle<0,5,2,7> t27, t26
--
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 38640] New: -Wthread-safety runs into an infinite loop on self-recursive data
https://bugs.llvm.org/show_bug.cgi?id=38640
Bug ID: 38640
Summary: -Wthread-safety runs into an infinite loop on
self-recursive data
Product: clang
Version: unspecified
Hardware: PC
OS: All
Status: NEW
Severity: enhancement
Priority: P
Component: Static Analyzer
Assignee: dcough...@apple.com
Reporter: nicolaswe...@gmx.de
CC: llvm-bugs@lists.llvm.org
$ cat foo.ii
void g(int);
void f() {
int& s = s;
g(s);
}
$ time clang -Wthread-safety -c foo.ii
foo.ii:4:12: warning: reference 's' is not yet bound to a value when used
within its own initialization [-Wuninitialized]
int& s = s;
~ ^
^ Never terminates after this. (I only waited a few minutes, not really never.)
--
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 38641] New: clang miscompiles at -O2 and above on valid code
https://bugs.llvm.org/show_bug.cgi?id=38641
Bug ID: 38641
Summary: clang miscompiles at -O2 and above on valid code
Product: clang
Version: trunk
Hardware: PC
OS: All
Status: NEW
Severity: enhancement
Priority: P
Component: LLVM Codegen
Assignee: unassignedclangb...@nondot.org
Reporter: helloqi...@gmail.com
CC: llvm-bugs@lists.llvm.org
clang-r339936: first working build
clang-r339938: next failing build
$ clang-trunk -v
clang version 8.0.0 (trunk 340155)
Target: x86_64-unknown-linux-gnu
Thread model: posix
InstalledDir: /usr/local/bin
$ clang-trunk abc.c
$ ./a.out
$
$ clang-trunk -O2 abc.c
$ ./a.out
0
$ cat abc.c
int printf(const char *, ...);
int a = 1, b;
static short(c)(short d, int e) { return d < 0 ? d : d >> e; }
int main() {
char f = a;
if (c(f, 5))
printf("%d\n", b);
}
--
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 35306] "error in backend: unknown codeview register" while compiling optimized AVX-512 code
https://bugs.llvm.org/show_bug.cgi?id=35306 Zachary Turner changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED CC||ztur...@google.com --- Comment #2 from Zachary Turner --- Fixed in r340118 -- 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 38642] New: [IA][ARM64] literal value out of range for directive
https://bugs.llvm.org/show_bug.cgi?id=38642 Bug ID: 38642 Summary: [IA][ARM64] literal value out of range for directive Product: clang Version: trunk Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: Frontend Assignee: unassignedclangb...@nondot.org Reporter: ndesaulni...@google.com CC: echri...@gmail.com, kristof.be...@arm.com, kristof.be...@gmail.com, llvm-bugs@lists.llvm.org, oliver.stann...@arm.com, srhi...@google.com Created attachment 20744 --> https://bugs.llvm.org/attachment.cgi?id=20744&action=edit test.S In the Linux kernel (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/arm64/crypto/aes-modes.S), there's an assembly instruction: ldr q8, =0x300020001/* addends 1,2,3[,0] */ This produces the error: literal value out of range for directive I'm not sure what the `=` is supposed to do. 0x300020001 is 9B (72b), so q8 must be a vector register? $ cat /tmp/test.S .text .global _start _start: ldr q8, =0x300020001 $ aarch64-linux-gnu-as /tmp/test.S $ aarch64-linux-gnu-objdump -D a.out a.out: file format elf64-littleaarch64 Disassembly of section .text: <_start>: 0: 9c88ldr q8, 10 <_start+0x10> ... 10: 0001.word 0x0001 14: 0002.word 0x0002 18: 0003.word 0x0003 1c: .word 0x $ clang -target aarch64-linux-gnu /tmp/test.S /tmp/test.S:5:12: error: literal value out of range for directive ldr q8, =0x300020001 ^ I thought that =0x300020001 was maybe an immediate, but changing the `=` to a `#` produces a `bignum invalid` error in gas, and the same error in this bug's title in Clang. -- 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 18317] Assertion `!D->isInvalidDecl() && "Cannot get layout of invalid decl!"' failed on r193323
https://bugs.llvm.org/show_bug.cgi?id=18317 Reid Kleckner changed: What|Removed |Added Resolution|--- |FIXED CC||r...@google.com Status|NEW |RESOLVED --- Comment #3 from Reid Kleckner --- Clang definitely builds Chromium at this point, and we've changed record layout significantly since 2013. I think this must have been 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 18708] Crash when trying to build Qt 5.1.0 with clang from svn Trunk ( compiling with -faddress=sanitize
https://bugs.llvm.org/show_bug.cgi?id=18708 Reid Kleckner changed: What|Removed |Added Status|NEW |RESOLVED CC||r...@google.com Resolution|--- |FIXED --- Comment #8 from Reid Kleckner --- This was fixed at some point. I confirmed that the reduced code does not crash clang today. -- 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 15825] [not-a-bug, powerpc-darwin8] bad_alloc during assembly of RecursiveASTVisitorTest.cpp
https://bugs.llvm.org/show_bug.cgi?id=15825 Reid Kleckner changed: What|Removed |Added CC||r...@google.com Status|NEW |RESOLVED Resolution|--- |WONTFIX --- Comment #3 from Reid Kleckner --- I don't think we need to track this anymore, essentially it was an OOM while compiling RecursiveASTVisitorTest, which is a very large TU. -- 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 13096] Crash on invalid, "Cannot layout type before complete!" assertion fails
https://bugs.llvm.org/show_bug.cgi?id=13096 Reid Kleckner changed: What|Removed |Added CC||r...@google.com Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #9 from Reid Kleckner --- (In reply to Brian Brooks from comment #8) > Hi Nico - None of these reduced test cases crash on r167357 Based on that comment, we can close this. -- 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 15728] clang crashes with SIGSEV in clang::CodeGen::CodeGenFunction::EmitScalarExpr
https://bugs.llvm.org/show_bug.cgi?id=15728 Reid Kleckner changed: What|Removed |Added Resolution|--- |FIXED CC||r...@google.com Status|NEW |RESOLVED --- Comment #3 from Reid Kleckner --- (In reply to Benjamin Kramer from comment #2) > The crash doesn't reproduce with clang trunk. Then we can close this. -- 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 22401] Segmentation fault: 11, CreateLLVMCodeGen
https://bugs.llvm.org/show_bug.cgi?id=22401 Reid Kleckner changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED CC||r...@google.com --- Comment #4 from Reid Kleckner --- This does not crash anymore, or was caused by Chromium's plugins. -- 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 21181] Crash when building LLVM/CLANG from latest
https://bugs.llvm.org/show_bug.cgi?id=21181 Reid Kleckner changed: What|Removed |Added CC||r...@google.com Status|NEW |RESOLVED Resolution|--- |WONTFIX --- Comment #2 from Reid Kleckner --- The pre-processed source is no longer available and this is old, so let's close it. -- 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 7047] Nuisance "self-comparison" Warning from Template and Macro code
https://bugs.llvm.org/show_bug.cgi?id=7047 Reid Kleckner changed: What|Removed |Added CC||r...@google.com Resolution|--- |WONTFIX Status|NEW |RESOLVED --- Comment #7 from Reid Kleckner --- I think our decision here from 2010 stands and we can close this. -- 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 12025] fix-it for '->' versus '.'
https://bugs.llvm.org/show_bug.cgi?id=12025 Reid Kleckner changed: What|Removed |Added CC||r...@google.com Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #2 from Reid Kleckner --- Works for me today. We get all four fixit suggestions in c++ mode. -- 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 38643] New: BPF: Assertion faliure at BPFAsmBackend.cpp:73: Assertion `Value == 0' failed
https://bugs.llvm.org/show_bug.cgi?id=38643 Bug ID: 38643 Summary: BPF: Assertion faliure at BPFAsmBackend.cpp:73: Assertion `Value == 0' failed Product: libraries Version: 6.0 Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: Core LLVM classes Assignee: unassignedb...@nondot.org Reporter: tstel...@redhat.com CC: alexei.starovoi...@gmail.com, llvm-bugs@lists.llvm.org Created attachment 20745 --> https://bugs.llvm.org/attachment.cgi?id=20745&action=edit C test case The attached test cases trigger assertion failures in BPFAsmBackend::applyFixup() with llvm/clang 6.0.1. I've provided the original C test case as well as a reduced LLVM IR To reproduce: clang -target bpf kprobes_kern.c or ./llc -march=bpf bpf-fixup-crash.ll -filetype=obj -- 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 38644] New: multimap::clear() missing exception specifier
https://bugs.llvm.org/show_bug.cgi?id=38644
Bug ID: 38644
Summary: multimap::clear() missing exception specifier
Product: libc++
Version: unspecified
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P
Component: All Bugs
Assignee: unassignedclangb...@nondot.org
Reporter: stephen.w...@bregmasoft.ca
CC: llvm-bugs@lists.llvm.org, mclow.li...@gmail.com
std::multimap::clear() is missing the noexcept specifier (see ISO/IEC 14882
[multimap.overview).
The following test case will raise an assertion.
#include
int
main()
{
std::multimap mymap;
static_assert(noexcept(mymap.clear()), "missing noexcept specifier");
}
--
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 38645] New: [COFF] LLD Crashing binary when compiling with LDC and build with LLD
https://bugs.llvm.org/show_bug.cgi?id=38645 Bug ID: 38645 Summary: [COFF] LLD Crashing binary when compiling with LDC and build with LLD Product: lld Version: unspecified Hardware: PC OS: Windows NT Status: NEW Severity: normal Priority: P Component: COFF Assignee: unassignedb...@nondot.org Reporter: radu.raca...@gmail.com CC: llvm-bugs@lists.llvm.org Created attachment 20747 --> https://bugs.llvm.org/attachment.cgi?id=20747&action=edit Program D source code When compiling the attached program with LDC 1.11.0 (latest release ATM) and linking with LLD for Win32 x86-64 the resulting binary will crash with an access violation. The same program linked with the MS linker works. To get LDC 1.11.0, download the Window x86-64 variant https://github.com/ldc-developers/ldc/releases/download/v1.11.0/ldc2-1.11.0-windows-x64.7z The setup used Visual Studio Community 2017 for the system libraries. Command line for building the binary: ``` %LDC_HOME%\bin\ldc2.exe -m64 -v -linker=lld-link bug.d ``` This will print the linker parameters also. The probable cause is related with the size of the .rdata section, as by reducing the size of the big enum string in the example program the crash disappears. This bug is also tracked at https://github.com/ldc-developers/ldc/issues/2823 -- 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 38646] New: Hexagon buildbots broken
https://bugs.llvm.org/show_bug.cgi?id=38646
Bug ID: 38646
Summary: Hexagon buildbots broken
Product: libraries
Version: trunk
Hardware: PC
OS: Windows NT
Status: NEW
Severity: enhancement
Priority: P
Component: Global Analyses
Assignee: unassignedb...@nondot.org
Reporter: kparz...@codeaurora.org
CC: llvm-bugs@lists.llvm.org
Created attachment 20748
--> https://bugs.llvm.org/attachment.cgi?id=20748&action=edit
preprocessed file
Using clang 3.7.x or 3.8.0:
clang++ -std=c++11 -O3 -fno-exceptions -fno-rtti -c
IteratedDominanceFrontier.ii
In file included from
/w/src/llvm.org/lib/Analysis/IteratedDominanceFrontier.cpp:14:
In file included from
/w/src/llvm.org/include/llvm/Analysis/IteratedDominanceFrontier.h:27:
In file included from /w/src/llvm.org/include/llvm/ADT/DenseMap.h:17:
In file included from /w/src/llvm.org/include/llvm/ADT/DenseMapInfo.h:17:
In file included from /w/src/llvm.org/include/llvm/ADT/ArrayRef.h:13:
In file included from /w/src/llvm.org/include/llvm/ADT/Hashing.h:49:
In file included from /w/src/llvm.org/include/llvm/Support/Host.h:17:
In file included from /w/src/llvm.org/include/llvm/ADT/StringMap.h:17:
In file included from /w/src/llvm.org/include/llvm/ADT/StringRef.h:13:
In file included from /w/src/llvm.org/include/llvm/ADT/STLExtras.h:20:
In file included from /w/src/llvm.org/include/llvm/ADT/Optional.h:22:
In file included from /w/src/llvm.org/include/llvm/Support/type_traits.h:19:
/w/c/clang+llvm-3.7.0-x86_64-linux-gnu-ubuntu-14.04/include/c++/v1/utility:264:86:
error: no matching constructor for initialization of
'llvm::WrappedPairNodeDataIterator *,
llvm::BasicBlock *>, const llvm::GraphDiff *>'
__attribute__ ((__visibility__("hidden"), __always_inline__)) constexpr
pair() : first(), second() {}
^
/w/c/clang+llvm-3.7.0-x86_64-linux-gnu-ubuntu-14.04/include/c++/v1/type_traits:2375:38:
note: in instantiation of member function
'std::__1::pair *,
llvm::BasicBlock *>, const llvm::GraphDiff *>,
llvm::WrappedPairNodeDataIterator *,
llvm::BasicBlock *>, const llvm::GraphDiff *>
>::pair' requested here
: public integral_constant
^
/w/c/clang+llvm-3.7.0-x86_64-linux-gnu-ubuntu-14.04/include/c++/v1/type_traits:2679:14:
note: in instantiation of template class
'std::__1::is_constructible *,
llvm::BasicBlock *>, const llvm::GraphDiff *>,
llvm::WrappedPairNodeDataIterator *,
llvm::BasicBlock *>, const llvm::GraphDiff *> >>'
requested here
: public is_constructible<_Tp>
^
/w/c/clang+llvm-3.7.0-x86_64-linux-gnu-ubuntu-14.04/include/c++/v1/tuple:387:13:
note: in instantiation of template class
'std::__1::is_default_constructible *,
llvm::BasicBlock *>, const llvm::GraphDiff *>,
llvm::WrappedPairNodeDataIterator *,
llvm::BasicBlock *>, const llvm::GraphDiff *> > >'
requested here
: __all::value...>
^
/w/c/clang+llvm-3.7.0-x86_64-linux-gnu-ubuntu-14.04/include/c++/v1/tuple:551:26:
note: in instantiation of template class
'std::__1::__all_default_constructible *,
llvm::BasicBlock *>, const llvm::GraphDiff *>,
llvm::WrappedPairNodeDataIterator *,
llvm::BasicBlock *>, const llvm::GraphDiff *> > > >'
requested here
__all_default_constructible<
^
/w/c/clang+llvm-3.7.0-x86_64-linux-gnu-ubuntu-14.04/include/c++/v1/tuple:561:9:
note: while substituting prior template arguments into non-type template
parameter [with _Up = , std::__1::pair *, llvm::BasicBlock *>, const llvm::GraphDiff
*>, llvm::CFGViewSuccessors::DeletedEdgesFilter,
std::__1::bidirectional_iterator_tag>,
llvm::filter_iterator_impl, std::__1::pair *, llvm::BasicBlock *>, const llvm::GraphDiff
*>, llvm::CFGViewSuccessors::DeletedEdgesFilter,
std::__1::bidirectional_iterator_tag> >,
std::__1::pair *,
llvm::BasicBlock *>, const llvm::GraphDiff *>,
llvm::WrappedPairNodeDataIterator *,
llvm::BasicBlock *>, const llvm::GraphDiff *> > >
&>]
tuple(_Up&&... __u)
^
/w/c/clang+llvm-3.7.0-x86_64-linux-gnu-ubuntu-14.04/include/c++/v1/tuple:498:56:
note: while substituting deduced template arguments into function template
'tuple' [with _Up = , std::__1::pair *, llvm::BasicBlock *>, const llvm::GraphDiff
*>, llvm::CFGViewSuccessors::DeletedEdgesFilter,
std::__1::bidirectional_iterator_tag>,
llvm::filter_iterator_impl, std::__1::pair *, llvm::BasicBlock *>, const llvm::GraphDiff
*>, llvm::CFGViewSuccessors::DeletedEdgesFilter,
std::__1::bidirectional_iterator_tag> >,
std::__1::pair *,
llvm::BasicBlock *>, const llvm::GraphDiff *>,
llvm::WrappedPairNodeDataIterator *,
llvm::BasicBlock *>, const llvm::GraphDiff *> > >
&>, $1 = (no value)]
class __attribute__ ((__type_visibility__("default"))) tuple
^
/w/src/llvm.org/incl
[llvm-bugs] [Bug 38406] [meta] 7.0.0 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=38406 Bug 38406 depends on bug 38637, which changed state. Bug 38637 Summary: Merge r340171 into LLVM 7.0 https://bugs.llvm.org/show_bug.cgi?id=38637 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |INVALID -- 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 38637] Merge r340171 into LLVM 7.0
https://bugs.llvm.org/show_bug.cgi?id=38637 Samuel Pitoiset changed: What|Removed |Added Resolution|--- |INVALID Status|NEW |RESOLVED --- Comment #1 from Samuel Pitoiset --- Both patches have been reverted with r340202. I will create a new issue when the correct fix will be upstream and ready to be backported. -- 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 38647] New: LLD can crash if exiting due to errors in writeTo
https://bugs.llvm.org/show_bug.cgi?id=38647 Bug ID: 38647 Summary: LLD can crash if exiting due to errors in writeTo Product: lld Version: unspecified Hardware: PC OS: All Status: NEW Severity: normal Priority: P Component: COFF Assignee: unassignedb...@nondot.org Reporter: mar...@martin.st CC: llvm-bugs@lists.llvm.org If LLD chooses to exit due to errors (either due to a 'fatal', or too many 'error') from within the writeTo methods (which are run in parallel), the linker can easily crash. The writeTo methods are run in parallel on many threads. When one of these threads report errors that lead to the linker exiting, calling the exitLld function, the exitLld function closes the output buffer, which can cause the other threads to crash (which still are trying to write output data to the buffer). One way of making the error less prone to happen would to change most 'fatal' into 'error' in Chunks.cpp, but that could still cause the linker to error out once one has encountered too many errors. -- 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 38648] New: MultiSource/Applications/siod fails on X86-64 with clang 7.0.0-rc1
https://bugs.llvm.org/show_bug.cgi?id=38648
Bug ID: 38648
Summary: MultiSource/Applications/siod fails on X86-64 with
clang 7.0.0-rc1
Product: clang
Version: 7.0
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: -New Bugs
Assignee: unassignedclangb...@nondot.org
Reporter: tstel...@redhat.com
CC: llvm-bugs@lists.llvm.org
Blocks: 38406
This is a regression, this test executes correctly with clang 6.0.1. Running
the command:
${TEST_SUITE_BUILDDIR}/MultiSource/Applications/siod/siod -v1
${TEST_SUITE_SRCDIR}/test-suite/MultiSource/Applications/siod/test.scm
Produces an error:
Content-type: text/plain
10
9
8
7
6
5
4
3
2
1
-42 is negative
0 is zero
42 is positive
the value of (get 'answer 'value) is 42
the value of (get 'answer 'value) is xyzzy
the 33rd Fibonacci number is ERROR: damaged frame (see errobj)
I am going to try to bisect this.
Referenced Bugs:
https://bugs.llvm.org/show_bug.cgi?id=38406
[Bug 38406] [meta] 7.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
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 38649] New: multiply lowering of divide-by-constant doesn't occur on haswell
https://bugs.llvm.org/show_bug.cgi?id=38649
Bug ID: 38649
Summary: multiply lowering of divide-by-constant doesn't occur
on haswell
Product: libraries
Version: trunk
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: Backend: X86
Assignee: unassignedb...@nondot.org
Reporter: jorg.br...@gmail.com
CC: llvm-bugs@lists.llvm.org
Source:
struct SecsAndTicks {
uint64_t seconds;
uint32_t ticks;
};
SecsAndTicks DivBy4Bill(uint64_t tix) {
return {tix / 40,
uint32_t(tix % 40)};
}
x86-64 codegen:
movq%rdi, %rax
shrq$11, %rax
movabsq $4835703278458517, %rcx # imm = 0x112E0BE826D695
mulq%rcx
shrq$9, %rdx
imull $-294967296, %edx, %eax # imm = 0xEE6B2800
subl%eax, %edi
movq%rdx, %rax
movl%edi, %edx
retq
march=haswell codegen:
movl$40, %ecx # imm = 0xEE6B2800
movq%rdi, %rax
shrq$32, %rax
je .LBB0_1
xorl%edx, %edx
movq%rdi, %rax
divq%rcx
retq
.LBB0_1:
xorl%edx, %edx
movl%edi, %eax
divl%ecx
retq
See https://godbolt.org/g/qGTDGN for repro
--
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 38639] lowerVectorShuffleByMerging128BitLanes - Detected cycle in SelectionDAG
https://bugs.llvm.org/show_bug.cgi?id=38639 Craig Topper changed: What|Removed |Added Fixed By Commit(s)||r340214 Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #2 from Craig Topper --- Fixed in r340214 -- 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 38511] opt crashes with 'Assertion `ResultPass && "getAnalysis*() called on an analysis that was not " "'required' by pass!"' failed.' when doing "opt -loop-reduce -iv-users -scalariz
https://bugs.llvm.org/show_bug.cgi?id=38511 Craig Topper changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED Fixed By Commit(s)||r340210 --- Comment #4 from Craig Topper --- Fixed in r340210 -- 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 38650] New: wasm32: Slowdown with large amount of relocations (?)
https://bugs.llvm.org/show_bug.cgi?id=38650 Bug ID: 38650 Summary: wasm32: Slowdown with large amount of relocations (?) Product: lld Version: unspecified Hardware: PC OS: All Status: NEW Severity: enhancement Priority: P Component: All Bugs Assignee: unassignedb...@nondot.org Reporter: a...@crichton.co CC: llvm-bugs@lists.llvm.org, s...@chromium.org When working with some wasm tools earlier today I realized that for one of our compilations in rust-lang/rust it takes LLD around 4 seconds to finish. I was quite surprised at this runtime because typically our linker invocations are quite speedy (under 1s most of the time, even non-incremental). A gist [1] contains a tarball with a reproduction script and all the necessary files and there's also a direct link [2] to the tarball itself. I do realize though that this is quite a large test case, there's ~100MB of input files which is generating ~20MB of an output. I suspect though that there may be some low hanging fruit to clear out though to improve link time here! [1]: https://gist.github.com/alexcrichton/cd4736e3faebbc7e45609a8b82a77d2a [2]: https://gist.github.com/alexcrichton/cd4736e3faebbc7e45609a8b82a77d2a/raw/e92638fb6f6706c7ada3567e232358cba00993b8/slow-lld-invocation.tar.xz -- 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 16569] Assertion `begin() + idx < end()` failed
https://bugs.llvm.org/show_bug.cgi?id=16569 Reid Kleckner changed: What|Removed |Added Status|NEW |RESOLVED CC||r...@google.com Resolution|--- |FIXED --- Comment #6 from Reid Kleckner --- The pre-processed source compiles today. -- 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 23057] fuzz clang
https://bugs.llvm.org/show_bug.cgi?id=23057 Bug 23057 depends on bug 21868, which changed state. Bug 21868 Summary: [fuzz] Assertion `I != Vec.end() && "list does not contain decl"' failed. https://bugs.llvm.org/show_bug.cgi?id=21868 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 21868] [fuzz] Assertion `I != Vec.end() && "list does not contain decl"' failed.
https://bugs.llvm.org/show_bug.cgi?id=21868 Reid Kleckner changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED CC||r...@google.com --- Comment #1 from Reid Kleckner --- Doesn't crash anymore. -- 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 21862] [fuzz] Assertion `LHS.isValid() && RHS.isValid() && "Passed invalid source location!"' failed.
https://bugs.llvm.org/show_bug.cgi?id=21862 Reid Kleckner changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED CC||r...@google.com --- Comment #1 from Reid Kleckner --- Doesn't crash anymore. -- 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 23057] fuzz clang
https://bugs.llvm.org/show_bug.cgi?id=23057 Bug 23057 depends on bug 21862, which changed state. Bug 21862 Summary: [fuzz] Assertion `LHS.isValid() && RHS.isValid() && "Passed invalid source location!"' failed. https://bugs.llvm.org/show_bug.cgi?id=21862 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 38651] New: Microsoft C++ doesn't consider anonymous namespaces for back-referencing
https://bugs.llvm.org/show_bug.cgi?id=38651
Bug ID: 38651
Summary: Microsoft C++ doesn't consider anonymous namespaces
for back-referencing
Product: clang
Version: unspecified
Hardware: PC
OS: Windows NT
Status: NEW
Severity: enhancement
Priority: P
Component: -New Bugs
Assignee: unassignedclangb...@nondot.org
Reporter: ztur...@google.com
CC: llvm-bugs@lists.llvm.org, r...@google.com
If you have this code:
// foo.cpp
namespace {
namespace {
int X;
}
}
//
We mangle this as:
?X@?A0xE81D4E31@?A0xE81D4E31@@3HA
while cl mangles this as:
?X@?A0xed6ebf2d@1@3HA
It's fine that the hash values don't match, but it's a bug that we don't store
this hash in the back-reference table. Consider this example instead:
namespace X { namespace X {
namespace { namespace {
namespace Y { namespace Y {
int Z;
} }
} }
} }
Now we mangle this as:
?Z@Y@1?A0xE81D4E31@?A0xE81D4E31@X@2@3HA
And Microsoft's own undname demangles this as:
int A0xE81D4E31::X::`anonymous namespace'::`anonymous namespace'::Y::Y::Z
which is obviously wrong.
This example might seem contrived, but you can make it matter in a more
realistic example too:
//
namespace {
struct X {};
X anonFunc(X x, X y);
template void foo(T t);
}
Here, we mangle anonFunc as:
?anonFunc@?A0xE81D4E31@@YA?AUX@?A0xE81D4E31@@U1?A0xE81D4E31@@0@Z
which undname demangles as:
struct `anonymous namespace'::X __cdecl `anonymous namespace'::anonFunc(struct
`anonymous namespace'::A0xE81D4E31,struct `anonymous namespace'::A0xE81D4E31)
(Note both function parameter types are nonsensical).
--
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 38632] wasm32: atomic_notify intrinsic disagrees with Gecko/wabt implementations
https://bugs.llvm.org/show_bug.cgi?id=38632 Heejin Ahn changed: What|Removed |Added CC||ahee...@gmail.com Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #1 from Heejin Ahn --- Turned out that we once changed the type of the wake count from i32 to i64 and then decided to revert it back to i32, but the spec was not update accordingly. Fixed in the following commits: https://reviews.llvm.org/rL340234 https://reviews.llvm.org/rL340235 https://github.com/WebAssembly/threads/commit/a8b68bbb0c90f66816c8073f6a3f9ef23f94d41f -- 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 38652] New: LLVM go bindings test fails when using LLD
https://bugs.llvm.org/show_bug.cgi?id=38652 Bug ID: 38652 Summary: LLVM go bindings test fails when using LLD Product: new-bugs Version: unspecified Hardware: PC OS: Windows NT Status: NEW Severity: enhancement Priority: P Component: new bugs Assignee: unassignedb...@nondot.org Reporter: r...@google.com CC: llvm-bugs@lists.llvm.org The go bindings tests fail on my machine. I don't think LLD recognizes zlib-gnu, and I'm not sure it can be made to. $ ninja check Already up to date. Current branch master is up to date. [83/84] Running the LLVM regression tests FAIL: LLVM :: Bindings/Go/go.test (14691 of 27228) TEST 'LLVM :: Bindings/Go/go.test' FAILED Script: -- : 'RUN: at line 1'; /usr/local/google/home/rnk/llvm-project/build/bin/llvm-go go=/usr/lib/google-golang/bin/go test llvm.org/llvm/bindings/go/llvm -- Exit Code: 1 Command Output (stdout): -- FAILllvm.org/llvm/bindings/go/llvm [build failed] -- Command Output (stderr): -- # llvm.org/llvm/bindings/go/llvm.test /usr/lib/google-golang/pkg/tool/linux_amd64/link: running /usr/local/google/home/rnk/chromium/src/third_party/llvm-build/Release+Asserts/bin/clang++ failed: exit status 1 ld.lld: error: unknown --compress-debug-sections value: zlib-gnu clang: error: linker command failed with exit code 1 (use -v to see invocation) -- Testing Time: 47.78s Failing Tests (1): LLVM :: Bindings/Go/go.test Expected Passes: 26533 Expected Failures : 148 Unsupported Tests : 546 Unexpected Failures: 1 FAILED: test/CMakeFiles/check-llvm cd /usr/local/google/home/rnk/llvm-project/build/test && /usr/bin/python2.7 /usr/local/google/home/rnk/llvm-project/build/./bin/llvm-lit -sv /usr/local/google/home/rnk/llvm-project/build/test ninja: build stopped: subcommand 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 38623] Assertion in CodeGen fails when a reference to a global variable is captured by a block
https://bugs.llvm.org/show_bug.cgi?id=38623 Akira Hatanaka changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #3 from Akira Hatanaka --- Thank you for the quick fix! Confirmed that the assertion doesn't fail anymore. -- 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 38653] New: The argument to __has_builtin (and maybe __has_feature?) should be macro-expanded.
https://bugs.llvm.org/show_bug.cgi?id=38653 Bug ID: 38653 Summary: The argument to __has_builtin (and maybe __has_feature?) should be macro-expanded. Product: clang Version: unspecified Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: Frontend Assignee: unassignedclangb...@nondot.org Reporter: bmo...@google.com CC: llvm-bugs@lists.llvm.org I was working around bug 16404 (short version: __builtin_mul_overflow doesn't work unless linking with compiler_rt), and since the relevant code guards the usages with __has_builtin, Richard Smith suggested that I could hack around it with this "extremely dubious hack": -D__builtin_mul_overflow=__builtin_no_such_builtin Unfortunately, this doesn't work, since __has_builtin doesn't macro-expand its argument. As Richard pointed out in private chat, "I'm not sure that hack failing is a solid justification for changing it." On the other hand, this behavior is surprising and inconsistent with what we'd get if __has_builtin were a true function or macro, and I'd argue that that's a good reason to change it to be less surprising. And it's not just me that had this expectation -- the documentation for __has_feature notes, "The feature name or extension name can also be specified with a preceding and following __ (double underscore) to avoid interference from a macro with the same name," so clearly the author of that documentation assumed the argument would be macro-expanded. -- 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 38654] New: MultiSource/Benchmarks/DOE-ProxyApps-C++/CLAMP fails to build with newer libstdc++
https://bugs.llvm.org/show_bug.cgi?id=38654
Bug ID: 38654
Summary: MultiSource/Benchmarks/DOE-ProxyApps-C++/CLAMP fails
to build with newer libstdc++
Product: Test Suite
Version: 7.0
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: Programs Tests
Assignee: unassignedb...@nondot.org
Reporter: tstel...@redhat.com
CC: llvm-bugs@lists.llvm.org
Blocks: 38406
Created attachment 20750
--> https://bugs.llvm.org/attachment.cgi?id=20750&action=edit
Build fix
I get the following error with gcc/libstdc++ 8.2 when trying to compile
MultiSource/Benchmarks/DOE-ProxyApps-C++/CLAMP. The attached patch fixes it
for me.
gcc -DNDEBUG
-I/usr/share/llvm-test-suite/MultiSource/Benchmarks/DOE-ProxyApps-C++/CLAMR
-IMultiSource/Benchmarks/DOE-ProxyApps-C++/CLAMR -O2 -DNDEBUG -o
MallocPlus.cpp.o -c
/usr/share/llvm-test-suite/MultiSource/Benchmarks/DOE-ProxyApps-C++/CLAMR/MallocPlus.cpp
In file included from /usr/include/c++/8/map:60,
from
/usr/share/llvm-test-suite/MultiSource/Benchmarks/DOE-ProxyApps-C++/CLAMR/MallocPlus.h:56,
from
/usr/share/llvm-test-suite/MultiSource/Benchmarks/DOE-ProxyApps-C++/CLAMR/MallocPlus.cpp:61:
/usr/include/c++/8/bits/stl_tree.h: In instantiation of 'class
std::_Rb_tree, std::pair, malloc_plus_memory_entry*>,
std::_Select1st,
malloc_plus_memory_entry*> >, cmp_str, std::allocator, malloc_plus_memory_entry*> > >':
/usr/include/c++/8/bits/stl_map.h:151:17: required from 'class
std::map, malloc_plus_memory_entry*, cmp_str>'
/usr/share/llvm-test-suite/MultiSource/Benchmarks/DOE-ProxyApps-C++/CLAMR/MallocPlus.cpp:97:48:
required from here
/usr/include/c++/8/bits/stl_tree.h:452:21: error: static assertion failed:
comparison object must be invocable with two arguments of key type
static_assert(__is_invocable<_Compare&, const _Key&, const _Key&>{},
Referenced Bugs:
https://bugs.llvm.org/show_bug.cgi?id=38406
[Bug 38406] [meta] 7.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
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 38655] New: sparc membar instruction not supported
https://bugs.llvm.org/show_bug.cgi?id=38655
Bug ID: 38655
Summary: sparc membar instruction not supported
Product: libraries
Version: trunk
Hardware: PC
OS: Windows NT
Status: NEW
Severity: enhancement
Priority: P
Component: Backend: Sparc
Assignee: unassignedb...@nondot.org
Reporter: b...@comstyle.com
CC: llvm-bugs@lists.llvm.org
The Sparc backend for SPARCv9 does not support the membar instruction.
/usr/local/include/c++/4.9.4/sparc64-unknown-openbsd6.2/bits/atomic_word.h:38:21:
\
note: expanded from macro '_GLIBCXX_READ_MEM_BARRIER' __asm __volatile
("membar \
#LoadLoad":::"memory") ^
:1:9: note: instantiated into assembly here
membar #LoadLoad
^
/usr/local/include/c++/4.9.4/sparc64-unknown-openbsd6.2/bits/atomic_word.h:40:21:
\
note: expanded from macro '_GLIBCXX_WRITE_MEM_BARRIER'
\
__asm __volatile ("membar #StoreStore":::"memory")
^
:1:9: note: instantiated into assembly here
membar #StoreStore
^
--
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 37241] Crash in sema::FunctionScopeInfo::markSafeWeakUse
https://bugs.llvm.org/show_bug.cgi?id=37241 Timothy J. Wood changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #3 from Timothy J. Wood --- I'm no longer seeing this problem on trunk builds (tried on r340246). -- 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 9994 in oss-fuzz: llvm/llvm-demangle-fuzzer: Stack-overflow in llvm::itanium_demangle::Db::parseEncoding
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com, igm...@gmail.com, eney...@google.com, llvm-b...@lists.llvm.org, j...@chromium.org, v...@apple.com, mitchphi...@outlook.com, xpl...@gmail.com, akils...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible Engine-libfuzzer Proj-llvm Reported-2018-08-21 Type: Bug New issue 9994 by ClusterFuzz-External: llvm/llvm-demangle-fuzzer: Stack-overflow in llvm::itanium_demangle::Db::parseEncoding https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=9994 Detailed report: https://oss-fuzz.com/testcase?key=5681464745132032 Project: llvm Fuzzer: libFuzzer_llvm_llvm-demangle-fuzzer Fuzz target binary: llvm-demangle-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Stack-overflow Crash Address: 0x7fff2d64bfe8 Crash State: llvm::itanium_demangle::Db::parseEncoding llvm::itanium_demangle::Db::parseName llvm::itanium_demangle::Db::parseClassEnumType Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201808200140:201808202008 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5681464745132032 Issue filed automatically. See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for more information. When you fix this bug, please * mention the fix revision(s). * state whether the bug was a short-lived regression or an old bug in any stable releases. * add any other useful information. This information can help downstream consumers. If you need to contact the OSS-Fuzz team with a question, concern, or any other feedback, please file an issue at https://github.com/google/oss-fuzz/issues. -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
