[llvm-bugs] Issue 5709 in oss-fuzz: llvm/llvm-isel-fuzzer--aarch64-gisel: ASSERT: Index + MRI->getType(Res).getSizeInBits() <
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com, igm...@gmail.com, llvm-b...@lists.llvm.org, v...@apple.com, mitchphi...@outlook.com, xpl...@gmail.com, akils...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible Engine-libfuzzer Proj-llvm Reported-2018-01-26 Type: Bug New issue 5709 by ClusterFuzz-External: llvm/llvm-isel-fuzzer--aarch64-gisel: ASSERT: Index + MRI->getType(Res).getSizeInBits() <= MRI->getType(Src).getSizeInBits() & https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=5709 Detailed report: https://oss-fuzz.com/testcase?key=5647351457775616 Project: llvm Fuzzer: libFuzzer_llvm_llvm-isel-fuzzer--aarch64-gisel Fuzz target binary: llvm-isel-fuzzer--aarch64-gisel Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: Index + MRI->getType(Res).getSizeInBits() <= MRI->getType(Src).getSizeInBits() & llvm::MachineIRBuilder::buildExtract llvm::LegalizerHelper::narrowScalar Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201710121744:201710130152 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5647351457775616 Issue filed automatically. See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for more information. When you fix this bug, please * mention the fix revision(s). * state whether the bug was a short-lived regression or an old bug in any stable releases. * add any other useful information. This information can help downstream consumers. If you have questions for the OSS-Fuzz team, please file an issue at https://github.com/google/oss-fuzz/issues. -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 36105] New: Infinite loop in -callsite-splitting
https://bugs.llvm.org/show_bug.cgi?id=36105
Bug ID: 36105
Summary: Infinite loop in -callsite-splitting
Product: new-bugs
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: new bugs
Assignee: unassignedb...@nondot.org
Reporter: mikael.hol...@ericsson.com
CC: llvm-bugs@lists.llvm.org
Created attachment 19755
--> https://bugs.llvm.org/attachment.cgi?id=19755&action=edit
reproducer
Running
opt -S -o - foo.ll -callsite-splitting
we get stuck and loop forever in function recordConditions in
CallSitesplitting.cpp:
/// Record ICmp conditions relevant to any argument in CS following Pred's
/// single successors. If there are conflicting conditions along a path, like
/// x == 1 and x == 0, the first condition will be used.
static void recordConditions(CallSite CS, BasicBlock *Pred,
ConditionsTy &Conditions) {
recordCondition(CS, Pred, CS.getInstruction()->getParent(), Conditions);
BasicBlock *From = Pred;
BasicBlock *To = Pred;
SmallPtrSet Visited = {From};
while (!Visited.count(From->getSinglePredecessor()) &&
(From = From->getSinglePredecessor())) {
recordCondition(CS, From, To, Conditions);
To = From;
}
}
It looks suspicious to me that Visited isn't updated in the loop.
--
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 36106] New: [AArch64][GlobalSel] Incorrect half to single precision code gen
https://bugs.llvm.org/show_bug.cgi?id=36106
Bug ID: 36106
Summary: [AArch64][GlobalSel] Incorrect half to single
precision code gen
Product: new-bugs
Version: trunk
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P
Component: new bugs
Assignee: unassignedb...@nondot.org
Reporter: carey.willi...@arm.com
CC: llvm-bugs@lists.llvm.org
Created attachment 19756
--> https://bugs.llvm.org/attachment.cgi?id=19756&action=edit
Generated ASM
I believe there is a bug in the GlobalISel -0O code generation that affects
AArch64's half-precision (FP16) mechanics.
The generated code tries to convert a float value from single precision to
half-precision via FCVT. The problem is that in this case the immediate value
it is operating on is actually already stored/encoded in the half-precision
format.
Minimal reproducer:
int main() {
_Float16 b = 1024.0f16;
return (float)b;
}
Compiled with: clang -S -O0 -mllvm -aarch64-enable-global-isel-at-O=0
--target=aarch64-arm-none-eabi -march=armv8.2-a+fp16
Passing -mllvm -aarch64-enable-global-isel-at-O=-1 instead will generate
correctly functioning code.
---
I've attached the problematic generation with some comments.
--
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 36105] Infinite loop in -callsite-splitting
https://bugs.llvm.org/show_bug.cgi?id=36105 Florian Hahn changed: What|Removed |Added CC||junb...@codeaurora.org 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 http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 36107] New: TestGModules.test_with_gmodules fails on linux
https://bugs.llvm.org/show_bug.cgi?id=36107 Bug ID: 36107 Summary: TestGModules.test_with_gmodules fails on linux Product: lldb Version: unspecified Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: All Bugs Assignee: lldb-...@lists.llvm.org Reporter: lab...@google.com CC: llvm-bugs@lists.llvm.org It started failing since r323450, but that's only because it did not actually use modules before that. This error message may be an indication of the problem: error: B-1GM9AHXMM9U5Y.pcm DWARF DIE at 0x0033 (class Module) has a member variable 0x003c (MBptr) whose type is a forward declaration, not a complete definition. Try compiling the source file with -fstandalone-debug The -fstandalone-debug is a red herring because we already pass that flag. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 35970] Implement addrspace machine memory operand printing / parsing in MIR
https://bugs.llvm.org/show_bug.cgi?id=35970 Francis Visoiu Mistrih changed: What|Removed |Added Fixed By Commit(s)||r323521 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 http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 36108] New: Merge r323515 into the 6.0 branch : [CallSiteSplitting] Fix infinite loop when recording conditions.
https://bugs.llvm.org/show_bug.cgi?id=36108 Bug ID: 36108 Summary: Merge r323515 into the 6.0 branch : [CallSiteSplitting] Fix infinite loop when recording conditions. Product: new-bugs Version: 6.0 Hardware: PC OS: All Status: NEW Severity: enhancement Priority: P Component: new bugs Assignee: unassignedb...@nondot.org Reporter: florian.h...@arm.com CC: llvm-bugs@lists.llvm.org It would great if we could pick r323515 on the 6.0 branch as this is a small fix for an infinite loop in CallSiteSplitting. https://reviews.llvm.org/rL323515 -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 34084] [PowerPC] Wimplicit-fallthrough warning in PPCISelLowering.cpp
https://bugs.llvm.org/show_bug.cgi?id=34084 Simon Pilgrim changed: What|Removed |Added Resolution|--- |FIXED Fixed By Commit(s)||320806 Status|ASSIGNED|RESOLVED --- Comment #2 from Simon Pilgrim --- This was fixed by rL320806 -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 26138] [LoopInterchange] loop-interchange pass fails during the compilation
https://bugs.llvm.org/show_bug.cgi?id=26138 Florian Hahn changed: What|Removed |Added CC||david.gr...@arm.com Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #5 from Florian Hahn --- The compile failure has been fixed by https://reviews.llvm.org/rL316261 -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 36109] New: libc++ queue and string tests fail with -gmodules on android
https://bugs.llvm.org/show_bug.cgi?id=36109 Bug ID: 36109 Summary: libc++ queue and string tests fail with -gmodules on android Product: lldb Version: unspecified Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: All Bugs Assignee: lldb-...@lists.llvm.org Reporter: lab...@google.com CC: llvm-bugs@lists.llvm.org The std::queue test fails with an amusing error message: file "Android clang version 5.0.300080 (based on LLVM 5.0.300080)\Android clang version 5.0.300080 (based on LLVM 5.0.300080)" does not exist while the std::string just fails to print a std::wstring value. Could be a parsing problem, or an issue with a (relatively) old clang used to compile the tests. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 36110] New: Erratic behavior with inline asm macros
https://bugs.llvm.org/show_bug.cgi?id=36110
Bug ID: 36110
Summary: Erratic behavior with inline asm macros
Product: clang
Version: 6.0
Hardware: PC
OS: All
Status: NEW
Severity: enhancement
Priority: P
Component: -New Bugs
Assignee: unassignedclangb...@nondot.org
Reporter: roy...@freebsd.org
CC: llvm-bugs@lists.llvm.org
It seems like clang has some specific behavior when dealing with .macros
defined inside of inline asm. Given the following example:
# cat snip.c
int main(void)
{
asm ( ".macro FOO\n.endm" );
asm ( ".macro FOO\n.endm" );
}
# clang -o snip snip.c
# clang -no-integrated-as -o snip snip.c
/tmp/snip-a5a133.s: Assembler messages:
/tmp/snip-a5a133.s:19: Error: Macro `foo' was already defined
clang: error: assembler command failed with exit code 1 (use -v to see
invocation)
Would it be possible to fix clang so it keeps .macro-s defined in other asm()-s
on the same compilation unit? (ie: so that it has the same behavior as gnu as)
Thanks, Roger.
--
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 36111] New: [X86] Clang doesn't support -mcet/-mno-cet from gcc
https://bugs.llvm.org/show_bug.cgi?id=36111 Bug ID: 36111 Summary: [X86] Clang doesn't support -mcet/-mno-cet from gcc Product: clang Version: trunk Hardware: PC OS: Windows NT Status: NEW Severity: enhancement Priority: P Component: Driver Assignee: unassignedclangb...@nondot.org Reporter: craig.top...@gmail.com CC: llvm-bugs@lists.llvm.org The clang driver doesn't support -mcet/-mno-cet which gcc treats as sort of an alias for "-mibt -mshstk". gcc additionally defines __CET__ if -mibt, -mshstk, or -mcet is specified and -fcf-protection is set to any value other than none. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 36112] New: TableGen .inc files should include #line directives
https://bugs.llvm.org/show_bug.cgi?id=36112 Bug ID: 36112 Summary: TableGen .inc files should include #line directives Product: tools Version: trunk Hardware: All OS: All Status: NEW Severity: enhancement Priority: P Component: TableGen Assignee: unassignedb...@nondot.org Reporter: jordan_r...@apple.com CC: llvm-bugs@lists.llvm.org When a diagnostic occurs in TableGen-generated .inc files, we get it in the .inc file. It would be way more helpful to get it in the .td instead. The same goes for "Jump to Definition"-y features in IDEs. Changing generators to include #line directives would solve this problem. (This is not without drawbacks; sometimes the /generator/ is wrong and you really do want to see the .inc file.) -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 36113] New: [X86] Incorrect scheduler information for scalar multiplies in Znver1 scheduler model
https://bugs.llvm.org/show_bug.cgi?id=36113
Bug ID: 36113
Summary: [X86] Incorrect scheduler information for scalar
multiplies in Znver1 scheduler model
Product: libraries
Version: trunk
Hardware: PC
OS: Windows NT
Status: NEW
Severity: enhancement
Priority: P
Component: Backend: X86
Assignee: unassignedb...@nondot.org
Reporter: craig.top...@gmail.com
CC: llvm-bugs@lists.llvm.org
Due to funny naming of multiply instructions and weak regular expressions in
the scheduler model, the Znver1 scheduler model has incorrect information.
I've changed the regular expressions to explicit instruction lists to point out
the problem. I've left TODOs for the things that I added that are either wrong
or I'm not sure about.
Here is the current version of the file with the TODOs
def ZnWriteMul16 : SchedWriteRes<[ZnALU1, ZnMultiplier]> {
let Latency = 3;
}
def : InstRW<[ZnWriteMul16], (instrs IMUL16r, MUL16r)>;
def : InstRW<[ZnWriteMul16], (instrs IMUL16rr, IMUL16rri, IMUL16rri8)>; //
TODO: is this right?
def : InstRW<[ZnWriteMul16], (instrs IMUL16rm, IMUL16rmi, IMUL16rmi8)>; //
TODO: this is definitely wrong but matches what the instregex did.
// m16.
def ZnWriteMul16Ld : SchedWriteRes<[ZnAGU, ZnALU1, ZnMultiplier]> {
let Latency = 8;
}
def : InstRW<[ZnWriteMul16Ld, ReadAfterLd], (instrs IMUL16m, MUL16m)>;
// r32.
def ZnWriteMul32 : SchedWriteRes<[ZnALU1, ZnMultiplier]> {
let Latency = 3;
}
def : InstRW<[ZnWriteMul32], (instrs IMUL32r, MUL32r)>;
def : InstRW<[ZnWriteMul32], (instrs IMUL32rr, IMUL32rri, IMUL32rri8)>; //
TODO: is this right?
def : InstRW<[ZnWriteMul32], (instrs IMUL32rm, IMUL32rmi, IMUL32rmi8)>; //
TODO: this is definitely wrong but matches what the instregex did.
// m32.
def ZnWriteMul32Ld : SchedWriteRes<[ZnAGU, ZnALU1, ZnMultiplier]> {
let Latency = 8;
}
def : InstRW<[ZnWriteMul32Ld, ReadAfterLd], (instrs IMUL32m, MUL32m)>;
// r64.
def ZnWriteMul64 : SchedWriteRes<[ZnALU1, ZnMultiplier]> {
let Latency = 4;
let NumMicroOps = 2;
}
def : InstRW<[ZnWriteMul64], (instrs IMUL64r, MUL64r)>;
def : InstRW<[ZnWriteMul64], (instrs IMUL64rr, IMUL64rri8, IMUL64rri32)>; //
TODO: is this right?
def : InstRW<[ZnWriteMul64], (instrs IMUL64rm, IMUL64rmi32, IMUL64rmi8)>; //
TODO: this is definitely wrong but matches what the instregex did.
--
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 33827] _Generic associated list is misformatted
https://bugs.llvm.org/show_bug.cgi?id=33827 Anatol changed: What|Removed |Added CC||anatol.pomo...@gmail.com Resolution|--- |DUPLICATE Status|NEW |RESOLVED --- Comment #1 from Anatol --- *** This bug has been marked as a duplicate of bug 17706 *** -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 36073] Regression: ARM segfault when upgrading to 6.0.0
https://bugs.llvm.org/show_bug.cgi?id=36073 Eli Friedman changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #19 from Eli Friedman --- https://reviews.llvm.org/rL323559 -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 36114] New: Merge r323559 to 6.0 branch ([LivePhysRegs] Preserve pristine regs in blocks with no successors.)
https://bugs.llvm.org/show_bug.cgi?id=36114 Bug ID: 36114 Summary: Merge r323559 to 6.0 branch ([LivePhysRegs] Preserve pristine regs in blocks with no successors.) Product: libraries Version: 6.0 Hardware: PC OS: Windows NT Status: NEW Severity: normal Priority: P Component: Common Code Generator Code Assignee: unassignedb...@nondot.org Reporter: efrie...@codeaurora.org CC: a...@crichton.co, h...@chromium.org, llvm-bugs@lists.llvm.org, ma...@braunis.de Blocks: 35804 https://reviews.llvm.org/rL323559. Fixes a ARM miscompile with certain code pattterns; see https://bugs.llvm.org/show_bug.cgi?id=36073 . Referenced Bugs: https://bugs.llvm.org/show_bug.cgi?id=35804 [Bug 35804] [meta] 6.0.0 Release Blockers -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 36116] New: After r299770, Assertion failed: (New->getType() == getType() && "replaceAllUses of value with new value of different type!"), function doRAUW, file lib/IR/Value.cpp, line
https://bugs.llvm.org/show_bug.cgi?id=36116
Bug ID: 36116
Summary: After r299770, Assertion failed: (New->getType() ==
getType() && "replaceAllUses of value with new value
of different type!"), function doRAUW, file
lib/IR/Value.cpp, line 375.
Product: new-bugs
Version: trunk
Hardware: PC
OS: All
Status: NEW
Severity: normal
Priority: P
Component: new bugs
Assignee: unassignedb...@nondot.org
Reporter: dimi...@andric.com
CC: llvm-bugs@lists.llvm.org
As reported in https://bugs.freebsd.org/225471, building the FreeBSD
emulators/snes9x port for x86_64 with clang 6.0.0 results in an assertion:
Assertion failed: (New->getType() == getType() && "replaceAllUses of value with
new value of different type!"), function doRAUW, file
/poudriere/jails/head-amd64/usr/src/contrib/llvm/lib/IR/Value.cpp, line 404.
This assertion still occurs with trunk r322755, and bisection shows it has
regressed with http://reviews.llvm.org/rL299770 ("Reapply r298620: [LV]
Vectorize GEPs") by Matthew Simpson. (Which was a reapplication of
https://reviews.llvm.org/rL298620.)
Minimized test case:
// clang -cc1 -triple x86_64 -S -O2 -vectorize-loops fxemu-minimized.cpp
struct {
unsigned char *a[];
} b;
unsigned char c;
int d;
void e() {
d = 0;
for (; d < 32; d++)
b.a[d] = &c + ((d & 16) << 1);
}
Note that -vectorize-loops is essential for reproducing the assertion.
As far as I can see, this is *not* a duplicate of bug 27969, bug 30783, bug
34783 or bug 34759, as those are all resolved, and this assertion still occurs
as of 2018-01-27.
--
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 36117] New: The -fdiagnostic-format option is not being passed from the driver to the assembler job
https://bugs.llvm.org/show_bug.cgi?id=36117 Bug ID: 36117 Summary: The -fdiagnostic-format option is not being passed from the driver to the assembler job Product: clang Version: unspecified Hardware: PC OS: Windows NT Status: NEW Severity: enhancement Priority: P Component: Driver Assignee: unassignedclangb...@nondot.org Reporter: konstantin.belocha...@sony.com CC: llvm-bugs@lists.llvm.org Reproducible test.s: .section .text .global TestFunc_ASM TestFunc_ASM: nop nop deliberate_error ret 1) -fdiagnostic-format option is not being passed from the driver to the assembler $ clang -fdiagnostics-format=msvc test.s clang: warning: argument unused during compilation: '-fdiagnostics-format=msvc' test.s:7:5: error: invalid instruction mnemonic 'deliberate_error' deliberate_error ^~~~ 2) The assembler does not support this option. $clang -cc1as -fdiagnostics-format=msvc -fno-show-column source1.s clang -cc1as: error: unknown argument: '-fdiagnostics-format=msvc' clang -cc1as: error: unknown argument: '-fno-show-column' -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 5734 in oss-fuzz: llvm: Stack-overflow in clang::Sema::GetNameFromUnqualifiedId
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com, igm...@gmail.com, llvm-b...@lists.llvm.org, v...@apple.com, mitchphi...@outlook.com, xpl...@gmail.com, akils...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible Engine-libfuzzer Proj-llvm Reported-2018-01-27 Type: Bug New issue 5734 by ClusterFuzz-External: llvm: Stack-overflow in clang::Sema::GetNameFromUnqualifiedId https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=5734 Detailed report: https://oss-fuzz.com/testcase?key=5160586775101440 Project: llvm Fuzzer: libFuzzer_llvm_clang-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Stack-overflow Crash Address: 0x7ffdfd22dc98 Crash State: clang::Sema::GetNameFromUnqualifiedId clang::Sema::DecomposeUnqualifiedId clang::Sema::ActOnIdExpression Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201801030610:201801040618 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5160586775101440 Issue filed automatically. See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for more information. When you fix this bug, please * mention the fix revision(s). * state whether the bug was a short-lived regression or an old bug in any stable releases. * add any other useful information. This information can help downstream consumers. If you have questions for the OSS-Fuzz team, please file an issue at https://github.com/google/oss-fuzz/issues. -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 36106] [AArch64][GlobalSel] Incorrect half to single precision code gen
https://bugs.llvm.org/show_bug.cgi?id=36106 Amara Emerson changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #2 from Amara Emerson --- Should be fixed in r323582. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
