[llvm-bugs] [Bug 48347] New: Method metadata emitted twice from synthesised properties targeting GNU Objective-C runtimes
https://bugs.llvm.org/show_bug.cgi?id=48347 Bug ID: 48347 Summary: Method metadata emitted twice from synthesised properties targeting GNU Objective-C runtimes Product: clang Version: 11.0 Hardware: PC OS: All Status: NEW Severity: enhancement Priority: P Component: LLVM Codegen Assignee: unassignedclangb...@nondot.org Reporter: csda...@swan.ac.uk CC: llvm-bugs@lists.llvm.org, neeil...@live.com, richard-l...@metafoo.co.uk Blocks: 47800 The clang AST was refactored to add method nodes for methods synthesised from Objective-C properties but the GNU runtime (ABIv1) code that emitted runtime metadata was not updated so these methods were emitted twice. This was fixed in trunk: d1ed67037de6f3f44dc446784f74f0e02adec9b5 Please can this be added to the 11 point release? 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 48341] C99 code completion for field names in designated initializers used with compound literals
https://bugs.llvm.org/show_bug.cgi?id=48341 Michael Aganier changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED Fixed By Commit(s)||https://reviews.llvm.org/D9 ||2370 -- 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 48348] New: ObjC incorrectly using DWARF exception handling with MinGW-w64 and GNU Objective-C runtime
https://bugs.llvm.org/show_bug.cgi?id=48348 Bug ID: 48348 Summary: ObjC incorrectly using DWARF exception handling with MinGW-w64 and GNU Objective-C runtime Product: clang Version: 11.0 Hardware: PC OS: Windows NT Status: NEW Severity: normal Priority: P Component: -New Bugs Assignee: unassignedclangb...@nondot.org Reporter: frede...@algoriddim.com CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org, neeil...@live.com, richard-l...@metafoo.co.uk Building Objective-C code on Windows using the gnustep-2.0 ObjC runtime in a MinGW-w64 environment and using SEH exception handling incorrectly generates code with DWARF exception handling. ``` $ clang -I/c/GNUstep/x64/include/ -L/c/GNUstep/x64/lib/ -lobjc -fobjc-runtime=gnustep-2.0 -fuse-ld=lld test.m -v clang version 11.0.0 (https://github.com/msys2/MINGW-packages c0083b9edc111315c868f9c53dd60aaa78d1669b) Target: x86_64-w64-windows-gnu Thread model: posix InstalledDir: C:\msys64\mingw64\bin "C:\\msys64\\mingw64\\bin\\clang.exe" -cc1 -triple x86_64-w64-windows-gnu -emit-obj -mrelax-all -disable-free -disable-llvm-verifier -discard-value-names -main-file-name test.m -mrelocation-model pic -pic-level 2 -mframe-pointer=none -fmath-errno -fno-rounding-math -mconstructor-aliases -mms-bitfields -munwind-tables -target-cpu x86-64 -debugger-tuning=gdb -v -resource-dir "C:\\msys64\\mingw64\\lib\\clang\\11.0.0" -I C:/GNUstep/x64/include/ -internal-isystem "C:\\msys64\\mingw64\\lib\\clang\\11.0.0\\include" -internal-isystem "C:\\msys64\\mingw64\\x86_64-w64-mingw32/sys-root/mingw/include" -internal-isystem "C:\\msys64\\mingw64\\x86_64-w64-mingw32\\include" -internal-isystem "C:\\msys64\\mingw64\\include" -fdebug-compilation-dir "C:\\Dev" -ferror-limit 19 -fmessage-length=164 -fno-use-cxa-atexit -fgnuc-version=4.2.1 -fobjc-runtime=gnustep-2.0 -fobjc-dispatch-method=non-legacy -fobjc-exceptions -fexceptions -fseh-exceptions -fcolor-diagnostics -faddrsig -o "C:\\msys64\\tmp\\test-c8678f.o" -x objective-c test.m clang -cc1 version 11.0.0 based upon LLVM 11.0.0 default target x86_64-w64-windows-gnu "C:\\msys64\\mingw64\\bin\\ld.lld" -m i386pep -Bdynamic -o a.exe "C:\\msys64\\mingw64\\x86_64-w64-mingw32\\lib\\crt2.o" "C:\\msys64\\mingw64\\lib\\gcc\\x86_64-w64-mingw32\\10.2.0\\crtbegin.o" -LC:/GNUstep/x64/lib/ "-LC:\\msys64\\mingw64\\lib\\gcc\\x86_64-w64-mingw32\\10.2.0" "-LC:\\msys64\\mingw64\\x86_64-w64-mingw32\\lib" "-LC:\\msys64\\mingw64\\lib" "-LC:\\msys64\\mingw64\\x86_64-w64-mingw32/sys-root/mingw/lib" -lobjc "C:\\msys64\\tmp\\test-c8678f.o" -lmingw32 -lgcc -lgcc_eh -lmoldname -lmingwex -lmsvcrt -lpthread -ladvapi32 -lshell32 -luser32 -lkernel32 -lmingw32 -lgcc -lgcc_eh -lmoldname -lmingwex -lmsvcrt -lkernel32 "C:\\msys64\\mingw64\\lib\\gcc\\x86_64-w64-mingw32\\10.2.0\\crtend.o" lld-link: error: undefined symbol: objc_begin_catch >>> referenced by C:\msys64\tmp\test-c8678f.o:(test) lld-link: error: undefined symbol: objc_end_catch >>> referenced by C:\msys64\tmp\test-c8678f.o:(test) lld-link: error: undefined symbol: __gnustep_objc_personality_v0 >>> referenced by C:\msys64\tmp\test-c8678f.o:(.xdata) clang: error: linker command failed with exit code 1 (use -v to see invocation) ``` Also happens for i686 when manually specifying -fseh-exceptions. -- 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 46277] [X86][SSE] Failure to SimplifyDemandedElts through ADDSUB intrinsics
https://bugs.llvm.org/show_bug.cgi?id=46277 Simon Pilgrim changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED Fixed By Commit(s)||e425d0b92a1df69e5e41e6b2380 ||1fabeaaef7937,c63799fc52ff2 ||473dc64cdbc343cefb8bb786b6b -- 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 48349] New: Host::ShellExpandArguments not implemented on Linux, FreeBSD and NetBSD
https://bugs.llvm.org/show_bug.cgi?id=48349 Bug ID: 48349 Summary: Host::ShellExpandArguments not implemented on Linux, FreeBSD and NetBSD 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 I was considering implementing it but it's not clear what exactly is it expected to do. The applicable expansions vary a lot between different shells. -- 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 48350] New: The generation of non-aligned instructions ldm cannot be avoided.
https://bugs.llvm.org/show_bug.cgi?id=48350
Bug ID: 48350
Summary: The generation of non-aligned instructions ldm cannot
be avoided.
Product: clang
Version: trunk
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
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
My armv8 hardware environment supports non-aligned access, except for ldrd and
ldm class instructions.But whatever option I add, I can't prevent the compiler
from generating ldm/stm, which can cause my program to be misaligned.
The code is as follows:
```
extern void* getaddr();
typedef struct {
unsigned int x[4];
unsigned char y;
}A;
typedef struct {
unsigned long long x;
}B;
typedef struct {
A a;
B b;
}Obj;
typedef struct {
int x;
A a;
B b;
}Src;
int test(Obj *a)
{
Src *b = getaddr();
a->a = b->a;
}
```
clang --target=arm-none-eabi -S -O2 a.c -o -
I've tried -mllvm arm-assume-misaligned-load-store=true, -mno-unaligned-access,
even O0, and I can't stop this kind of instruction.
```
.save {r4, r5, r6, r10, r11, lr}
push{r4, r5, r6, r10, r11, lr}
.setfp r11, sp, #16
add r11, sp, #16
mov r6, r0
bl getaddr
add r0, r0, #4
ldm r0, {r1, r2, r3, r4, r5} // This directive may cause exceptions
but cannot disable generation.
stm r6, {r1, r2, r3, r4, r5}
pop {r4, r5, r6, r10, r11, lr}
bx lr
```
--
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 48223] [AVX512][Regression] Failed to use vpsubusw
https://bugs.llvm.org/show_bug.cgi?id=48223 Simon Pilgrim changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Fixed By Commit(s)||1b209ff9e3e13492fd56ae66629 ||89ef47510db4d --- Comment #4 from Simon Pilgrim --- Should be fixed by rG1b209ff9e3e13492fd56ae6662989ef47510db4d -- 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 26049 in oss-fuzz: llvm:llvm-isel-fuzzer--aarch64-gisel: ASSERT: mutationIsSane(Rule, Query, Mutation) && "legality mutation invalid for match"
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #1 on issue 26049 by ClusterFuzz-External: llvm:llvm-isel-fuzzer--aarch64-gisel: ASSERT: mutationIsSane(Rule, Query, Mutation) && "legality mutation invalid for match" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=26049#c1 ClusterFuzz testcase 5145628651552768 is verified as fixed in https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=202011300612:202012010626 If this is incorrect, please file a bug on https://github.com/google/oss-fuzz/issues/new -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 48351] New: [lld][COFF] Backporting b79e990f4019 to 11.0.1
https://bugs.llvm.org/show_bug.cgi?id=48351 Bug ID: 48351 Summary: [lld][COFF] Backporting b79e990f4019 to 11.0.1 Product: new-bugs Version: trunk Hardware: PC OS: Windows NT Status: NEW Severity: enhancement Priority: P Component: new bugs Assignee: unassignedb...@nondot.org Reporter: dma...@mozilla.com CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org, tstel...@redhat.com Blocks: 47800 Tom: I'm OK if you don't want to take this, I'm not sure if new command line options are considered too much "new feature"-ish for a minor release. It should be pretty innocuous though, it's just wiring a couple of flags down to pre-existing functionality in the LLVM layer. 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 48256] clang-format Allman brace style joins } with while keyword in do/while loop
https://bugs.llvm.org/show_bug.cgi?id=48256
Richard changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|--- |WONTFIX
--- Comment #5 from Richard ---
OK, after more spelunking and with a little help from a vintage computing
discord server community, I found sources for sendmail 4.12 here:
http://ftp.math.utah.edu/pub/mirrors/minnie.tuhs.org/old/4BSD/Distributions/components/sendmail/
Use this gist to convert the compressed tarball to something gzip
can understand: https://gist.github.com/MikeRalphson/232163
Unpacking the 4.12 sources, we find aux/arpa.c with an author comment by
Eric Allman and a date comment of 7/25/83 containing a do/while loop like
this at line 376:
/* output the rest of the header & the body of the letter */
do
{
fputs(buf, sfp);
if (ferror(sfp))
goto spoolerr;
} while (fgets(buf, sizeof buf, stdin) != NULL);
...and several more do/while loops in the 4.12 code base that are formatted
similarly.
So while it doesn't seem consistent to me, it apparently was consistent to
Eric Allman :)
I'm therefore closing this bug as WONTFIX.
--
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 28183 in oss-fuzz: llvm:clang-objc-fuzzer: ASSERT: (LHSExpr->containsErrors() || RHSExpr->containsErrors()) && "Should only occur i
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-01 Type: Bug New issue 28183 by ClusterFuzz-External: llvm:clang-objc-fuzzer: ASSERT: (LHSExpr->containsErrors() || RHSExpr->containsErrors()) && "Should only occur i https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=28183 Detailed Report: https://oss-fuzz.com/testcase?key=4831211847155712 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: clang-objc-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: (LHSExpr->containsErrors() || RHSExpr->containsErrors()) && "Should only occur i clang::Sema::BuildBinOp clang::Sema::ActOnBinOp Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=202011300612:202012010626 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=4831211847155712 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 48342] LLDB crashes when inspecting an object created using ni::type_hierarchy
https://bugs.llvm.org/show_bug.cgi?id=48342 Raphael Isemann changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 47970] Merge cc612c29084e907900ce63ad9031ab573a64e942 into 11.0.1: [WebAssembly] Fix FastISel address calculation bug
https://bugs.llvm.org/show_bug.cgi?id=47970 Tom Stellard changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED Fixed By Commit(s)|cc612c29084e907900ce63ad903 |cc612c29084e907900ce63ad903 |1ab573a64e942 |1ab573a64e942 a082c730b89 --- Comment #5 from Tom Stellard --- Merged: a082c730b89 -- 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 47970, which changed state. Bug 47970 Summary: Merge cc612c29084e907900ce63ad9031ab573a64e942 into 11.0.1: [WebAssembly] Fix FastISel address calculation bug https://bugs.llvm.org/show_bug.cgi?id=47970 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 48352] New: TestOSPluginStepping hits an infinite loop
https://bugs.llvm.org/show_bug.cgi?id=48352 Bug ID: 48352 Summary: TestOSPluginStepping hits an infinite loop Product: lldb Version: unspecified Hardware: PC OS: FreeBSD Status: NEW Severity: normal Priority: P Component: All Bugs Assignee: lldb-...@lists.llvm.org Reporter: mgo...@gentoo.org CC: jdevliegh...@apple.com, llvm-bugs@lists.llvm.org TIMEOUT: lldb-api :: functionalities/plugins/python_os_plugin/stepping_plugin_threads/TestOSPluginStepping.py (2 of 2) TEST 'lldb-api :: functionalities/plugins/python_os_plugin/stepping_plugin_threads/TestOSPluginStepping.py' FAILED Script: -- /usr/local/bin/python3.7 /home/mgorny/llvm-project/llvm/tools/lldb/test/API/dotest.py -S nm -u CXXFLAGS -u CFLAGS --env ARCHIVER=/usr/bin/ar --env OBJCOPY=/usr/bin/objcopy --env LLVM_LIBS_DIR=/home/mgorny/llvm-project/_build/./lib --arch x86_64 --build-dir /home/mgorny/llvm-project/_build/lldb-test-build.noindex -s /home/mgorny/llvm-project/_build/lldb-test-traces --lldb-module-cache-dir /home/mgorny/llvm-project/_build/lldb-test-build.noindex/module-cache-lldb/lldb-api --clang-module-cache-dir /home/mgorny/llvm-project/_build/lldb-test-build.noindex/module-cache-clang/lldb-api --executable /home/mgorny/llvm-project/_build/./bin/lldb --compiler /home/mgorny/llvm-project/_build/./bin/clang --dsymutil /home/mgorny/llvm-project/_build/./bin/dsymutil --filecheck /home/mgorny/llvm-project/_build/./bin/FileCheck --yaml2obj /home/mgorny/llvm-project/_build/./bin/yaml2obj --lldb-libs-dir /home/mgorny/llvm-project/_build/./lib /usr/home/mgorny/llvm-project/lldb/test/API/functionalities/plugins/python_os_plugin/stepping_plugin_threads -p TestOSPluginStepping.py -- Exit Code: -9 Timeout: Reached timeout of 15 seconds Command Output (stdout): -- lldb version 12.0.0 Called get_thread_info: g_value: 0 Called get_thread_info: g_value: 0 Called get_thread_info: g_value: 0 Called get_thread_info: g_value: 0 Called get_thread_info: g_value: 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 48063] Merge 0fca6517118d435f9c2d7afe6135fd5f357509b5 into 11.0.1 release
https://bugs.llvm.org/show_bug.cgi?id=48063 Tom Stellard changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED Fixed By Commit(s)|0fca6517118d435f9c2d7afe613 |0fca6517118d435f9c2d7afe613 |5fd5f357509b5 |5fd5f357509b5 8b89bc0de0e --- Comment #6 from Tom Stellard --- Merged: 8b89bc0de0e -- 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 48063, which changed state. Bug 48063 Summary: Merge 0fca6517118d435f9c2d7afe6135fd5f357509b5 into 11.0.1 release https://bugs.llvm.org/show_bug.cgi?id=48063 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 48353] New: [InstCombine] Incorrect folding of LShr into select instruction
https://bugs.llvm.org/show_bug.cgi?id=48353
Bug ID: 48353
Summary: [InstCombine] Incorrect folding of LShr into select
instruction
Product: libraries
Version: trunk
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: Scalar Optimizations
Assignee: unassignedb...@nondot.org
Reporter: congzhe...@gmail.com
CC: llvm-bugs@lists.llvm.org
The IR that exposes this bug is as follows.
; ModuleID = 'test.c'
@m = common dso_local local_unnamed_addr global i32 0, align 4
define dso_local i32 @test() local_unnamed_addr #1 {
entry:
call fastcc void @foo(i32 51)
ret i32 0
}
define internal fastcc void @foo(i32 %aj) {
entry:
%cmp.i = icmp sgt i32 %aj, 1
%shr.i = select i1 %cmp.i, i32 0, i32 %aj
%cond.i1 = lshr i32 3, %shr.i
%conv.i = trunc i32 %cond.i1 to i8
%0 = and i8 %conv.i, 1
%cmp4 = icmp ugt i8 %0, 0
%conv5 = zext i1 %cmp4 to i32
store i32 %conv5, i32* @m
ret void
}
Note that at compile time we know the argument of foo() is %aj = 51 thus
"%shr.i = select i1 %cmp.i, i32 0, i32 %aj" will result in 0 and hence LShr
instruction that follows is correct, not resulting in a poison value.
When running "opt -instcombine test.ll -S", the following IR is generated.
Specifically, "%aj.op = lshr i32 3, %aj" is generated which result in a poison
value since %aj is actually greater than 32.
@m = common dso_local local_unnamed_addr global i32 0, align 4
define dso_local i32 @test() local_unnamed_addr #1 {
entry:
call fastcc void @foo(i32 51)
ret i32 0
}
define internal fastcc void @o(i32 %aj) {
entry:
%cmp.i = icmp sgt i32 %aj, 1
%aj.op = lshr i32 3, %aj
%.op2 = and i32 %aj.op, 1
%cmp.i3 = zext i1 %cmp.i to i32
%conv55 = or i32 %.op2, %cmp.i3
store i32 %conv55, i32* @m, align 4
ret void
}
The cause is that during InstCombine, we fold
%shr.i = select i1 %cmp.i, i32 0, i32 %aj
%cond.i1 = lshr i32 3, %shr.i
into
%aj.op = lshr i32 3, %aj
%cond.i1 = select i1 %cmp.i, i32 3, i32 %aj.op,
thus generating the incorrect LShr instruction "%aj.op = lshr i32 3, %aj".
Our proposed fix:
In function InstCombiner::FoldOpIntoSelect() from
Transforms/InstCombine/InstructionCombining.cpp, add the following check such
that we only fold LShr into select when both the true value and the false value
are known to be constants.
// If op is a LShr instruction, we can only fold into select when both TV
// and FV are known to be constants, otherwise they may be evaluated to be
// greater than the width of the first operand of LShr, resulting in for
// example:
// LShr i32 X Y where Y > 32,
// which is not suppose to be generated.
if (Op.getOpcode() == Instruction::LShr &&
!(isa(TV) && isa(FV))) {
return nullptr;
}
--
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 48289] Driver/hip-toolchain-rdc-static-lib.hip fails on Windows
https://bugs.llvm.org/show_bug.cgi?id=48289 Tom Stellard changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Fixed By Commit(s)|f89e9c8201ea5a5b63af854c92e |f89e9c8201ea5a5b63af854c92e |d26bc7ab4b8db |d26bc7ab4b8db |cd5897d55908827faf3e16c505b |cd5897d55908827faf3e16c505b |d79732a8f6eb6 |d79732a8f6eb6 19a8a7445dd ||2cf5c80ab6d --- Comment #4 from Tom Stellard --- Merged: 2cf5c80ab6d -- 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 48289, which changed state. Bug 48289 Summary: Driver/hip-toolchain-rdc-static-lib.hip fails on Windows https://bugs.llvm.org/show_bug.cgi?id=48289 What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 28198 in oss-fuzz: llvm:clang-fuzzer: Stack-overflow in DiagnoseTwoPhaseLookup
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-02 Type: Bug New issue 28198 by ClusterFuzz-External: llvm:clang-fuzzer: Stack-overflow in DiagnoseTwoPhaseLookup https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=28198 Detailed Report: https://oss-fuzz.com/testcase?key=5699236515282944 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: clang-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Stack-overflow Crash Address: 0x7ffcbb057ac0 Crash State: DiagnoseTwoPhaseLookup BuildRecoveryCallExpr FinishOverloadedCallExpr 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=5699236515282944 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
