[llvm-bugs] [Bug 38803] AVX-512: Unable to copy EFLAGS physical register!
https://bugs.llvm.org/show_bug.cgi?id=38803 Craig Topper changed: What|Removed |Added Resolution|--- |FIXED Fixed By Commit(s)||r343443 Status|NEW |RESOLVED --- Comment #2 from Craig Topper --- Fixed in r343443 -- 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 38773] [DebugInfo][Dexter] Incorrect DBG_VALUE after MCP dead copy instruction removal.
https://bugs.llvm.org/show_bug.cgi?id=38773 Carlos Alberto Enciso changed: What|Removed |Added Summary|[DebugInfo][Dexter] |[DebugInfo][Dexter] |Divide-before-return|Incorrect DBG_VALUE after |displays wrong value in |MCP dead copy instruction |debugger|removal. Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #3 from Carlos Alberto Enciso --- The patch has been committed at: https://reviews.llvm.org/rL343445 -- 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 38768] [meta][DebugInfo] Umbrella bug for poor debug experiences
https://bugs.llvm.org/show_bug.cgi?id=38768 Bug 38768 depends on bug 38773, which changed state. Bug 38773 Summary: [DebugInfo][Dexter] Incorrect DBG_VALUE after MCP dead copy instruction removal. https://bugs.llvm.org/show_bug.cgi?id=38773 What|Removed |Added Status|ASSIGNED|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 http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 39136] New: Clang crash when compiling buggy code in 7.0
https://bugs.llvm.org/show_bug.cgi?id=39136 Bug ID: 39136 Summary: Clang crash when compiling buggy code in 7.0 Product: clang Version: 7.0 Hardware: PC OS: Linux Status: NEW Severity: normal Priority: P Component: -New Bugs Assignee: unassignedclangb...@nondot.org Reporter: james.chic...@xtxmarkets.com CC: llvm-bugs@lists.llvm.org Created attachment 20946 --> https://bugs.llvm.org/attachment.cgi?id=20946&action=edit Stack dump from compiling the excerpt as well as preprocessed source and run script When compiling our C++17 codebase I encounter a segmentation fault in clang 7.0. It's when compiling an invalid program admittedly but of course the compiler should not crash regardless. I ran creduce on the example and it cut it down to this excerpt: template qwertyuiopasdfghjklz; template b()->qwertyuiopasdfghjklz<>; The length of symbol 'qwertyuiopasdfghjklz' is actually important for the crash. I found I cannot reproduce with a token shorter than above, but that length or larger causes the crash. I have attached the output I get when attempting to compile the excerpt, as well as the preprocessed source and associated run script. We build clang like this (tl;dr build from source using gcc 8.2): export LINK_FLAGS="-Wl,-rpath,/gcc-8.2/lib64 -L/gcc-8.2/lib64" cmake \ -G "Unix Makefiles" \ -DCMAKE_INSTALL_PREFIX=/home/jchicke/clang-7 \ -DCMAKE_BUILD_TYPE=RelWithDebInfo \ -DCMAKE_SHARED_LINKER_FLAGS=$LINK_FLAGS \ -DCMAKE_MODULE_LINKER_FLAGS=$LINK_FLAGS \ -DCMAKE_EXE_LINKER_FLAGS=$LINK_FLAGS \ -DCMAKE_C_LINK_FLAGS=$LINK_FLAGS \ -DLLVM_OPTIMIZED_TABLEGEN=On \ -DLLVM_BINUTILS_INCDIR=/gcc-8.2/include \ ../src Any more info you need please ask. -- 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 39137] New: Imrove perfromance when user sets same number of threads
https://bugs.llvm.org/show_bug.cgi?id=39137 Bug ID: 39137 Summary: Imrove perfromance when user sets same number of threads Product: OpenMP Version: unspecified Hardware: PC OS: All Status: NEW Severity: enhancement Priority: P Component: Runtime Library Assignee: unassignedb...@nondot.org Reporter: andrey.churba...@intel.com CC: llvm-bugs@lists.llvm.org omp_set_num_threads() or num_threads() clause can set same number of threads each time. The library should do "nothing" in this case. -- 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 39138] New: Missing SymbolCast for explicit integer downcasts
https://bugs.llvm.org/show_bug.cgi?id=39138 Bug ID: 39138 Summary: Missing SymbolCast for explicit integer downcasts Product: clang Version: trunk Hardware: All OS: All Status: NEW Severity: normal Priority: P Component: Static Analyzer Assignee: dcough...@apple.com Reporter: adam.bal...@ericsson.com CC: llvm-bugs@lists.llvm.org `ExprEngine` only creates `SymbolCast` for an integer `CastExpr` if the result is known to be truncated. However it does not create it if the result only "may be" truncated. These casts are simply ignored which leads to incorrect results: If `n` is of type `unsigned char` and `m` is a wider `unsigned`, then the range of `m` is incorrect after this code: ``` assert(n >= 0xfe); m = (unsigned char)(n + 1); ``` If `n >= 0xfe` then `n` is either `0xfe` or `0xff`, so `m` should be either `0xff` or `0`. However, the range of `m` in this case is `[0xff..0x100]` which means that the downcast is ignored. -- 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 39139] New: When inserting DBG_VALUEs check for duplicates
https://bugs.llvm.org/show_bug.cgi?id=39139 Bug ID: 39139 Summary: When inserting DBG_VALUEs check for duplicates Product: new-bugs Version: trunk Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: new bugs Assignee: unassignedb...@nondot.org Reporter: international.phan...@gmail.com CC: apra...@apple.com, david.stenb...@ericsson.com, dblai...@gmail.com, greg.bedw...@sony.com, llvm-bugs@lists.llvm.org, paul.robin...@am.sony.com, paul_robin...@playstation.sony.com, v...@apple.com As part of the review of bug 38773, the used MIR test case, showed duplicated DBG_VALUES: = renamable $ecx = COPY $eax, debug-location !31 DBG_VALUE debug-use $ecx, debug-use $noreg, !14, !DIExpression(), debug-location !23 DBG_VALUE debug-use $ecx, debug-use $noreg, !14, !DIExpression(), debug-location !23 = -- 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 39140] New: Improve 'collectDebugValues' algorithm.
https://bugs.llvm.org/show_bug.cgi?id=39140 Bug ID: 39140 Summary: Improve 'collectDebugValues' algorithm. Product: new-bugs Version: trunk Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: new bugs Assignee: unassignedb...@nondot.org Reporter: international.phan...@gmail.com CC: apra...@apple.com, dblai...@gmail.com, f...@flametop.co.uk, greg.bedw...@sony.com, jeremy.morse.l...@gmail.com, llvm-bugs@lists.llvm.org, paul.robin...@am.sony.com, v...@apple.com, wolfgang_p...@playstation.sony.com During the review of https://reviews.llvm.org/D50887 there were some discussion on the algorithm used by 'collectDebugValues': https://reviews.llvm.org/D50887?id=161183#inline-448054 The idea was to use the list of USEs instead of linearily scanning through all instructions. https://reviews.llvm.org/D50887?id=161183#inline-448099 It was mentioned to use `MachineInstrIterator::use_instructions(Reg)`, with a MRI object being available in the contexts where collecting debug values. -- 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 39141] New: Extend llvm.dbg.value to take more than one LLVM SSA value.
https://bugs.llvm.org/show_bug.cgi?id=39141 Bug ID: 39141 Summary: Extend llvm.dbg.value to take more than one LLVM SSA value. Product: new-bugs Version: trunk Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: new bugs Assignee: unassignedb...@nondot.org Reporter: international.phan...@gmail.com CC: apra...@apple.com, david.stenb...@ericsson.com, dblai...@gmail.com, f...@flametop.co.uk, greg.bedw...@sony.com, jeremy.morse.l...@gmail.com, llvm-bugs@lists.llvm.org, paul.robin...@am.sony.com, v...@apple.com, wolfgang_p...@playstation.sony.com During the review of https://reviews.llvm.org/D51976 where debug information being incorrect (-O2), there were some discussions about extending `llvm.dbg.value' to take more than one LLVM SSA value, as reflected by: bug 38763 comment 7 and comment 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 http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 39142] New: Merge r342461 into the 7.0 branch : [Xray] llvm-xray fix possible segfault
https://bugs.llvm.org/show_bug.cgi?id=39142 Bug ID: 39142 Summary: Merge r342461 into the 7.0 branch : [Xray] llvm-xray fix possible segfault Product: new-bugs Version: 7.0 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P Component: new bugs Assignee: unassignedb...@nondot.org Reporter: devne...@gmail.com CC: llvm-bugs@lists.llvm.org Blocks: 39106 Is it OK to merge the following revision(s) to the 7.0 branch? Referenced Bugs: https://bugs.llvm.org/show_bug.cgi?id=39106 [Bug 39106] [meta] 7.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 http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 38803] AVX-512: Unable to copy EFLAGS physical register!
https://bugs.llvm.org/show_bug.cgi?id=38803 Craig Topper changed: What|Removed |Added Status|RESOLVED|REOPENED Blocks||39106 Resolution|FIXED |--- --- Comment #4 from Craig Topper --- Reopening and marking block 7.0.1 Referenced Bugs: https://bugs.llvm.org/show_bug.cgi?id=39106 [Bug 39106] [meta] 7.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 http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 39106] [meta] 7.0.1 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=39106 Bug 39106 depends on bug 38803, which changed state. Bug 38803 Summary: AVX-512: Unable to copy EFLAGS physical register! https://bugs.llvm.org/show_bug.cgi?id=38803 What|Removed |Added Status|RESOLVED|REOPENED 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 http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 39131] CommandObjectType.cpp:1063:7: error: cannot initialize aggregate of type 'const lldb_private::OptionDefinition [2]' with a compound literal
https://bugs.llvm.org/show_bug.cgi?id=39131 Tatyana Krasnukha changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Fixed By Commit(s)||343500 --- Comment #3 from Tatyana Krasnukha --- Thanks for the report! Please, re-open if the issue is not 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] [Bug 39143] New: option descriptions in man page diverges from --help and sometimes from actual behaviour
https://bugs.llvm.org/show_bug.cgi?id=39143 Bug ID: 39143 Summary: option descriptions in man page diverges from --help and sometimes from actual behaviour Product: lld Version: unspecified Hardware: PC OS: All Status: NEW Severity: normal Priority: P Component: ELF Assignee: unassignedb...@nondot.org Reporter: edd-l...@mr-edd.co.uk CC: llvm-bugs@lists.llvm.org As of r335947, the content of ELF LLD man page at docs/ld.lld.1 differs from the --help in a number of places. In a couple of places, the information is contradictory and the man page does not match actual behaviour. Problems include but may not be limited to the following. I quickly scanned by eye. The following switches don't appear in the man page, but are in the --help: -(, -), --apply-dynamic-relocs, -Bshareable, -b, --call-graph-ordering-file, --call_shared, --check-sections, --cref, --dc, --dn, --dp, --dy, -d, --end-group, --execute-only, -E, -e, --fix-cortex-a53-843419, -F, -f, --gnu-unique, -h, --icf=safe, --ignore-data-address-equality, --ignore-function-address-equality, --just-symbols, --keep-unique, --library, --lto-debug-pass-manager, --lto-new-pass-manager, --lto-sample-profile, --merge-exidx-entries, --mllvm, -M, -m, --no-allow-multiple-definition, --no-apply-dynamic-relocs, --no-check-sections, --no-cref, --no-eh-frame-hdr, --no-execute-only, --no-export-dynamic, --no-fatal-warnings, --no-gdb-index, --no-merge-exidx-entries, --no-omagic, --no-pic-executable, --no-print-gc-sections, --no-print-icf-sections, --no-toc-optimize, --no-use-android-relr-tags, --no-warn-backrefs, --no-warn-common, --no-warn-symbol-ordering, --non_shared, -N, --orphan-handling, --output, --pack-dyn-relocs, --pic-executable, --plugin-opt, --plugin, --print-icf-sections, -q, -R, -r, --start-group, -S, -s, --toc-optimize, -Ttext-segment, -T, -t, --use-android-relr-tags, -u, --version, --warn-symbol-ordering, -X, -x, -y, -z. For --build-id, the man page mentions 'sha1', which isn't a supported value. It also mentions 'tree', which is handled internally but is not mentioned by --help. For --color-diagnostics, the man page says the default is 'auto', whereas --help says it's 'always'. Perhaps there's a way to generate the --help and man page from the same source? -- 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 39145] New: [libsupc++] file INSTALL cannot find "[...]/include/c++build/bits/c++config.h".
https://bugs.llvm.org/show_bug.cgi?id=39145 Bug ID: 39145 Summary: [libsupc++] file INSTALL cannot find "[...]/include/c++build/bits/c++config.h". Product: libc++ Version: 7.0 Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: All Bugs Assignee: unassignedclangb...@nondot.org Reporter: mgo...@gentoo.org CC: llvm-bugs@lists.llvm.org, mclow.li...@gmail.com, pho...@chromium.org Blocks: 39106 It seems that libcxx-7 introduces a regression in building against libsupc++. The resulting build fails to install with the following error: CMake Error at cmake_install.cmake:40 (file): file INSTALL cannot find "/var/tmp/portage/sys-libs/libcxx-7.0.0/work/libcxx-7.0.0.src-.arm/include/c++build/bits/c++config.h". It seems that the file is created in wrong directory with 'bits/bits' instead of just 'bits': [3/46] cd /var/tmp/portage/sys-libs/libcxx-7.0.0/work/libcxx-7.0.0.src-.arm && /usr/bin/cmake -E copy_if_different /usr/lib/gcc/armv7a-unknown-linux-gnueabihf/7.3.0/include/g++-v7/armv7a-unknown-linux-gnueabihf/bits/c++config.h /var/tmp/portage/sys-libs/libcxx-7.0.0/work/libcxx-7.0.0.src-.arm/include/c++build/bits/bits/c++config.h A quick bisect uncovers that the issue was introduced by the following commit: commit f48515b28b423e5387399524a7aef53c51810f59 Author: Petr Hosek Date: Tue Jun 12 03:10:02 2018 + Reland "Use custom command and target to install libc++ headers" Using file(COPY FILE...) has several downsides. Since the file command is only executed at configuration time, any changes to headers made after the initial CMake execution are ignored. This can lead to subtle errors since the just built Clang will be using stale libc++ headers. Furthermore, since the headers are copied prior to executing the build system, this may hide missing dependencies on libc++ from other LLVM components. This changes replaces the use of file(COPY FILE...) command with a custom command and target which addresses all aforementioned issues and matches the implementation already used by other LLVM components that also install headers like Clang builtin headers. Differential Revision: https://reviews.llvm.org/D44773 git-svn-id: https://llvm.org/svn/llvm-project/libcxx/trunk@334468 91177308-0d34-0410-b5e6-96231b3b80d8 Original report: https://bugs.gentoo.org/667174 Referenced Bugs: https://bugs.llvm.org/show_bug.cgi?id=39106 [Bug 39106] [meta] 7.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 http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 10343 in oss-fuzz: llvm/clang-fuzzer: ASSERT: !empty()
Comment #2 on issue 10343 by ClusterFuzz-External: llvm/clang-fuzzer: ASSERT: !empty() https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=10343#c2 ClusterFuzz has detected this issue as fixed in range 201810010232:201810011631. Detailed report: https://oss-fuzz.com/testcase?key=5753152272334848 Project: llvm Fuzzer: libFuzzer_llvm_clang-fuzzer Fuzz target binary: clang-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: !empty() clang::Preprocessor::HandleIncludeDirective clang::Preprocessor::HandleDirective Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201809130127:201809140127 Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201810010232:201810011631 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5753152272334848 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 4805 in oss-fuzz: llvm/llvm-isel-fuzzer--x86_64-O2: Abrt in llvm::llvm_unreachable_internal
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #7 on issue 4805 by ClusterFuzz-External: llvm/llvm-isel-fuzzer--x86_64-O2: Abrt in llvm::llvm_unreachable_internal https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4805#c7 ClusterFuzz testcase 5453405481861120 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 10343 in oss-fuzz: llvm/clang-fuzzer: ASSERT: !empty()
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #3 on issue 10343 by ClusterFuzz-External: llvm/clang-fuzzer: ASSERT: !empty() https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=10343#c3 ClusterFuzz testcase 5753152272334848 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 4805 in oss-fuzz: llvm/llvm-isel-fuzzer--x86_64-O2: Abrt in llvm::llvm_unreachable_internal
Comment #8 on issue 4805 by ClusterFuzz-External: llvm/llvm-isel-fuzzer--x86_64-O2: Abrt in llvm::llvm_unreachable_internal https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4805#c8 ClusterFuzz has detected this issue as fixed in range 201809300230:201810010232. Detailed report: https://oss-fuzz.com/testcase?key=5453405481861120 Project: llvm Fuzzer: libFuzzer_llvm_llvm-isel-fuzzer--x86_64-O2 Fuzz target binary: llvm-isel-fuzzer--x86_64-O2 Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Abrt Crash Address: 0x0001 Crash State: llvm::llvm_unreachable_internal llvm::X86InstrInfo::copyPhysReg ExpandPostRA::runOnMachineFunction 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=201809300230:201810010232 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5453405481861120 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] [Bug 39146] New: clang-cl ignores #pragma optimize("", off), continues optimizing
https://bugs.llvm.org/show_bug.cgi?id=39146
Bug ID: 39146
Summary: clang-cl ignores #pragma optimize("", off), continues
optimizing
Product: clang
Version: trunk
Hardware: PC
OS: Windows NT
Status: NEW
Severity: enhancement
Priority: P
Component: C++
Assignee: unassignedclangb...@nondot.org
Reporter: brucedaw...@chromium.org
CC: dgre...@apple.com, llvm-bugs@lists.llvm.org
A handy technique when working on optimized builds is to disable optimizations
for a single source file or function by adding this to the source:
#pragma optimize("", off)
With clang-cl this seems to be silently ignored - functions are still inlined
and become undebuggable. The desired effect can be obtained with this:
#pragma clang optimize off
However, if clang-cl is trying to maintain the semantics of cl.exe then it
needs to support #pragma optimize - and __pragma(optimize... - to avoid the
need for source-code changes.
Chrome's repo has about 35 instances of #pragma optimize("", off), and a couple
of instances of #pragma optimize("g", off). Some of these are bogus and should
be removed, but the compiler should still support the construct, or warn if it
is being ignored (maybe warn on unsupported variants).
--
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 36048] Several C++ data formatter tests fail with -fmodules
https://bugs.llvm.org/show_bug.cgi?id=36048 Adrian Prantl changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #6 from Adrian Prantl --- r343545 -- 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 39147] New: lld-link emits symbol data for global variables that were optimized out by /opt:ref
https://bugs.llvm.org/show_bug.cgi?id=39147 Bug ID: 39147 Summary: lld-link emits symbol data for global variables that were optimized out by /opt:ref Product: lld Version: unspecified Hardware: PC OS: Windows NT Status: NEW Severity: enhancement Priority: P Component: COFF Assignee: unassignedb...@nondot.org Reporter: brucedaw...@chromium.org CC: llvm-bugs@lists.llvm.org When running https://cs.chromium.org/chromium/src/tools/win/ShowGlobals/ on the latest Canary chrome_child.dll.pdb I noticed that some of the large globals were listed as being in section 0. I was trying to make sure that as much data as possible was in the read-only section (section 2) and this section number confused me. One of the variables in question was kWebuiResources. ShowGlobals shows this as being in section 2 in chrome.dll (browser process) and I confirmed this using the debugger and vmmap, however when I tried to repeat this test in the renderer process the debugger claimed that kWebuiResources did not exist. Checking the .rsp for chrome_child.dll I see that obj/ui/resources/webui_resources_grd/webui_resources_map.obj is indeed linked in but the linker presumably then discards kWebuiResources. It appears that when it discards the symbol it still emits a debug record for it, leading to this confusion. This isn't a serious bug but it would seem worthwhile to avoid emitting debug information for deleted data. This will shrink the PDB slightly and will avoid confusion. But, not high priority. Any recent published PDB for chrome_child.dll.pdb can be used to investigate this but the one I was using has been uploaded to Google drive and is accessible to Google employees at https://drive.google.com/open?id=1aA5LngryRAoo7T-uLdV_4Y3gpOr42mBF The top-ten (by size) symbols that this applies to are: StrTable kWebuiResources ff_aac_eld_window_512_fixed ff_aac_eld_window_480_fixed g_kuiDequantCoeff8x8 instruction_table kChromePolicyDetails kPower10MantissaTable ff_celt_pvq_u gCurrencyList -- 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 10763 in oss-fuzz: llvm/llvm-isel-fuzzer--aarch64-O2: Abrt in checkForCyclesHelper
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com, igm...@gmail.com, eney...@google.com, llvm-b...@lists.llvm.org, j...@chromium.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-10-02 Type: Bug New issue 10763 by ClusterFuzz-External: llvm/llvm-isel-fuzzer--aarch64-O2: Abrt in checkForCyclesHelper https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=10763 Detailed report: https://oss-fuzz.com/testcase?key=5704113443045376 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: Abrt Crash Address: 0x0001 Crash State: checkForCyclesHelper checkForCyclesHelper checkForCyclesHelper Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201809250234:201809260235 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5704113443045376 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 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. -- 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 10764 in oss-fuzz: llvm/clang-fuzzer: Stack-overflow in clang::APValue::swap
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com, igm...@gmail.com, eney...@google.com, llvm-b...@lists.llvm.org, j...@chromium.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-10-02 Type: Bug New issue 10764 by ClusterFuzz-External: llvm/clang-fuzzer: Stack-overflow in clang::APValue::swap https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=10764 Detailed report: https://oss-fuzz.com/testcase?key=5635264848855040 Project: llvm Fuzzer: libFuzzer_llvm_clang-fuzzer Fuzz target binary: clang-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Stack-overflow Crash Address: 0x7ffd984eb8b8 Crash State: clang::APValue::swap IntExprEvaluator::Success clang::StmtVisitorBasebool>::Visit Sanitizer: address (ASAN) Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5635264848855040 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 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. -- 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 39132] [AMDGPU] bitcast between different types assertion/crash
https://bugs.llvm.org/show_bug.cgi?id=39132 Matt Arsenault changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #6 from Matt Arsenault --- r343493 seems to have fixed this for me -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 38950] Warning for unary minus used with unsigned type
https://bugs.llvm.org/show_bug.cgi?id=38950 David Bolvansky changed: What|Removed |Added Status|NEW |RESOLVED Fixed By Commit(s)||343560 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 http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
