[llvm-bugs] Issue 4802 in oss-fuzz: llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: (NewCT.isUndef() || isConstantOrConstantVector(NewCT) || isConstantFPBuildVector
Comment #3 on issue 4802 by ClusterFuzz-External: llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: (NewCT.isUndef() || isConstantOrConstantVector(NewCT) || isConstantFPBuildVector https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4802#c3 ClusterFuzz has detected this issue as fixed in range 201712270612:201712280611. Detailed report: https://oss-fuzz.com/testcase?key=5451383089135616 Project: llvm Fuzzer: libFuzzer_llvm_llvm-isel-fuzzer--aarch64-O2 Fuzz target binary: llvm-isel-fuzzer--aarch64-O2 Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: (NewCT.isUndef() || isConstantOrConstantVector(NewCT) || isConstantFPBuildVector DAGCombiner::foldBinOpIntoSelect DAGCombiner::visit Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201710160455:201710190451 Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201712270612:201712280611 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5451383089135616 See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for more information. If you suspect that the result above is incorrect, try re-doing that job on the test case report page. -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 4808 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-instcombine: ASSERT: IndexVal < VectorWidth
Comment #3 on issue 4808 by ClusterFuzz-External: llvm/llvm-opt-fuzzer--x86_64-instcombine: ASSERT: IndexVal < VectorWidth https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4808#c3 ClusterFuzz has detected this issue as fixed in range 201712270612:201712280611. Detailed report: https://oss-fuzz.com/testcase?key=4573003489738752 Project: llvm Fuzzer: libFuzzer_llvm_llvm-opt-fuzzer--x86_64-instcombine Fuzz target binary: llvm-opt-fuzzer--x86_64-instcombine Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: IndexVal < VectorWidth llvm::InstCombiner::visitExtractElementInst llvm::InstCombiner::run Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201712260607:201712270612 Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201712270612:201712280611 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=4573003489738752 See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for more information. If you suspect that the result above is incorrect, try re-doing that job on the test case report page. -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 4768 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-instcombine: ASSERT: getActiveBits() <= 64 && "Too many bits for uint64_t"
Comment #3 on issue 4768 by ClusterFuzz-External: llvm/llvm-opt-fuzzer--x86_64-instcombine: ASSERT: getActiveBits() <= 64 && "Too many bits for uint64_t" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4768#c3 ClusterFuzz has detected this issue as fixed in range 201712270612:201712280611. Detailed report: https://oss-fuzz.com/testcase?key=5281633767784448 Project: llvm Fuzzer: libFuzzer_llvm_llvm-opt-fuzzer--x86_64-instcombine Fuzz target binary: llvm-opt-fuzzer--x86_64-instcombine Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: getActiveBits() <= 64 && "Too many bits for uint64_t" llvm::SimplifyExtractElementInst llvm::InstCombiner::visitExtractElementInst Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201712190608:201712210617 Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201712270612:201712280611 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5281633767784448 See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for more information. If you suspect that the result above is incorrect, try re-doing that job on the test case report page. -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 4808 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-instcombine: ASSERT: IndexVal < VectorWidth
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #4 on issue 4808 by ClusterFuzz-External: llvm/llvm-opt-fuzzer--x86_64-instcombine: ASSERT: IndexVal < VectorWidth https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4808#c4 ClusterFuzz testcase 4573003489738752 is verified as fixed, so closing issue as verified. If this is incorrect, please file a bug on https://github.com/google/oss-fuzz/issues/new -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 4768 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-instcombine: ASSERT: getActiveBits() <= 64 && "Too many bits for uint64_t"
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #4 on issue 4768 by ClusterFuzz-External: llvm/llvm-opt-fuzzer--x86_64-instcombine: ASSERT: getActiveBits() <= 64 && "Too many bits for uint64_t" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4768#c4 ClusterFuzz testcase 5281633767784448 is verified as fixed, so closing issue as verified. If this is incorrect, please file a bug on https://github.com/google/oss-fuzz/issues/new -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 4802 in oss-fuzz: llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: (NewCT.isUndef() || isConstantOrConstantVector(NewCT) || isConstantFPBuildVector
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #4 on issue 4802 by ClusterFuzz-External: llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: (NewCT.isUndef() || isConstantOrConstantVector(NewCT) || isConstantFPBuildVector https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4802#c4 ClusterFuzz testcase 5451383089135616 is verified as fixed, so closing issue as verified. If this is incorrect, please file a bug on https://github.com/google/oss-fuzz/issues/new -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 4788 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-instcombine: ASSERT: isa(Val) && "cast() argument of incompatible type!"
Comment #2 on issue 4788 by simon.j@gmail.com: llvm/llvm-opt-fuzzer--x86_64-instcombine: ASSERT: isa(Val) && "cast() argument of incompatible type!" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4788#c2 Fixed in llvm trunk at rL321515. -- 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 35763] New: -O0 bug: long bitfields triggering incorrect code
https://bugs.llvm.org/show_bug.cgi?id=35763
Bug ID: 35763
Summary: -O0 bug: long bitfields triggering incorrect code
Product: new-bugs
Version: trunk
Hardware: PC
OS: All
Status: NEW
Severity: enhancement
Priority: P
Component: new bugs
Assignee: unassignedb...@nondot.org
Reporter: babo...@gmail.com
CC: llvm-bugs@lists.llvm.org
clang trunk, x86_64, rev321482.
> cat f.cpp
struct S {
short m0;
unsigned long long int m2 : 21;
short m3 : 16;
short m5 : 17;
short : 16;
};
S z = {-724, 388702ULL, 26720, 2792};
unsigned long long int tf_3_var_136 = 0;
void foo() {
tf_3_var_136 = ((unsigned short)(z.m0 | z.m2));
z.m5 = 0;
}
int main() {
foo();
__builtin_printf("%llu\n", tf_3_var_136);
return 0;
}
> clang++ -w f.cpp -o outc; g++ -w f.cpp -o outg; ./outc; ./outg
3999203198
65406
Note that clang 5.0 also produces correct result (as gcc in the example above).
Slight massaging of the test case make the bug go. You may notice that one of
the bit fields is longer than "base" type, i.e. short : 17. But this is a valid
C++, according to the standard bits after the "base" type size are just
"padding".
Anyway, effects triggered by this example are definitely considered as a bug by
regular clang users.
--
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 35764] New: [AMDGPU][MC][GFX8][GFX9] Missing XNACK_MASK support
https://bugs.llvm.org/show_bug.cgi?id=35764 Bug ID: 35764 Summary: [AMDGPU][MC][GFX8][GFX9] Missing XNACK_MASK support Product: libraries Version: trunk Hardware: PC OS: All Status: NEW Severity: enhancement Priority: P Component: Backend: AMDGPU Assignee: unassignedb...@nondot.org Reporter: dpreobrazhen...@luxoft.com CC: llvm-bugs@lists.llvm.org GFX8 and GFX9 should support XNACK_MASK operand. An example of a failed test: s_mov_b64 xnack_mask, -1 -- 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 35765] New: "X86 DAG->DAG Instruction Selection on function" triggers wrong code
https://bugs.llvm.org/show_bug.cgi?id=35765
Bug ID: 35765
Summary: "X86 DAG->DAG Instruction Selection on function"
triggers wrong code
Product: new-bugs
Version: trunk
Hardware: PC
OS: All
Status: NEW
Severity: enhancement
Priority: P
Component: new bugs
Assignee: unassignedb...@nondot.org
Reporter: babo...@gmail.com
CC: llvm-bugs@lists.llvm.org
clang trunk, x86_64, rev321482
> cat f.cpp
struct S {
unsigned short m : 11;
};
long long int ll;
S s1 = { 1403 };
long long int x = 2651237805702985558L;
S s2 = { 902 };
void foo() {
ll = (4 << (s1.m - 1398)) ^ (unsigned short)(x | ~s2.m);
}
int main() {
foo();
__builtin_printf("%lld\n", ll);
return 0;
}
> clang++ f.cpp -std=c++11 -o out -O0; ./out
65535
> clang++ f.cpp -std=c++11 -o out -O2; ./out
-1
clang 5.0 produces correct result, so this is regression.
--
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 35766] New: After r320437, lld links FreeBSD kernel incorrectly
https://bugs.llvm.org/show_bug.cgi?id=35766
Bug ID: 35766
Summary: After r320437, lld links FreeBSD kernel incorrectly
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
Linking the FreeBSD kernel with recent lld, I noticed complaints from ctfmerge:
ERROR: ctfmerge: kernel.full.ctf: Cannot finalize temp file: Layout constraint
violation
Running GNU objcopy on such a kernel image shows:
/usr/local/bin/objcopy: kernel.test: section .init_array lma 0x1733000 adjusted
to 0x17330f0
/usr/local/bin/objcopy: kernel.test: section .fini_array lma 0x1733000 adjusted
to 0x17330f0
/usr/local/bin/objcopy: kernel.test: section .data.rel.ro lma 0x1733000
adjusted to 0x17330f0
/usr/local/bin/objcopy: kernel.test: section .preinit_array lma 0x1733000
adjusted to 0x17330f0
I bisected and found https://reviews.llvm.org/rL320437 ("[ELF] Change default
output section type to SHT_NOBITS") to be the cause.
Maybe it is due to the linker script the FreeBSD kernel uses? I will attach or
upload the reproduction files.
--
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 4821 in oss-fuzz: llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: NumValues == VTs.NumVTs && "NumValues wasn't wide enough for its operands!"
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com, igm...@gmail.com, llvm-b...@lists.llvm.org, v...@apple.com, akils...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible Engine-libfuzzer Proj-llvm Reported-2017-12-28 Type: Bug New issue 4821 by ClusterFuzz-External: llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: NumValues == VTs.NumVTs && "NumValues wasn't wide enough for its operands!" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4821 Detailed report: https://oss-fuzz.com/testcase?key=4537382373163008 Project: llvm Fuzzer: libFuzzer_llvm_llvm-isel-fuzzer--aarch64-O2 Fuzz target binary: llvm-isel-fuzzer--aarch64-O2 Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: NumValues == VTs.NumVTs && "NumValues wasn't wide enough for its operands!" llvm::SDNode::SDNode llvm::SelectionDAG::getNode Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201710160455:201710190451 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=4537382373163008 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 35767] New: Crash with alloca swifterror
https://bugs.llvm.org/show_bug.cgi?id=35767
Bug ID: 35767
Summary: Crash with alloca swifterror
Product: libraries
Version: trunk
Hardware: PC
OS: Windows NT
Status: NEW
Severity: enhancement
Priority: P
Component: Backend: X86
Assignee: unassignedb...@nondot.org
Reporter: llvm-...@redking.me.uk
CC: llvm-bugs@lists.llvm.org
Reduced from https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4805
Removing the 'swifterror' attribute succeeds.
llc -mtriple=x86_64-unknown
define void @f() {
br label %BB1
BB1:
%A31 = alloca swifterror i32
%L7 = load i32, i32* %A31
%B30 = add i32 %L7, 2147483647
store i32 %B30, i32* %A31
store i32 %L7, i32* undef
%C29 = icmp slt i32 %L7, %B30
br label %BB1
unreachable
}
** EXPANDING POST-RA PSEUDO INSTRS **
** Function: f
real copy: renamable %rcx = COPY %rsp
replaced by: %rcx = MOV64rr %rsp
real copy: %rsp = COPY killed renamable %rcx
replaced by: %rsp = MOV64rr killed %rcx
real copy: renamable %eax = COPY killed renamable %rax
Cannot copy RAX to EAX
Cannot emit physreg copy instruction
UNREACHABLE executed at D:\LLVM\llvm\lib\Target\X86\X86InstrInfo.cpp:6813!
--
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 35768] New: Clang format does not add an extra space for comments that starts with #
https://bugs.llvm.org/show_bug.cgi?id=35768 Bug ID: 35768 Summary: Clang format does not add an extra space for comments that starts with # Product: clang Version: trunk Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: Formatter Assignee: unassignedclangb...@nondot.org Reporter: jasju...@gmail.com CC: djas...@google.com, kli...@google.com, llvm-bugs@lists.llvm.org For normal situations, if I comment out code like //int a; Clang format reformats it to // int a; However for the below code //#include Clang format doesn't do anything to it. I am expecting it to reformat it to // #include I am dealing with legacy code and because clang format doesn't handle this I had to manually go in one by one to fix it otherwise it won't pass the check by cpplint, which causes the CI to fail. It would be great to have this fixed. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 4644 in oss-fuzz: llvm/llvm-dwarfdump-fuzzer: ASSERT: Params.Version && Params.AddrSize && "Invalid Params for form"
Comment #4 on issue 4644 by jdevlieg...@apple.com: llvm/llvm-dwarfdump-fuzzer: ASSERT: Params.Version && Params.AddrSize && "Invalid Params for form" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4644#c4 Potential fix up for review: https://reviews.llvm.org/D41615 -- 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 35769] New: [ValueTracking] Can't make a non-negative value negative
https://bugs.llvm.org/show_bug.cgi?id=35769
Bug ID: 35769
Summary: [ValueTracking] Can't make a non-negative value
negative
Product: libraries
Version: trunk
Hardware: PC
OS: Windows NT
Status: NEW
Severity: enhancement
Priority: P
Component: Common Code Generator Code
Assignee: unassignedb...@nondot.org
Reporter: llvm-...@redking.me.uk
CC: craig.top...@gmail.com, llvm-bugs@lists.llvm.org
Reduced from: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4729
opt -instcombine
define i32 @bar4(i32 %a) {
%and = and i32 %a, 7
%C2 = icmp sle i32 %and, -2147483648
tail call void @llvm.assume(i1 %C2)
store i1 %C2, i1* undef
ret i32 -2147483648
}
declare void @llvm.assume(i1) nounwind
Craig - this looks like it came from D32651/rL301747
--
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 35736] ThinLTO-generated IR yields assembler error on i686 MSVC
https://bugs.llvm.org/show_bug.cgi?id=35736 Reid Kleckner changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #1 from Reid Kleckner --- r321532 should fix this. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 35762] lld-link does not support /ignore:4217 (suppress "locally defined symbol imported")
https://bugs.llvm.org/show_bug.cgi?id=35762 Robbert Haarman changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #4 from Robbert Haarman --- Fixed by r321512. -- 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 35769] [ValueTracking] Can't make a non-negative value negative
https://bugs.llvm.org/show_bug.cgi?id=35769 Craig Topper changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #1 from Craig Topper --- Bad assert removed in r321539 -- 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 35770] New: running clang -g on a text-format LLVM IR input should add debug information
https://bugs.llvm.org/show_bug.cgi?id=35770 Bug ID: 35770 Summary: running clang -g on a text-format LLVM IR input should add debug information Product: clang Version: unspecified Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: LLVM Codegen Assignee: unassignedclangb...@nondot.org Reporter: richard-l...@metafoo.co.uk CC: llvm-bugs@lists.llvm.org $ clang -g foo.ll ... should add debug information, pointing back to the .ll file, in the same way that $ clang -g foo.s ... already adds debug information pointing back to the relevant line in the .s file. This would make it possible to perform "source"-level single-step debugging through llvm IR in the user's debugger of choice. (And for optimizations that properly preserve debug information, would allow a limited amount of mapping from optimized IR back into the original IR.) -- 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
