[llvm-bugs] [Bug 24896] "Process 1 was reported... but no stop reply packet was received" error from TestConnectRemote on FreeBSD
https://bugs.llvm.org/show_bug.cgi?id=24896 Michał Górny changed: What|Removed |Added CC||mgo...@gentoo.org Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #1 from Michał Górny --- This test works now that we have a remote plugin. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 25057] On x86_64-FreeBSD Platform, LLDB hangs while debugging an inferior with 'int3' assembly instruction.
https://bugs.llvm.org/show_bug.cgi?id=25057 Michał Górny changed: What|Removed |Added CC||mgo...@gentoo.org Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 25624] TestFdLeak fails on FreeBSD with Python 2.7.10
https://bugs.llvm.org/show_bug.cgi?id=25624 Michał Górny changed: What|Removed |Added Resolution|--- |FIXED CC||mgo...@gentoo.org Status|NEW |RESOLVED --- Comment #6 from Michał Górny --- This test should be good now. Besides, LLDB no longer supports Python 2. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 25625] TestCppIncompleteTypes failing on FreeBSD 11 buildbot
https://bugs.llvm.org/show_bug.cgi?id=25625 Michał Górny changed: What|Removed |Added Resolution|--- |FIXED CC||mgo...@gentoo.org Status|NEW |RESOLVED --- Comment #1 from Michał Górny --- The test passes for me now. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 25626] expectedFailureClang decorator may not work on FreeBSD
https://bugs.llvm.org/show_bug.cgi?id=25626 Michał Górny changed: What|Removed |Added CC||mgo...@gentoo.org Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #5 from Michał Górny --- The decorator seems to work fine now, so I've removed the duplicate xfail for FreeBSD. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 25819] TestNamespaceLookup is failing on FreeBSD
https://bugs.llvm.org/show_bug.cgi?id=25819 Michał Górny changed: What|Removed |Added CC||mgo...@gentoo.org Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #5 from Michał Górny --- Seems to be passing for me now. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 26565] test_expr_with_macros_dwarf (TestMacros.TestMacros) failing on FreeBSD 11
https://bugs.llvm.org/show_bug.cgi?id=26565 Michał Górny changed: What|Removed |Added Resolution|--- |FIXED CC||mgo...@gentoo.org Status|NEW |RESOLVED --- Comment #3 from Michał Górny --- It's marked xfail for clang, so I suppose there's nothing specific to be done for FreeBSD. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 26566] test_with_run_command_dwarf (TestDataFormatterLibcxxListLoop.LibcxxListDataFormatterTestCase) failing on FreeBS 11
https://bugs.llvm.org/show_bug.cgi?id=26566 Michał Górny changed: What|Removed |Added CC||mgo...@gentoo.org Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #1 from Michał Górny --- Works for me. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 26924] LLDB doesn't handle FreeBSD's setproctitle() call properly
https://bugs.llvm.org/show_bug.cgi?id=26924 Michał Górny changed: What|Removed |Added CC||mgo...@gentoo.org Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #5 from Michał Górny --- This is fixed with the new plugin. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 26937] TestRegisterVariables failing with Clang 3.4.1 on FreeBSD
https://bugs.llvm.org/show_bug.cgi?id=26937 Michał Górny changed: What|Removed |Added Resolution|--- |FIXED CC||mgo...@gentoo.org Status|NEW |RESOLVED --- Comment #2 from Michał Górny --- I see it's restricted to old clang today, and it passes for me on 13.0. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 36527] test_*int*_t_dwarf failing on FreeBSD
https://bugs.llvm.org/show_bug.cgi?id=36527 Michał Górny changed: What|Removed |Added Resolution|--- |FIXED CC||mgo...@gentoo.org Status|NEW |RESOLVED --- Comment #2 from Michał Górny --- The tests changed a bit and they certainly don't fail for me now. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 48425] New: [CloneModule] Cloned module retains some pointers to original module's objects
https://bugs.llvm.org/show_bug.cgi?id=48425 Bug ID: 48425 Summary: [CloneModule] Cloned module retains some pointers to original module's objects Product: libraries Version: trunk Hardware: All OS: All Status: NEW Severity: normal Priority: P Component: Transformation Utilities Assignee: unassignedb...@nondot.org Reporter: itay.bookst...@nextsilicon.com CC: llvm-bugs@lists.llvm.org When BlockAddresses are used as initializers of GlobalVariables, and the module is cloned, the BlockAddress constants used as initializers in the cloned module contain pointers to the BasicBlocks of the old module rather than the new one. As far as I can tell, in ValueMapper.cpp, Mapper::flush() attempts to RAUW the temporary basic block it created when attempting to map the BlockAddress constant which it encountered as the initializer of a GlobalVariable, and it passes the OldBB when failing to find a target. To my limited understanding, it sounds risky/incorrect to fall-back to the OldBB there. The BasicBlocks themselves are of course properly mapped/cloned into the new module in CloneFunction.cpp, in function llvm::CloneFunctionInto, but a comment there seems to talk exactly about it not being legal to clone a function that has an external BlockAddress referencing 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 37506] vector operations fail to optimize to _mm_testz_si128 / _mm256_testz_si256
https://bugs.llvm.org/show_bug.cgi?id=37506 Simon Pilgrim changed: What|Removed |Added Fixed By Commit(s)||0101fb73de71132bd5b25cfadc6 ||3974c692dbc5b Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #1 from Simon Pilgrim --- I'm going to resolve this - InstCombine will now expand MOVMSK intrinsics to a generic bitcast(trunc(icmp_slt(x))) pattern that can be optimized much further, and the backend does a good job of lowering such reduction patterns to PTEST where appropriate. In this case we still use MOVMSK as we can avoid the constant load and just perform it as a CMP+MOVMSK; after 0101fb73de71132bd5b25cfadc63974c692dbc5b we remove all ashr/icmp ops and just use MOVMSK to directly extract the signbits of the loaded vectors. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 48326] ICE: Assertion `Num < NumOperands && "Invalid child # of SDNode!"' failed with -march=skylake-avx512 -O3
https://bugs.llvm.org/show_bug.cgi?id=48326 Simon Pilgrim changed: What|Removed |Added CC||bing1...@intel.com Resolution|--- |FIXED Fixed By Commit(s)||eee30a6dceb6da8467fa3e0a7cd ||35b5a221bed0f Status|NEW |RESOLVED --- Comment #2 from Simon Pilgrim --- This was fixed by D92548 / rGeee30a6dceb6da8467fa3e0a7cd35b5a221bed0f -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 48426] New: Backport 79657e2: Avoid setting the delete-on-close bit if a TempFil… …e doesn't reside on a local drive
https://bugs.llvm.org/show_bug.cgi?id=48426 Bug ID: 48426 Summary: Backport 79657e2: Avoid setting the delete-on-close bit if a TempFil… …e doesn't reside on a local drive Product: new-bugs Version: 11.0 Hardware: PC OS: All Status: NEW Severity: enhancement Priority: P Component: new bugs Assignee: unassignedb...@nondot.org Reporter: rdwamp...@gmail.com CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org Blocks: 47800 Can https://reviews.llvm.org/D81803 be backported for the 11.0.1 release? This bug has existed since 7.0. Referenced Bugs: https://bugs.llvm.org/show_bug.cgi?id=47800 [Bug 47800] [meta] 11.0.1 Release Blockers -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 48055] Crash in Global Variable Optimizer: "Invalid GetElementPtrInst indices for type!"
https://bugs.llvm.org/show_bug.cgi?id=48055 Hiroshi Yamauchi changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #5 from Hiroshi Yamauchi --- Fixed with https://reviews.llvm.org/rGf9c3954a6ec5 -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 48427] New: [powerpc] -m32 should not define __powerpc64__
https://bugs.llvm.org/show_bug.cgi?id=48427 Bug ID: 48427 Summary: [powerpc] -m32 should not define __powerpc64__ Product: clang Version: trunk Hardware: PC OS: All Status: NEW Severity: enhancement Priority: P Component: Frontend Assignee: unassignedclangb...@nondot.org Reporter: ndesaulni...@google.com CC: kit.bar...@gmail.com, llvm-bugs@lists.llvm.org, neeil...@live.com, richard-l...@metafoo.co.uk, srhi...@google.com Blocks: 4068 For building the Linux kernel with Clang, particularly the 32b compat VDSO for powerpc64, we build one image file using `--target=powerpc64le-linux-gnu -m32`. It looks like in this case Clang's preprocessor #defines __powerpc64__. This causes compatibility issues for building this code with Clang (as GCC does not define this for -m32). See also: https://lore.kernel.org/linuxppc-dev/87czzlu7n4@mpe.ellerman.id.au/T/ Referenced Bugs: https://bugs.llvm.org/show_bug.cgi?id=4068 [Bug 4068] [Meta] Compiling the Linux kernel with 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 48428] New: x32: support variadic functions
https://bugs.llvm.org/show_bug.cgi?id=48428
Bug ID: 48428
Summary: x32: support variadic functions
Product: libraries
Version: trunk
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P
Component: Backend: X86
Assignee: har...@gigawatt.nl
Reporter: har...@gigawatt.nl
CC: craig.top...@gmail.com, llvm-bugs@lists.llvm.org,
llvm-...@redking.me.uk, pengfei.w...@intel.com,
spatel+l...@rotateright.com
The x86-64 ABI defines va_list as:
typedef struct {
unsigned int gp_offset;
unsigned int fp_offset;
void *overflow_arg_area;
void *reg_save_area;
} va_list[1];
LLVM hardcodes size, alignment and member offsets of this struct based on the
LP64 model, where the pointers have a size and alignment of 8 bytes. In the
ILP32 model, this is not correct. This occurs in X86ISelLowering in at least
LowerVACOPY and X86TargetLowering::EmitVAARG64WithCustomInserter.
I am reporting but self-assigning this to make sure it does not get forgotten.
The fixes for this are already available as part of
,
just need to be extracted and possibly cleaned up.
--
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 48429] New: Generated scatter instructions are slower than scalar version
https://bugs.llvm.org/show_bug.cgi?id=48429
Bug ID: 48429
Summary: Generated scatter instructions are slower than scalar
version
Product: libraries
Version: trunk
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: Backend: X86
Assignee: unassignedb...@nondot.org
Reporter: car...@google.com
CC: craig.top...@gmail.com, llvm-bugs@lists.llvm.org,
llvm-...@redking.me.uk, pengfei.w...@intel.com,
spatel+l...@rotateright.com
Compile the following code with command line
clang '--target=x86_64-grtev4-linux-gnu' -maes -m64 -mcx16 -msse4.2 -mpclmul
'-mprefer-vector-width=128' -fexperimental-new-pass-manager
-fsized-deallocation -O3 '-std=gnu++17' -c scatter.cc -save-temps
__attribute((target("avx,avx2,fma,avx512f,avx512dq,avx512bw"))) void
foo(int d, const float* ptr, float* dest)
{
const float* ptr_end = ptr + d;
for (; ptr != ptr_end; ++ptr, dest += 16) {
dest[0] = ptr[-1 * d];
dest[1] = ptr[0 * d];
dest[2] = ptr[1 * d];
dest[3] = ptr[2 * d];
}
}
llvm generates 4 element scatters, which is more than 50% slower than scalar
version on my skylake desktop.
The problem is in function int X86TTIImpl::getGatherScatterOpCost(), it has
already found scatter is not profitable if avx512vl is not enabled, so it
should be scalarized, and return a scalarized cost. But the caller
LoopVectorize doesn't know it's a scalarized cost, it thinks it's a scatter
cost, and compares it with a different scalar cost computed by
getMemInstScalarizationCost, and unfortunately X86 backend computed scalar cost
is smaller than LoopVectorize computed scalar cost, so LoopVectorize thinks
scatter is cheaper than scalarize, and generates the slow scatter version.
--
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 48430] New: CallAndMessageChecker would infinite loop
https://bugs.llvm.org/show_bug.cgi?id=48430 Bug ID: 48430 Summary: CallAndMessageChecker would infinite loop Product: clang Version: trunk Hardware: PC OS: Linux Status: NEW Severity: normal Priority: P Component: Static Analyzer Assignee: dcough...@apple.com Reporter: danny_sha...@outlook.com CC: dcough...@apple.com, llvm-bugs@lists.llvm.org Created attachment 24245 --> https://bugs.llvm.org/attachment.cgi?id=24245&action=edit Preprocessed source file to reproduce the error. The CallAndMessageChecker might get into infinite loop at 'generateVisitorsDiagnostics' function in 'BugReporter.cpp' due to a loop in the errorNode graph. I have attached a demo code that could reproduce this error. You could reproduce the error by running clang static analyzer on the code with 'core.CallAndMessage' checker. I am unsure what causes errorNode graph to contain a loop. Might be the function that passes right-value reference? -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 48177] clang returns 11 silently without any error
https://bugs.llvm.org/show_bug.cgi?id=48177 Erich Keane changed: What|Removed |Added Status|NEW |RESOLVED Fixed By Commit(s)||1c98f984105e Resolution|--- |FIXED --- Comment #7 from Erich Keane --- Fixed in 'main', I'll file a bug to merge into the 11 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 48431] New: Cherry pick 1c98f984105e to the 11 release branch.
https://bugs.llvm.org/show_bug.cgi?id=48431 Bug ID: 48431 Summary: Cherry pick 1c98f984105e to the 11 release branch. Product: clang Version: 11.0 Hardware: PC OS: Windows NT Status: NEW Severity: enhancement Priority: P Component: C++2a Assignee: unassignedclangb...@nondot.org Reporter: erich.ke...@intel.com CC: blitzrak...@gmail.com, erik.pilking...@gmail.com, llvm-bugs@lists.llvm.org, richard-l...@metafoo.co.uk This fixes a regression that affects compilation of 'boost', as filed here:https://bugs.llvm.org/show_bug.cgi?id=48177 -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 25686 in oss-fuzz: llvm:llvm-isel-fuzzer--aarch64-O2: Abrt in llvm::llvm_unreachable_internal
Updates: Labels: Deadline-Approaching Comment #1 on issue 25686 by sheriffbot: llvm:llvm-isel-fuzzer--aarch64-O2: Abrt in llvm::llvm_unreachable_internal https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=25686#c1 This bug is approaching its deadline for being fixed, and will be automatically derestricted within 7 days. If a fix is planned within 2 weeks after the deadline has passed, a grace extension can be granted. - Your friendly Sheriffbot -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 48432] New: [codeview] Different lambda functions getting the same codeview function ID
https://bugs.llvm.org/show_bug.cgi?id=48432
Bug ID: 48432
Summary: [codeview] Different lambda functions getting the same
codeview function ID
Product: libraries
Version: trunk
Hardware: PC
OS: All
Status: NEW
Severity: enhancement
Priority: P
Component: DebugInfo
Assignee: unassignedb...@nondot.org
Reporter: akhu...@google.com
CC: jdevliegh...@apple.com, keith.wal...@arm.com,
llvm-bugs@lists.llvm.org,
paul_robin...@playstation.sony.com
If there are multiple lambda functions in a file, they sometimes get the same
function id.
In the symbolizer output below, both lambda functions in the stack trace have
the line number 5, even though the second one should be on line 6.
repro:
$ cat t.cpp
template void uselambda1(int &x, F f) { f(x); }
template void uselambda2(int &x, F f) { f(x); }
int Test(int n) {
uselambda1(n, [](int &x) { x /= 10; });
uselambda2(n, [](int &x) { x *= 2; });
return n;
}
int main() {
return Test(100);
}
$ clang -cc1 -triple x86_64-pc-windows-msvc -gcodeview
-debug-info-kind=line-tables-only -O2 -emit-obj -o t.obj t.cpp
$ lld-link -debug -entry:main -pdb:t.pdb t.obj
$ llvm-symbolizer --obj=t.exe --relative-address 0x1001 0x1018
Test(int)::(anonymous class)::operator()
C:\src\tests\sbox-integration\small-repro\t.cpp:5:0
uselambda1
C:\src\tests\sbox-integration\small-repro\t.cpp:1:0
Test(int)??:0:0
Test(int)::(anonymous class)::operator()
C:\src\tests\sbox-integration\small-repro\t.cpp:5:0
uselambda2
C:\src\tests\sbox-integration\small-repro\t.cpp:2:0
Test(int)
??:0:0
A dump of the inline line table shows that there are two functions with the
func id 0x1001.
Inlinee Lines
Mod | `C:\src\tests\t.obj`:
Inlinee | Line | Source File
0x1000 | 1 | C:\src\tests\t.cpp (MD5: 4A4CBE958FA977B1C4A844AA292CF8C3)
0x1001 | 5 | C:\src\tests\t.cpp (MD5: 4A4CBE958FA977B1C4A844AA292CF8C3)
0x1002 | 2 | C:\src\tests\t.cpp (MD5: 4A4CBE958FA977B1C4A844AA292CF8C3)
0x1001 | 6 | C:\src\tests\t.cpp (MD5: 4A4CBE958FA977B1C4A844AA292CF8C3)
Mod 0001 | `* Linker *`:
(side note: there should be a line number for `Test(int)` in the symbolizer
output -- this is an unrelated bug in llvm-symbolizer)
--
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 48433] New: Crash on "help memory read"
https://bugs.llvm.org/show_bug.cgi?id=48433 Bug ID: 48433 Summary: Crash on "help memory read" Product: lldb Version: unspecified Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: All Bugs Assignee: lldb-...@lists.llvm.org Reporter: kparz...@quicinc.com CC: jdevliegh...@apple.com, llvm-bugs@lists.llvm.org The command "help memory read" causes a crash. No other action is required, load lldb and ask for help about "memory read". $ lldb (lldb) help memory read PLEASE submit a bug report to https://bugs.llvm.org/ and include the crash backtrace. Stack dump: 0. Program arguments: /w/c/org/bin/lldb #0 0x0042cdc3 llvm::sys::PrintStackTrace(llvm::raw_ostream&, int) (/w/c/org/bin/lldb+0x42cdc3) #1 0x0042b07e llvm::sys::RunSignalHandlers() (/w/c/org/bin/lldb+0x42b07e) #2 0x0042d405 SignalHandler(int) (/w/c/org/bin/lldb+0x42d405) #3 0x7f78efde6890 __restore_rt (/lib/x86_64-linux-gnu/libpthread.so.0+0x12890) #4 0x7f78e8980c70 lldb_private::Options::GenerateOptionUsage(lldb_private::Stream&, lldb_private::CommandObject*, unsigned int) (/w/c/org/bin/../lib/liblldb.so.12git+0x1000c70) #5 0x7f78e896d8eb lldb_private::CommandObject::GenerateHelpText(lldb_private::Stream&) (/w/c/org/bin/../lib/liblldb.so.12git+0xfed8eb) #6 0x7f78e896d75e lldb_private::CommandObject::GenerateHelpText(lldb_private::CommandReturnObject&) (/w/c/org/bin/../lib/liblldb.so.12git+0xfed75e) #7 0x7f78ea2ac4be lldb_private::CommandObjectHelp::DoExecute(lldb_private::Args&, lldb_private::CommandReturnObject&) (/w/c/org/bin/../lib/liblldb.so.12git+0x292c4be) #8 0x7f78e896e02c lldb_private::CommandObjectParsed::Execute(char const*, lldb_private::CommandReturnObject&) (/w/c/org/bin/../lib/liblldb.so.12git+0xfee02c) #9 0x7f78e8964b4c lldb_private::CommandInterpreter::HandleCommand(char const*, lldb_private::LazyBool, lldb_private::CommandReturnObject&, lldb_private::ExecutionContext*, bool, bool) (/w/c/org/bin/../lib/liblldb.so.12git+0xfe4b4c) #10 0x7f78e8968253 lldb_private::CommandInterpreter::IOHandlerInputComplete(lldb_private::IOHandler&, std::__1::basic_string, std::__1::allocator >&) (/w/c/org/bin/../lib/liblldb.so.12git+0xfe8253) #11 0x7f78e88d2d9d lldb_private::IOHandlerEditline::Run() (/w/c/org/bin/../lib/liblldb.so.12git+0xf52d9d) #12 0x7f78e88b932d lldb_private::Debugger::RunIOHandlers() (/w/c/org/bin/../lib/liblldb.so.12git+0xf3932d) #13 0x7f78e89695eb lldb_private::CommandInterpreter::RunCommandInterpreter(lldb_private::CommandInterpreterRunOptions&) (/w/c/org/bin/../lib/liblldb.so.12git+0xfe95eb) #14 0x7f78e85bcd49 lldb::SBDebugger::RunCommandInterpreter(bool, bool) (/w/c/org/bin/../lib/liblldb.so.12git+0xc3cd49) #15 0x00409fb6 Driver::MainLoop() (/w/c/org/bin/lldb+0x409fb6) #16 0x0040c215 main (/w/c/org/bin/lldb+0x40c215) #17 0x7f78e62a3b97 __libc_start_main /build/glibc-OTsEL5/glibc-2.27/csu/../csu/libc-start.c:344:0 #18 0x00406cca _start (/w/c/org/bin/lldb+0x406cca) Segmentation fault -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 26082] Invariant store should sink to loop exit
https://bugs.llvm.org/show_bug.cgi?id=26082 Nikita Popov changed: What|Removed |Added CC||nikita@gmail.com Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #12 from Nikita Popov --- BasicAA determines NoAlias and LICM performs promotion on trunk. Presumably because recphi handling was enabled. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 48422] Assertion `SE->DT.dominates(ENT.ExitingBlock, Latch) && "We should only have known counts for exiting blocks that dominate " "latch!"' failed
https://bugs.llvm.org/show_bug.cgi?id=48422 Michael Kruse changed: What|Removed |Added Fixed By Commit(s)||6249bfeefeed7ee2634355d4d75 ||23b46fb00fda6 Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #2 from Michael Kruse --- Should be fixed in 6249bfeefeed7ee2634355d4d7523b46fb00fda6. Thank you for the report. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 48379] aarch64: Some casting/shifting of __uint128_t hits an UNREACHABLE after regalloc in AArch64InstrInfo::copyPhysReg
https://bugs.llvm.org/show_bug.cgi?id=48379 Jessica Paquette changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #4 from Jessica Paquette --- Patch landed in 195a7af0abb26915f962462f69c0f17e3835f78b. Attached IR no longer crashes. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 47800] [meta] 11.0.1 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=47800 Bug 47800 depends on bug 48379, which changed state. Bug 48379 Summary: aarch64: Some casting/shifting of __uint128_t hits an UNREACHABLE after regalloc in AArch64InstrInfo::copyPhysReg https://bugs.llvm.org/show_bug.cgi?id=48379 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 48434] New: attribute instantiation for class template specializations can lead to deserialization cycles
https://bugs.llvm.org/show_bug.cgi?id=48434
Bug ID: 48434
Summary: attribute instantiation for class template
specializations can lead to deserialization cycles
Product: clang
Version: unspecified
Hardware: PC
OS: All
Status: NEW
Severity: enhancement
Priority: P
Component: Modules
Assignee: unassignedclangb...@nondot.org
Reporter: richard-l...@metafoo.co.uk
CC: dgre...@apple.com, llvm-bugs@lists.llvm.org,
richard-l...@metafoo.co.uk
Consider:
```
template struct A;
using X = A;
template struct [[attr(X)]] A {};
X x;
```
Now, deserializing `x` crashes, because it hits a cycle:
* Deserializing `x` reads the TypedefNameDecl `X`
* Deserializing `X` reads its RecordType `A`
* Deserializing `A` reads its attributes
* Deserializing `attr(X)` finds we already have an `X`, so tries to use it
* Using the `X` to form a `TypedefType` crashes, because `X` is not
sufficiently initialized
This is broken because we violated the deserialization invariant by emitting
bitcode for `X` that (indirectly) refers to a lexically-later part of the
program, specifically the attributes for `A`.
To fix this, I think we need to lazily load attributes, at least for template
specializations.
--
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 28410 in oss-fuzz: llvm:llvm-dwarfdump-fuzzer: Null-dereference READ in llvm::raw_ostream::operator<
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevl...@apple.com, igm...@gmail.com, d...@google.com, mit...@google.com, bigch...@gmail.com, eney...@google.com, llvm-...@lists.llvm.org, j...@chromium.org, v...@apple.com, mitch...@outlook.com, xpl...@gmail.com, akils...@apple.com Labels: ClusterFuzz Reproducible Stability-Memory-MemorySanitizer Engine-libfuzzer OS-Linux Proj-llvm Reported-2020-12-08 Type: Bug New issue 28410 by ClusterFuzz-External: llvm:llvm-dwarfdump-fuzzer: Null-dereference READ in llvm::raw_ostream::operator<< https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=28410 Detailed Report: https://oss-fuzz.com/testcase?key=4842450686443520 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: llvm-dwarfdump-fuzzer Job Type: libfuzzer_msan_llvm Platform Id: linux Crash Type: Null-dereference READ Crash Address: 0x Crash State: llvm::raw_ostream::operator<< llvm::DWARFFormValue::dump dumpAttribute Sanitizer: memory (MSAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_msan_llvm&range=202004090442:202004100305 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=4842450686443520 Issue filed automatically. See https://google.github.io/oss-fuzz/advanced-topics/reproducing for instructions to reproduce this bug locally. When you fix this bug, please * mention the fix revision(s). * state whether the bug was a short-lived regression or an old bug in any stable releases. * add any other useful information. This information can help downstream consumers. If you need to contact the OSS-Fuzz team with a question, concern, or any other feedback, please file an issue at https://github.com/google/oss-fuzz/issues. Comments on individual Monorail issues are not monitored. -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 28411 in oss-fuzz: llvm:llvm-isel-fuzzer--x86_64-O2: Use-after-poison in llvm::SelectionDAG::getNode
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevl...@apple.com, igm...@gmail.com, d...@google.com, mit...@google.com, bigch...@gmail.com, eney...@google.com, llvm-...@lists.llvm.org, j...@chromium.org, v...@apple.com, mitch...@outlook.com, xpl...@gmail.com, akils...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible Engine-libfuzzer OS-Linux Proj-llvm Security_Severity-High Reported-2020-12-08 Type: Bug-Security New issue 28411 by ClusterFuzz-External: llvm:llvm-isel-fuzzer--x86_64-O2: Use-after-poison in llvm::SelectionDAG::getNode https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=28411 Detailed Report: https://oss-fuzz.com/testcase?key=4861603086467072 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: llvm-isel-fuzzer--x86_64-O2 Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Use-after-poison READ 2 Crash Address: 0x6214b1aa Crash State: llvm::SelectionDAG::getNode llvm::SelectionDAG::getNode DAGCombiner::visit Sanitizer: address (ASAN) Recommended Security Severity: High Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=202012060612:202012070611 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=4861603086467072 Issue filed automatically. See https://google.github.io/oss-fuzz/advanced-topics/reproducing for instructions to reproduce this bug locally. When you fix this bug, please * mention the fix revision(s). * state whether the bug was a short-lived regression or an old bug in any stable releases. * add any other useful information. This information can help downstream consumers. If you need to contact the OSS-Fuzz team with a question, concern, or any other feedback, please file an issue at https://github.com/google/oss-fuzz/issues. Comments on individual Monorail issues are not monitored. -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 48435] New: [InstCombine] Miscompile (?) of select with poison case
https://bugs.llvm.org/show_bug.cgi?id=48435
Bug ID: 48435
Summary: [InstCombine] Miscompile (?) of select with poison
case
Product: libraries
Version: trunk
Hardware: PC
OS: All
Status: NEW
Severity: enhancement
Priority: P
Component: Scalar Optimizations
Assignee: unassignedb...@nondot.org
Reporter: meh...@google.com
CC: llvm-bugs@lists.llvm.org
I'm not totally sure this is a bug as I don't know the semantics of a select
which has a poison value in the non-selected position. Anyway, the input is
basically a shift followed by select with some other cruft. The select guards
against use of an overshifted value by selecting zero in the case of overshift.
Input:
define i1 @test() local_unnamed_addr {
so_basic:
%x5 = call i32 @f(i32 100)
%ne_42 = icmp ne i32 %x5, 0
%_z3 = zext i32 %x5 to i64
%_z4 = icmp uge i64 %_z3, 64
%_z5 = lshr i64 256, %_z3
%_z6 = trunc i64 %_z5 to i32
%x15 = select i1 %_z4, i32 0, i32 %_z6
%ne_44 = icmp ne i32 %x15, 0
%x18 = or i1 %ne_42, %ne_44
ret i1 %x18
}
define i32 @f(i32 %x) {
ret i32 %x
}
Result of opt -O2:
define i1 @test() local_unnamed_addr #0 {
so_basic:
ret i1 poison
}
Looks like the problematic xform replaces the select(p, false, x) with
and(not(p), x) where x is poison in this case.
Alive:
define i1 @src() {
%0:
%x5 = call i32 @f(i32 100)
%ne_42 = icmp ne i32 %x5, 0
%_z3 = zext i32 %x5 to i64
%_z4 = icmp ugt i32 %x5, 63
%_z5 = lshr i64 256, %_z3
%_z6 = trunc i64 %_z5 to i32
%ne_441 = icmp ne i32 %_z6, 0
%not._z4 = xor i1 %_z4, 1
%ne_44 = and i1 %not._z4, %ne_441
%x18 = or i1 %ne_42, %ne_44
ret i1 %x18
}
=>
define i1 @tgt() {
%0:
ret i1 poison
}
Transformation doesn't verify!
ERROR: Target is more poisonous than source
Example:
Source:
i32 %x5 = #x (0)
i1 %ne_42 = #x0 (0)
i64 %_z3 = #x (0)
i1 %_z4 = #x0 (0)
i64 %_z5 = #x0100 (256)
i32 %_z6 = #x0100 (256)
i1 %ne_441 = #x1 (1)
i1 %not._z4 = #x1 (1)
i1 %ne_44 = #x1 (1)
i1 %x18 = #x1 (1)
SOURCE MEMORY STATE
===
NON-LOCAL BLOCKS:
Block 0 > size: 0 align: 1alloc type: 0
Block 1 > size: 0 align: 2alloc type: 0
Target:
Source value: #x1 (1)
Target value: poison
--
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 9573] Attempt to instantiate invalid nested class declaration crashes clang
https://bugs.llvm.org/show_bug.cgi?id=9573 Faisal Vali changed: What|Removed |Added Status|NEW |RESOLVED CC||fais...@yahoo.com Resolution|--- |FIXED --- Comment #1 from Faisal Vali --- this is an old bug and not reproducible in trunk (and probably not for a while) - so am closing it for now. Thanks! -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 48436] New: Add CSKY backend component
https://bugs.llvm.org/show_bug.cgi?id=48436 Bug ID: 48436 Summary: Add CSKY backend component Product: Bugzilla Admin Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P Component: Products Assignee: unassignedb...@nondot.org Reporter: zixuan...@linux.alibaba.com CC: kristof.be...@gmail.com, llvm-bugs@lists.llvm.org, r...@google.com, t.p.northo...@gmail.com Hi, all. Could anyone please add a new backend component CSKY as https://bugs.llvm.org/show_bug.cgi?id=48199 does for M68K? Thank you! The default CC should be: Zi Xuan Wu . -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 42211] using declaration on method with multiple inheritance disables virtual call to overridden method
https://bugs.llvm.org/show_bug.cgi?id=42211 Faisal Vali changed: What|Removed |Added CC||fais...@yahoo.com Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Fixed By Commit(s)||https://github.com/llvm/llv ||m-project/commit/aade5fbbfe ||f3e8555df202082bea905deebc2 ||ca5 --- Comment #1 from Faisal Vali --- This appears fixed in clang 10 - I believe fixed by this commit: https://github.com/llvm/llvm-project/commit/aade5fbbfef3e8555df202082bea905deebc2ca5 -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 28421 in oss-fuzz: llvm:clang-objc-fuzzer: Stack-overflow in clang::DeclaratorChunk::getFunction
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevl...@apple.com, igm...@gmail.com, d...@google.com, mit...@google.com, bigch...@gmail.com, eney...@google.com, llvm-...@lists.llvm.org, j...@chromium.org, v...@apple.com, mitch...@outlook.com, xpl...@gmail.com, akils...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible Engine-libfuzzer OS-Linux Proj-llvm Reported-2020-12-08 Type: Bug New issue 28421 by ClusterFuzz-External: llvm:clang-objc-fuzzer: Stack-overflow in clang::DeclaratorChunk::getFunction https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=28421 Detailed Report: https://oss-fuzz.com/testcase?key=5895693520732160 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: clang-objc-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Stack-overflow Crash Address: 0x7ffd8c82fea8 Crash State: clang::DeclaratorChunk::getFunction ConvertDeclSpecToType GetDeclSpecTypeForDeclarator Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=202011130615:202011140605 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5895693520732160 Issue filed automatically. See https://google.github.io/oss-fuzz/advanced-topics/reproducing for instructions to reproduce this bug locally. When you fix this bug, please * mention the fix revision(s). * state whether the bug was a short-lived regression or an old bug in any stable releases. * add any other useful information. This information can help downstream consumers. If you need to contact the OSS-Fuzz team with a question, concern, or any other feedback, please file an issue at https://github.com/google/oss-fuzz/issues. Comments on individual Monorail issues are not monitored. -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 48437] New: [flang] Flang can't evaluate constant arrays with lower bounds <= 0
https://bugs.llvm.org/show_bug.cgi?id=48437 Bug ID: 48437 Summary: [flang] Flang can't evaluate constant arrays with lower bounds <= 0 Product: flang Version: trunk Hardware: PC OS: Windows NT Status: NEW Severity: release blocker Priority: P Component: Frontend Assignee: unassignedb...@nondot.org Reporter: chinoune.me...@hotmail.com CC: david.tr...@arm.com, jper...@nvidia.com, kirankuma...@gmail.com, llvm-bugs@lists.llvm.org, sscalp...@nvidia.com Reproducer: module m implicit none real, parameter :: a(-1:-1) = [ 1. ], b(-1:-1) = log(a) end module m $ f18 -c bug.f90 fatal internal error: CHECK(j >= lb && j < lb + extent) failed at ***/llvm-project/flang/lib/Evaluate/constant.cpp(51) -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 45605] [flang][MSVC] Compilation errors with MSVC 2019.
https://bugs.llvm.org/show_bug.cgi?id=45605 مهدي شينون (Mehdi Chinoune) changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
