[llvm-bugs] [Bug 51410] New: Incorrect optimization results cause branch redirection errors.
https://bugs.llvm.org/show_bug.cgi?id=51410
Bug ID: 51410
Summary: Incorrect optimization results cause branch
redirection errors.
Product: clang
Version: trunk
Hardware: PC
OS: Windows NT
Status: NEW
Severity: enhancement
Priority: P
Component: C
Assignee: unassignedclangb...@nondot.org
Reporter: 2077213...@qq.com
CC: blitzrak...@gmail.com, dgre...@apple.com,
erik.pilking...@gmail.com, llvm-bugs@lists.llvm.org,
richard-l...@metafoo.co.uk
I have the following test case. The problem occurs on the ARM platform. It
seems that the problem is caused by Clang optimization. I expected to enter the
return 1 branch of the foo function, but actually enter return 0, which is
normal only when O2 optimization occurs.
clang --target=arm-none-eabi -O2 test.c
#include
typedef struct {
void *pPtAddr;
unsigned int uwPtSize;
} Node;
unsigned int foo(unsigned int ucPtNo, Node *para) {
char *pcPtEnd;
pcPtEnd = (char *)para->pPtAddr + para->uwPtSize;
if ((unsigned int)para->pPtAddr >= (unsigned int)pcPtEnd) {
return 1;
}
printf("unexcetion print %p %p\n", para->pPtAddr, pcPtEnd);
return 0;
}
int main() {
Node para;
para.pPtAddr = (void *)0x;
para.uwPtSize = 0xfff;
int res = foo(32, ¶);
printf("%d\n", res);
return 0;
}
--
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 50618] Binary inconsistency problems with occasional precedence
https://bugs.llvm.org/show_bug.cgi?id=50618 Arron <2077213...@qq.com> 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 51411] New: Semantic error - - different output are observed on changing flags
https://bugs.llvm.org/show_bug.cgi?id=51411
Bug ID: 51411
Summary: Semantic error - - different output are observed on
changing flags
Product: new-bugs
Version: 12.0
Hardware: PC
OS: Linux
Status: NEW
Severity: release blocker
Priority: P
Component: new bugs
Assignee: unassignedb...@nondot.org
Reporter: rohit.aggar...@amd.com
CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org
The issue is present in main stream LLVM. I tired the example code on clang-12
release.
## Sample Code (inline_ex.c)
int main() {
double dbl;
unsigned i[1000], j[1000], k[1000], l[1000];
int index;
for (index = 0; index < 1000; index++) {
i[index] = j[index] = k[index] = l[index] = 1;
}
unsigned long r1=0, r2=0, r3=0, r4=0;
for (int a = 0; a < 1000; a++) {
r1 += i[a];
r2 += j[a];
r3 += k[a];
r4 += l[a];
}
double R1 = DBL_MAX + (double)r1;
double R2 = DBL_MAX + (double)r2;
double R3 = DBL_MAX + (double)r3;
double R4 = DBL_MAX + (double)r4;
// printf("%lf\n%lf\n%lf\n%lf\n", R1, R2, R3, R4);
dbl = R1 + R2 + R3 + R4;
printf("Result: %lf\n", dbl);
return 0;
}
## GCC
(gcc inline_ex.c -o a.out && ./a.out )
Result: inf
(gcc inline_ex.c -O3 -ffast-math -o a.out && ./a.out )
Result: inf
## CLANG 12
clang-12 -O3 -flto -ffast-math -fno-unroll-loops inline_ex.c -o a.out &&
./a.out )
Result: 0.00
(clang-12 -O3 -ffast-math inline_ex.c -o a.out && ./a.out )
Result: 0.00
(clang-12 -O3 -flto -fno-unroll-loops inline_ex.c -o a.out && ./a.out )
Result: inf
(clang-12 -O3 inline_ex.c -o a.out && ./a.out )
Result: inf
(clang-12 inline_ex.c -o a.out && ./a.out )
Result: inf
Observation
The problem occurs when we use fast-math flag with O3. This flag enables
certain transformation in instCombine pass which leads to creation of poison
value. The poison value is not handle properly and is propagated to it's uses.
In the end, a poison value remains as the operand in printf. The value of
poison depends upon type and for double the value is 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 51411] Semantic error - - different output are observed on changing flags
https://bugs.llvm.org/show_bug.cgi?id=51411 Roman Lebedev changed: What|Removed |Added Resolution|--- |INVALID Status|NEW |RESOLVED CC||lebedev...@gmail.com, ||sca...@apple.com --- Comment #1 from Roman Lebedev --- This seems to be working as intended. `-ffast-math` implies `-fno-honor-infinities`, which specifies that the result of an FP computation can not be inf, so naturally, if you were expecting to end up with an inf, that's UB. -- 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 51412] New: [clang-format] AlignConsecutiveMacros fights with Visual Studio and resource.h
https://bugs.llvm.org/show_bug.cgi?id=51412
Bug ID: 51412
Summary: [clang-format] AlignConsecutiveMacros fights with
Visual Studio and resource.h
Product: clang
Version: unspecified
Hardware: PC
OS: Windows NT
Status: NEW
Severity: enhancement
Priority: P
Component: Formatter
Assignee: unassignedclangb...@nondot.org
Reporter: mydeveloper...@gmail.com
CC: djas...@google.com, kli...@google.com,
llvm-bugs@lists.llvm.org
clang-format AlignConsecutiveMacros feature is excellent, but it causes real
problems when using the resource editor in Visual Studio
A resource.h file will be "Align" with an alignment of 40
//{{NO_DEPENDENCIES}}
// Microsoft Visual C++ generated include file.
// Used by MyTest.rc
//
#define IDP_OLE_INIT_FAILED 100
#define IDP_FAILED_TO_CREATE102
#define ID_STATUSBAR_SHOW 108
#define ID_STATUSBAR_TEXT 109
if it encounters a long symbol it will push it out
#define ID_VERYVERYVERYVERY_LONG_LONG_LONG_LONG_RESOURCE 33221
Every time we make a change in the resource editor in visual studio the
resource.h will be written out (and its not auto clang-formatted)
If you check all files for "clang-formatting" then resource.h will fail
everytime
It would be good to have some AlignConsecutiveMacros options so that
clang-format didn't fight against this format
Some sort of "AlignConsecutiveMacrosMinMaxAlignment: 40"
--
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 51336] clang_other_error_1dNytc.ii
https://bugs.llvm.org/show_bug.cgi?id=51336 Judzinsky, Nils changed: What|Removed |Added Resolution|--- |INVALID 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
[llvm-bugs] [Bug 51413] New: the C API for the dwarf debug info does not allow to link a global variable to a DI compilation unit
https://bugs.llvm.org/show_bug.cgi?id=51413 Bug ID: 51413 Summary: the C API for the dwarf debug info does not allow to link a global variable to a DI compilation unit Product: libraries Version: 11.0 Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: Support Libraries Assignee: unassignedb...@nondot.org Reporter: b2.t...@gmx.com CC: llvm-bugs@lists.llvm.org -- 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 30808 in oss-fuzz: llvm:clang-fuzzer: Stack-overflow in llvm::detail::IEEEFloat::roundSignificandWithExponent
Updates: Status: WontFix Comment #1 on issue 30808 by ClusterFuzz-External: llvm:clang-fuzzer: Stack-overflow in llvm::detail::IEEEFloat::roundSignificandWithExponent https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=30808#c1 ClusterFuzz testcase 4644764815327232 is closed as invalid, so closing issue. -- 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 51414] New: Exporting nested classes doesn't compile and link with Clang on Windows
https://bugs.llvm.org/show_bug.cgi?id=51414
Bug ID: 51414
Summary: Exporting nested classes doesn't compile and link with
Clang on Windows
Product: clang
Version: 12.0
Hardware: PC
OS: Windows NT
Status: NEW
Severity: enhancement
Priority: P
Component: -New Bugs
Assignee: unassignedclangb...@nondot.org
Reporter: peterghos...@gmail.com
CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org,
neeil...@live.com, richard-l...@metafoo.co.uk
The following code won't compile and link using `clang-cl /std:c++17 test.cpp`.
#include
#include
#include
#include
#define EXPORT_OUTER __declspec(dllexport)
#define EXPORT_INNER __declspec(dllexport)
class EXPORT_OUTER A
{
public:
class EXPORT_INNER B
{
public:
B(
const std::optional> &opt =
std::nullopt)
{
}
};
};
int main()
{
auto b = A::B();
return 0;
}
Error:
test-e1dae6.obj: error LNK2019: Unresolved external symbol "public: __cdecl
std::optional,class std:: allocator >,class std::allocator,class
std::allocator>>> >::~optional,class std::allocator
>,class std::allocator,class std::allocator>>> >(void)"
(??1?$optional@V?$vector@V?$basic_string@DU?$char_traits@D@std@@V?$allocator
@D@2@@std@@V?$allocator@V?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@@2@@std@@@
std@@QEAA@XZ), the symbol is referenced in the function main
test.exe: fatal error LNK1120: 1 unresolved external command
clang-cl: error: linker command failed with exit code 1120 (use -v to see
invocation)
However, the same code compiles and links if
1. using cl.exe from MSVC
2. using `#define EXPORT_INNER` instead
3. removing the default value of `opt` in the ctor of the class B and passing
in `std::nullopt` explicitly
--
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 36984 in oss-fuzz: llvm:clang-fuzzer: Stack-overflow in clang::Sema::SemaDiagnosticBuilder::SemaDiagnosticBuilder
Updates: Status: WontFix Comment #1 on issue 36984 by ClusterFuzz-External: llvm:clang-fuzzer: Stack-overflow in clang::Sema::SemaDiagnosticBuilder::SemaDiagnosticBuilder https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=36984#c1 ClusterFuzz testcase 5809697134346240 is closed as invalid, so closing issue. -- 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 36933 in oss-fuzz: llvm:clang-fuzzer: Stack-overflow in clang::Sema::getPrintingPolicy
Updates: Status: WontFix Comment #1 on issue 36933 by ClusterFuzz-External: llvm:clang-fuzzer: Stack-overflow in clang::Sema::getPrintingPolicy https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=36933#c1 ClusterFuzz testcase 6122345604448256 is closed as invalid, so closing issue. -- 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 36997 in oss-fuzz: llvm:clang-fuzzer: Stack-overflow in llvm::detail::IEEEFloat::convertFromStringSpecials
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-2021-08-09 Type: Bug New issue 36997 by ClusterFuzz-External: llvm:clang-fuzzer: Stack-overflow in llvm::detail::IEEEFloat::convertFromStringSpecials https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=36997 Detailed Report: https://oss-fuzz.com/testcase?key=4532132386045952 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: clang-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Stack-overflow Crash Address: 0x7fffcf796ed8 Crash State: llvm::detail::IEEEFloat::convertFromStringSpecials llvm::detail::IEEEFloat::convertFromString llvm::APFloat::convertFromString Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=202107290602:202107300611 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=4532132386045952 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 51415] New: [AArch64][SVE] Merge 73ecb9987b00db274b7b2ac34b0602ffdb906a4b into LLVM 13.0.0
https://bugs.llvm.org/show_bug.cgi?id=51415 Bug ID: 51415 Summary: [AArch64][SVE] Merge 73ecb9987b00db274b7b2ac34b0602ffdb906a4b into LLVM 13.0.0 Product: libraries Version: trunk Hardware: All OS: All Status: NEW Severity: release blocker Priority: P Component: Backend: AArch64 Assignee: unassignedb...@nondot.org Reporter: bradley.sm...@arm.com CC: arnaud.degrandmai...@arm.com, llvm-bugs@lists.llvm.org, smithp...@googlemail.com, ties.st...@arm.com Blocks: 51236 Please merge 73ecb9987b00db274b7b2ac34b0602ffdb906a4b (https://reviews.llvm.org/D107576) into the LLVM 13 release branch. This fixes an assertion failure when lowering fixed length SVE gather/scatter nodes with 32-bit offsets and 64-bit results. Referenced Bugs: https://bugs.llvm.org/show_bug.cgi?id=51236 [Bug 51236] [meta] 13.0.0 Release Blockers -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 51416] New: clang musttail crash on arm32
https://bugs.llvm.org/show_bug.cgi?id=51416
Bug ID: 51416
Summary: clang musttail crash on arm32
Product: clang
Version: unspecified
Hardware: PC
OS: All
Status: NEW
Severity: enhancement
Priority: P
Component: -New Bugs
Assignee: unassignedclangb...@nondot.org
Reporter: manojgu...@google.com
CC: htmldevelo...@gmail.com, lloz...@chromium.org,
llvm-bugs@lists.llvm.org, manojgu...@google.com,
neeil...@live.com, richard-l...@metafoo.co.uk
A new feture in clang [[msuttail]] is causing clang to cash on our internal
builds.
Reduced test case:
typedef long a;
typedef short b;
typedef long long c;
class d;
class e;
struct f {};
struct g;
class h {
public:
enum i { j };
};
template struct k : h {
static char *l(d *, const char *, e *, const g *, c, f);
template
static const char *m(d *, const char *, e *, const g *, c, f);
};
template
template
const char *k::m(d *o, const char *p, e *p3, const g *q, c r, f s) {
[[clang::musttail]] return l(o, p, p3, q, r, s);
}
template const char *k<1>::m(d *, const char *, e *, const g *, c,
f);
clang++ -target armv7a-linux-gnueabihf -mfpu=neon tctable_lite.cpp -c
fatal error: error in backend: failed to perform tail call elimination on a
call site marked musttail
PLEASE submit a bug report to https://crbug.com and run
tools/clang/scripts/process_crashreports.py (only works inside Google) which
will upload a report and include the crash backtrace, preprocessed source, and
associated run script.
Stack dump:
0. Program arguments:
/usr/local/google/home/manojgupta/chromeclang/third_party/llvm-build/Release+Asserts/bin/clang++
-target armv7a-linux-gnueabihf -mfpu=neon
generated_message_tctable_lite-b3fd7e.cpp -c
1. parser at end of file
2. Code generation
3. Running pass 'Function Pass Manager' on module
'generated_message_tctable_lite-b3fd7e.cpp'.
4. Running pass 'ARM Instruction Selection' on function
'@_ZN1kILj1EE1mIlsLN1h1iE0EEEPKcP1dS5_P1ePK1gx1f'
#0 0x033130b8
clang: error: clang frontend command failed with exit code 70 (use -v to see
invocation)
clang version 14.0.0 (https://github.com/llvm/llvm-project/
7d9d926a1861e2f6876943d47f297e2a08a57392)
Target: armv7a-unknown-linux-gnueabihf
Still repros on ToT.
--
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 51395] Clang error "file not found" on include files when building with modules
https://bugs.llvm.org/show_bug.cgi?id=51395 Amy Huang changed: What|Removed |Added Resolution|--- |DUPLICATE Status|NEW |RESOLVED --- Comment #2 from Amy Huang --- Yep, I think it's the same, marking as duplicate *** This bug has been marked as a duplicate of bug 47209 *** -- 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 51417] New: HowToUseLLJIT example doesn't find targets for this triple.
https://bugs.llvm.org/show_bug.cgi?id=51417 Bug ID: 51417 Summary: HowToUseLLJIT example doesn't find targets for this triple. Product: libraries Version: trunk Hardware: PC OS: Windows NT Status: NEW Severity: normal Priority: P Component: OrcJIT Assignee: unassignedb...@nondot.org Reporter: bisslit.1...@gmail.com CC: 1101.deb...@gmail.com, llvm-bugs@lists.llvm.org Trying to run the "HowToUseLLJIT" project results in the message: "Unable to find target for this triple (no targets are registered)". I have been trying to find information on this but I have been unable to find a fix or the reason this happens. Moreover, If i add "InitializeAllTargetInfos();" it results in: "No available targets are compatible with triple 'x86_64-pc-windows-msvc'". I'm using Visual Studio 2019 to compile my project. -- 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 37000 in oss-fuzz: llvm:clang-objc-fuzzer: Stack-overflow in GetFullTypeForDeclarator
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-2021-08-09 Type: Bug New issue 37000 by ClusterFuzz-External: llvm:clang-objc-fuzzer: Stack-overflow in GetFullTypeForDeclarator https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=37000 Detailed Report: https://oss-fuzz.com/testcase?key=4646792821080064 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: clang-objc-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Stack-overflow Crash Address: 0x7fff57a72e20 Crash State: GetFullTypeForDeclarator clang::Sema::GetTypeForDeclarator clang::Sema::ActOnBlockArguments Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=202107230602:202107240617 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=4646792821080064 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 51418] New: Please backport 15cacab73f7e36d9dca4a5516ccb360b67bf2dbc (skip test if LD_PRELOAD) to 13.x
https://bugs.llvm.org/show_bug.cgi?id=51418 Bug ID: 51418 Summary: Please backport 15cacab73f7e36d9dca4a5516ccb360b67bf2dbc (skip test if LD_PRELOAD) to 13.x Product: lldb Version: unspecified Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: All Bugs Assignee: lldb-...@lists.llvm.org Reporter: mgo...@gentoo.org CC: jdevliegh...@apple.com, llvm-bugs@lists.llvm.org Blocks: 51236 commit 15cacab73f7e36d9dca4a5516ccb360b67bf2dbc Author: Michał Górny Date: 2021-08-07 22:44:19 +0200 [lldb] [test] Skip Expr/nodefaultlib.cpp test if LD_PRELOAD Is used Some LD_PRELOAD-ed libraries tend to interact badly with --nodefaultlib, particularly Gentoo sandbox. Do not run this test if LD_PRELOAD is present in the running environment. Differential Revision: https://reviews.llvm.org/D107701 Referenced Bugs: https://bugs.llvm.org/show_bug.cgi?id=51236 [Bug 51236] [meta] 13.0.0 Release Blockers -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 51419] New: [InstCombine] Infinite loop in InstCombine on smax+cmp+select sequence
https://bugs.llvm.org/show_bug.cgi?id=51419
Bug ID: 51419
Summary: [InstCombine] Infinite loop in InstCombine on
smax+cmp+select sequence
Product: new-bugs
Version: trunk
Hardware: PC
OS: All
Status: NEW
Severity: normal
Priority: P
Component: new bugs
Assignee: unassignedb...@nondot.org
Reporter: cameron.mcina...@nyu.edu
CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org,
spatel+l...@rotateright.com
The following test case is tripping an infinite loop in InstCombine. I've been
unable to track down the root cause yet.
This issue was found in release/13.x, but Godbolt shows it failing in trunk as
well.
https://godbolt.org/z/xKasbGheK
; RUN: opt -O3 -instcombine -S < %s
define i64 @infloop(double %d, i64 %a) {
%1 = fptosi double %d to i32
%2 = call i32 @llvm.smax.i32(i32 %1, i32 0)
%3 = icmp slt i32 %2, 2
%4 = zext i1 %3 to i32
%5 = select i1 %3, i32 %2, i32 1
%6 = zext i32 %5 to i64
%7 = mul i64 %6, 4
%8 = add i64 %a, %7
ret i64 %8
}
--
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 51421] New: LLVM libc fails to build in 13.0-rc1
https://bugs.llvm.org/show_bug.cgi?id=51421 Bug ID: 51421 Summary: LLVM libc fails to build in 13.0-rc1 Product: new-bugs Version: unspecified Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: new bugs Assignee: unassignedb...@nondot.org Reporter: b...@lindev.ch CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org Building LLVM 13.0-rc1 with libc enabled results in FAILED: projects/libc/src/math/x86_64/CMakeFiles/libc.src.math.x86_64.cos.dir/cos.cpp.o /usr/bin/clang++ -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -I/home/bero/abf/llvm/BUILD/llvm-project-release-13.x/build/projects/libc/src/math/x86_64 -I/home/bero/abf/llvm/BUILD/llvm-project-release-13.x/libc/src/math/x86_64 -I/home/bero/abf/llvm/BUILD/llvm-project-release-13.x/build/include -I/home/bero/abf/llvm/BUILD/llvm-project-release-13.x/llvm/include -I/home/bero/abf/llvm/BUILD/llvm-project-release-13.x/build/projects/libc/include -I/home/bero/abf/llvm/BUILD/llvm-project-release-13.x/libc -I/home/bero/abf/llvm/BUILD/llvm-project-release-13.x/build/projects/libc -Os -fomit-frame-pointer -g3 -gdwarf-4 -Wstrict-aliasing=2 -pipe -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -fstack-protector-all --param=ssp-buffer-size=4 -O3 -march=znver1 -mtune=znver1 -mmmx -msse -msse2 -mssse3 -msse4a -msse4.1 -msse4.2 -mavx -mavx2 -msha -maes -mclflushopt -mfsgsbase -mrdrnd -mfma -mrdseed -mpopcnt -madx -mbmi -mbmi2 -mfxsr -mxsave -mxsaveopt -mxsavec -mxsaves -mmwaitx -mclzero -mfpmath=sse -O3 -fpic -fno-semantic-interposition -Wl,-Bsymbolic -fvisibility-inlines-hidden -Wall -Wextra -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wmissing-field-initializers -pedantic -Wno-long-long -Wno-noexcept-type -Wnon-virtual-dtor -Wsuggest-override -Wno-comment -fdiagnostics-color -Os -fomit-frame-pointer -g3 -gdwarf-4 -Wstrict-aliasing=2 -pipe -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -fstack-protector-all --param=ssp-buffer-size=4 -O3 -march=znver1 -mtune=znver1 -mmmx -msse -msse2 -mssse3 -msse4a -msse4.1 -msse4.2 -mavx -mavx2 -msha -maes -mclflushopt -mfsgsbase -mrdrnd -mfma -mrdseed -mpopcnt -madx -mbmi -mbmi2 -mfxsr -mxsave -mxsaveopt -mxsavec -mxsaves -mmwaitx -mclzero -mfpmath=sse -O3 -fpic -fno-semantic-interposition -Wl,-Bsymbolic -O2 -fpie -ffreestanding -DLLVM_LIBC_PUBLIC_PACKAGING -std=c++14 -MD -MT projects/libc/src/math/x86_64/CMakeFiles/libc.src.math.x86_64.cos.dir/cos.cpp.o -MF projects/libc/src/math/x86_64/CMakeFiles/libc.src.math.x86_64.cos.dir/cos.cpp.o.d -o projects/libc/src/math/x86_64/CMakeFiles/libc.src.math.x86_64.cos.dir/cos.cpp.o -c /home/bero/abf/llvm/BUILD/llvm-project-release-13.x/libc/src/math/x86_64/cos.cpp clang-12: warning: -Wl,-Bsymbolic: 'linker' input unused [-Wunused-command-line-argument] clang-12: warning: -Wl,-Bsymbolic: 'linker' input unused [-Wunused-command-line-argument] clang++: /builddir/build/BUILD/llvm-project-release-12.x/llvm/lib/Target/X86/X86FloatingPoint.cpp:1604: void (anonymous namespace)::FPS::handleSpecialFP(MachineBasicBlock::iterator &): Assertion `(1 << getFPReg(MI.getOperand(I)) & STDefs) == 0 && "Operands with constraint \"f\" cannot overlap with defs"' failed. PLEASE submit a bug report to https://bugs.llvm.org/ and include the crash backtrace, preprocessed source, and associated run script. Stack dump: 0. Program arguments: /usr/bin/clang++ -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -I/home/bero/abf/llvm/BUILD/llvm-project-release-13.x/build/projects/libc/src/math/x86_64 -I/home/bero/abf/llvm/BUILD/llvm-project-release-13.x/libc/src/math/x86_64 -I/home/bero/abf/llvm/BUILD/llvm-project-release-13.x/build/include -I/home/bero/abf/llvm/BUILD/llvm-project-release-13.x/llvm/include -I/home/bero/abf/llvm/BUILD/llvm-project-release-13.x/build/projects/libc/include -I/home/bero/abf/llvm/BUILD/llvm-project-release-13.x/libc -I/home/bero/abf/llvm/BUILD/llvm-project-release-13.x/build/projects/libc -Os -fomit-frame-pointer -g3 -gdwarf-4 -Wstrict-aliasing=2 -pipe -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -fstack-protector-all --param=ssp-buffer-size=4 -O3 -march=znver1 -mtune=znver1 -mmmx -msse -msse2 -mssse3 -msse4a -msse4.1 -msse4.2 -mavx -mavx2 -msha -maes -mclflushopt -mfsgsbase -mrdrnd -mfma -mrdseed -mpopcnt -madx -mbmi -mbmi2 -mfxsr -mxsave -mxsaveopt -mxsavec -mxsaves -mmwaitx -mclzero -mfpmath=sse -O3 -fpic -fno-semantic-interposition -Wl,-Bsymbolic -fvisibility-inlines-hidden -Wall -Wextra -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wmissing-field-initializers -pedantic -Wno-long-long -Wno-noexcept-type -Wnon-virtual-dtor -Wsuggest-override -Wno-comment -fdiagnostics-color -Os -fomit-frame-pointer -g3 -gdwarf-4 -Wstrict-aliasing=2 -pipe -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -fstack-protector-all --pa
[llvm-bugs] [Bug 51422] New: support --fix-v4bx
https://bugs.llvm.org/show_bug.cgi?id=51422 Bug ID: 51422 Summary: support --fix-v4bx Product: lld Version: unspecified Hardware: PC OS: All Status: NEW Severity: enhancement Priority: P Component: ELF Assignee: unassignedb...@nondot.org Reporter: ndesaulni...@google.com CC: a...@linaro.org, llvm-bugs@lists.llvm.org, natechancel...@gmail.com, smithp...@googlemail.com Blocks: 4068 In order to link armv4 Linux kernel images with LLD, it's required that LLD support --fix-v4bx, otherwise we get the warning: >> ld.lld: warning: lld uses blx instruction, no object with architecture >> supporting feature detected IIUC, there's even a relocation type for this: R_ARM_V4BX. https://github.com/ClangBuiltLinux/linux/issues/964 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 51423] New: Please backport 614c7d03877fd99c2de47429b15be3f00306a3bd (LLVM_LIT_ARGS override) to 13.x
https://bugs.llvm.org/show_bug.cgi?id=51423 Bug ID: 51423 Summary: Please backport 614c7d03877fd99c2de47429b15be3f00306a3bd (LLVM_LIT_ARGS override) to 13.x Product: lldb Version: unspecified Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: All Bugs Assignee: lldb-...@lists.llvm.org Reporter: mgo...@gentoo.org CC: jdevliegh...@apple.com, llvm-bugs@lists.llvm.org Blocks: 51236 commit 614c7d03877fd99c2de47429b15be3f00306a3bd Author: Michał Górny Date: 2021-08-07 22:06:20 +0200 [lldb] [cmake] Add LLVM_LIT_ARGS override support for standalone builds Add a LLVM_LIT_ARGS cached variable in order to make it possible to override lit arguments when doing standalone builds. Without that, the user variable is ignored and the default options are always used. Based on a similar solution found in clang. Differential Revision: https://reviews.llvm.org/D107700 Referenced Bugs: https://bugs.llvm.org/show_bug.cgi?id=51236 [Bug 51236] [meta] 13.0.0 Release Blockers -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 51424] New: [no_unique_address] Member not stored in previous member's padding
https://bugs.llvm.org/show_bug.cgi?id=51424 Bug ID: 51424 Summary: [no_unique_address] Member not stored in previous member's padding Product: clang Version: trunk Hardware: PC OS: All Status: NEW Severity: enhancement Priority: P Component: C++2a Assignee: unassignedclangb...@nondot.org Reporter: z.zoel...@gmail.com CC: blitzrak...@gmail.com, erik.pilking...@gmail.com, llvm-bugs@lists.llvm.org, richard-l...@metafoo.co.uk It seems like a missed optimization not to store members in a previous member's padding when the previous member is marked as `[[no_unique_address]]`. GCC implements this. The difference in codegen can be seen here: https://godbolt.org/z/zGs97xKG7 -- 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 37004 in oss-fuzz: llvm:clang-objc-fuzzer: Stack-overflow in llvm::FoldingSetNodeID::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 Stability-Memory-AddressSanitizer Reproducible Engine-libfuzzer OS-Linux Proj-llvm Reported-2021-08-09 Type: Bug New issue 37004 by ClusterFuzz-External: llvm:clang-objc-fuzzer: Stack-overflow in llvm::FoldingSetNodeID::operator== https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=37004 Detailed Report: https://oss-fuzz.com/testcase?key=6487107823599616 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: clang-objc-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Stack-overflow Crash Address: 0x7ffe1c849e28 Crash State: llvm::FoldingSetNodeID::operator== llvm::FoldingSetBase::FindNodeOrInsertPos clang::ASTContext::getFunctionNoProtoType Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=202103170627:202103180603 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=6487107823599616 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 51425] New: Cannot build lld 13 with gcc 6.5.0
https://bugs.llvm.org/show_bug.cgi?id=51425
Bug ID: 51425
Summary: Cannot build lld 13 with gcc 6.5.0
Product: lld
Version: unspecified
Hardware: PC
OS: All
Status: NEW
Severity: enhancement
Priority: P
Component: All Bugs
Assignee: unassignedb...@nondot.org
Reporter: romain.geiss...@amadeus.com
CC: llvm-bugs@lists.llvm.org, smithp...@googlemail.com
Hi,
I am trying to build llvm from branch release/13.x, including lld. It fails
with this error:
[2881/2906] Building CXX object
tools/lld/wasm/CMakeFiles/lldWasm.dir/Writer.cpp.o
FAILED: tools/lld/wasm/CMakeFiles/lldWasm.dir/Writer.cpp.o
/opt/1A/toolchain/x86_64-2.6.32-v3.0.108/bin/g++ -DGTEST_HAS_RTTI=0
-D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS
-D__STDC_LIMIT_MACROS -Itools/lld/wasm -I/workdir/src/llvm-13.0.0/lld/wasm
-I/workdir/src/llvm-13.0.0/lld/include -Itools/lld/include -Iinclude
-I/workdir/src/llvm-13.0.0/llvm/include -O2 -msse -msse2 -msse3
-I/workdir/build/final-system/llvm-temporary-static-dependencies/install/include
-I/workdir/build/final-system/llvm-temporary-static-dependencies/install/include/ncursesw
-fPIC -fno-semantic-interposition -fvisibility-inlines-hidden -Werror=date-time
-Wall -Wextra -Wno-unused-parameter -Wwrite-strings -Wcast-qual
-Wno-missing-field-initializers -pedantic -Wno-long-long
-Wno-maybe-uninitialized -Wdelete-non-virtual-dtor -Wno-comment
-Wmisleading-indentation -fdiagnostics-color -ffunction-sections
-fdata-sections -O3 -DNDEBUG -fno-exceptions -fno-rtti -std=c++14 -MD -MT
tools/lld/wasm/CMakeFiles/lldWasm.dir/Writer.cpp.o -MF
tools/lld/wasm/CMakeFiles/lldWasm.dir/Writer.cpp.o.d -o
tools/lld/wasm/CMakeFiles/lldWasm.dir/Writer.cpp.o -c
/workdir/src/llvm-13.0.0/lld/wasm/Writer.cpp
In file included from /workdir/src/llvm-13.0.0/lld/wasm/Writer.cpp:18:0:
/workdir/src/llvm-13.0.0/lld/wasm/SyntheticSections.h:134:36: error:
specialization of 'template struct llvm::DenseMapInfo' in different
namespace [-fpermissive]
template struct llvm::DenseMapInfo> {
^
In file included from /workdir/src/llvm-13.0.0/lld/wasm/Config.h:12:0,
from /workdir/src/llvm-13.0.0/lld/wasm/Writer.cpp:10:
/workdir/src/llvm-13.0.0/llvm/include/llvm/ADT/StringRef.h:38:32: error: from
definition of 'template struct llvm::DenseMapInfo' [-fpermissive]
template struct DenseMapInfo;
^~~~
while it works with gcc 8, 9 and 11. I suspect that this is because the
specialization is defined with llvm::DenseMapInfo while gcc 6 might expect it
to have it like:
namespace llvm {
template struct DenseMapInfo> {
// ...
}
}
Is it possible to update lld/wasm/SyntheticSections.h in this way ?
Cheers,
Romain
--
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 37007 in oss-fuzz: llvm:clang-fuzzer: Stack-overflow in clang::Sema::EmitCurrentDiagnostic
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-2021-08-10 Type: Bug New issue 37007 by ClusterFuzz-External: llvm:clang-fuzzer: Stack-overflow in clang::Sema::EmitCurrentDiagnostic https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=37007 Detailed Report: https://oss-fuzz.com/testcase?key=5714498580250624 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: clang-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Stack-overflow Crash Address: 0x7fffb98adfa0 Crash State: clang::Sema::EmitCurrentDiagnostic clang::Sema::ImmediateDiagBuilder::~ImmediateDiagBuilder clang::Sema::SemaDiagnosticBuilder::~SemaDiagnosticBuilder Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=202108030618:202108040600 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5714498580250624 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 51296] clang mingw driver -mconsole doesn't override earlier -mwindows
https://bugs.llvm.org/show_bug.cgi?id=51296 Tom Stellard changed: What|Removed |Added Fixed By Commit(s)|ce49fd024b43bd76b149f984b8f |ce49fd024b43bd76b149f984b8f |0d16e92b9bb06 |0d16e92b9bb06 58811fd0f731 Resolution|--- |FIXED Status|REOPENED|RESOLVED --- Comment #4 from Tom Stellard --- Merged: 58811fd0f731 -- 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 51236] [meta] 13.0.0 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=51236 Bug 51236 depends on bug 51296, which changed state. Bug 51296 Summary: clang mingw driver -mconsole doesn't override earlier -mwindows https://bugs.llvm.org/show_bug.cgi?id=51296 What|Removed |Added Status|REOPENED|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 51354] Backport "[LLD] [MinGW] Support both "--opt value" and "--opt=value" for more options" to 13.x
https://bugs.llvm.org/show_bug.cgi?id=51354 Tom Stellard changed: What|Removed |Added Fixed By Commit(s)|b7fb5b54a93099cf3d7ac64f4a9 |b7fb5b54a93099cf3d7ac64f4a9 |5d9942bc2e6a7 |5d9942bc2e6a7 8f24d178691f Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #1 from Tom Stellard --- Merged: 8f24d178691f -- 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 51236] [meta] 13.0.0 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=51236 Bug 51236 depends on bug 51354, which changed state. Bug 51354 Summary: Backport "[LLD] [MinGW] Support both "--opt value" and "--opt=value" for more options" to 13.x https://bugs.llvm.org/show_bug.cgi?id=51354 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 37012 in oss-fuzz: llvm:llvm-opt-fuzzer--x86_64-instcombine: ASSERT: LHS->getType() == RHS->getType() && "Pointer subtraction operand types must matc
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-2021-08-10 Type: Bug New issue 37012 by ClusterFuzz-External: llvm:llvm-opt-fuzzer--x86_64-instcombine: ASSERT: LHS->getType() == RHS->getType() && "Pointer subtraction operand types must matc https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=37012 Detailed Report: https://oss-fuzz.com/testcase?key=5648012973047808 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: llvm-opt-fuzzer--x86_64-instcombine Job Type: libfuzzer_msan_llvm Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: LHS->getType() == RHS->getType() && "Pointer subtraction operand types must matc llvm::IRBuilderBase::CreatePtrDiff llvm::LibCallSimplifier::optimizeSPrintFString Sanitizer: memory (MSAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_msan_llvm&range=202008140614:202008150620 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5648012973047808 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
