[llvm-bugs] [Bug 42231] [docs] Improve character code explanations to cover all cases
https://bugs.llvm.org/show_bug.cgi?id=42231 James Henderson changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #2 from James Henderson --- Fixed in r364171. The updated documentation now describes what the code does. There may be instances where what the code does makes no sense, but those should be fixed independently, and the docs updated accordingly. -- 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 42368] New: LLVM failed to run 2 Tests 'Clang :: CodeGenCXX/tail-padding.cpp' and 'Clang :: OpenMP/parallel_codegen.cpp' on both x86|debug and x86|release congigurations on windows wi
https://bugs.llvm.org/show_bug.cgi?id=42368 Bug ID: 42368 Summary: LLVM failed to run 2 Tests 'Clang :: CodeGenCXX/tail-padding.cpp' and 'Clang :: OpenMP/parallel_codegen.cpp' on both x86|debug and x86|release congigurations on windows with MSVC. Product: clang Version: trunk Hardware: PC OS: Windows NT Status: NEW Severity: enhancement Priority: P Component: C++ Assignee: unassignedclangb...@nondot.org Reporter: 1998zhan...@gmail.com CC: blitzrak...@gmail.com, dgre...@apple.com, erik.pilking...@gmail.com, llvm-bugs@lists.llvm.org, richard-l...@metafoo.co.uk Created attachment 22133 --> https://bugs.llvm.org/attachment.cgi?id=22133&action=edit log_x86_test LLVM failed to run 2 Tests 'Clang :: CodeGenCXX/tail-padding.cpp' and 'Clang :: OpenMP/parallel_codegen.cpp' on both x86|debug and x86|release congigurations on windows with MSVC.Could you please have a look at this issue? Thanks a lot! Clang :: CodeGenCXX/tail-padding.cpp failed should be first reproduced on 11817fa clang master reversion. Clang :: OpenMP/parallel_codegen.cpp failed should be first reproduced on f501945 clang master reversion. Repro steps: 1 git clone -c core.autocrlf=false https://github.com/llvm-mirror/llvm D:\llvm\src\ 2 git clone -c core.autocrlf=false https://github.com/llvm-mirror/clang D:\llvm\src\tools\clang 3 open a VS 2017 x86 command prompt and browse to D:\llvm 4 mkdir build_x86 && pushd build_x86 5 cmake -G "Visual Studio 15 2017" -DCMAKE_SYSTEM_VERSION=10.0.17134.0 ..\src\ 6 msbuild /maxcpucount:4 /p:Platform=Win32 /p:Configuration=RelWithDebInfo build_x86\ALL_BUILD.vcxproj /t:Rebuild 7. python.exe ./src/utils/lit/lit.py -v --no-progress-bar --param build_mode=RelWithDebInfo --param clang_site_config=./build_x86/tools/clang/test/lit.site.cfg ./build_x86/tools/clang/test -j 4 Failures: TEST 'Clang :: CodeGenCXX/tail-padding.cpp' FAILED Script: -- : 'RUN: at line 1'; d:\llvm\build_x86\relwithdebinfo\bin\clang.exe -cc1 -internal-isystem d:\llvm\build_x86\relwithdebinfo\lib\clang\9.0.0\include -nostdsysteminc -triple i686-pc-windows-gnu -emit-llvm -o - D:\LLVM\src\tools\clang\test\CodeGenCXX\tail-padding.cpp | d:\llvm\build_x86\relwithdebinfo\bin\filecheck.exe D:\LLVM\src\tools\clang\test\CodeGenCXX\tail-padding.cpp -- Exit Code: 1 TEST 'Clang :: OpenMP/parallel_codegen.cpp' FAILED Script: -- : 'RUN: at line 1'; d:\llvm\build_x86\relwithdebinfo\bin\clang.exe -cc1 -internal-isystem d:\llvm\build_x86\relwithdebinfo\lib\clang\9.0.0\include -nostdsysteminc -verify -fopenmp -x c++ -emit-llvm D:\LLVM\src\tools\clang\test\OpenMP\parallel_codegen.cpp -triple i686-pc-windows-gnu -fexceptions -fcxx-exceptions -o - | d:\llvm\build_x86\relwithdebinfo\bin\filecheck.exe D:\LLVM\src\tools\clang\test\OpenMP\parallel_codegen.cpp : 'RUN: at line 2'; d:\llvm\build_x86\relwithdebinfo\bin\clang.exe -cc1 -internal-isystem d:\llvm\build_x86\relwithdebinfo\lib\clang\9.0.0\include -nostdsysteminc -fopenmp -x c++ -std=c++11 -triple x86_64-unknown-unknown -fexceptions -fcxx-exceptions -emit-pch -o D:\LLVM\build_x86\tools\clang\test\OpenMP\Output\parallel_codegen.cpp.tmp D:\LLVM\src\tools\clang\test\OpenMP\parallel_codegen.cpp : 'RUN: at line 3'; d:\llvm\build_x86\relwithdebinfo\bin\clang.exe -cc1 -internal-isystem d:\llvm\build_x86\relwithdebinfo\lib\clang\9.0.0\include -nostdsysteminc -fopenmp -x c++ -triple x86_64-unknown-unknown -fexceptions -fcxx-exceptions -debug-info-kind=limited -std=c++11 -include-pch D:\LLVM\build_x86\tools\clang\test\OpenMP\Output\parallel_codegen.cpp.tmp -verify D:\LLVM\src\tools\clang\test\OpenMP\parallel_codegen.cpp -emit-llvm -o - | d:\llvm\build_x86\relwithdebinfo\bin\filecheck.exe --check-prefix=CHECK-DEBUG D:\LLVM\src\tools\clang\test\OpenMP\parallel_codegen.cpp : 'RUN: at line 5'; d:\llvm\build_x86\relwithdebinfo\bin\clang.exe -cc1 -internal-isystem d:\llvm\build_x86\relwithdebinfo\lib\clang\9.0.0\include -nostdsysteminc -verify -fopenmp-simd -x c++ -emit-llvm D:\LLVM\src\tools\clang\test\OpenMP\parallel_codegen.cpp -triple i686-pc-windows-gnu -fexceptions -fcxx-exceptions -o - | d:\llvm\build_x86\relwithdebinfo\bin\filecheck.exe --check-prefix SIMD-ONLY0 D:\LLVM\src\tools\clang\test\OpenMP\parallel_codegen.cpp : 'RUN: at line 6'; d:\llvm\build_x86\relwithdebinfo\bin\clang.exe -cc1 -internal-isystem d:\llvm\build_x86\relwithdebinfo\lib\clang\9.0.0\include -nostdsysteminc -fopenmp-simd -x c++ -std=c++11 -triple x86_64-unknown-unknown -fexceptions -fcxx-exceptions -emit-pch -o D:\LLVM\build_x86\tools\clang\test\OpenMP\Output\parallel_codegen.cpp.tmp D:\LLVM\src\tools\clang\test\OpenMP\parallel_codegen.cpp : 'RUN: at line 7'; d:\llvm\build_x86\relwithdebinfo\bin\clang
[llvm-bugs] [Bug 42234] [docs][llvm-nm] Add missing options to documentation
https://bugs.llvm.org/show_bug.cgi?id=42234 James Henderson changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #2 from James Henderson --- Fixed in r364176. -- 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 42369] New: llvm - 7.0 and llvm 8.0 specify binutils version using flag
https://bugs.llvm.org/show_bug.cgi?id=42369
Bug ID: 42369
Summary: llvm - 7.0 and llvm 8.0 specify binutils version using
flag
Product: new-bugs
Version: 8.0
Hardware: Other
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: new bugs
Assignee: unassignedb...@nondot.org
Reporter: abinaya.manikan...@wipro.com
CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org
Hi,
We have been trying to build llvm 7 and 8 on RedHat 7 machine.
Would like to use specific binutils version other than the OS one.
So please let us know do we have any specific flag/option which we can use with
the build steps of llvm to specify binutils installed path [library] so llvm
can use those binutils to build.
FYI , below are the steps we are using from our end to build llvm:
mkdir build
pushd build
export CLANG_GCC=/opt/gcc/x86_64/8.3.0a/bin/gcc
cmake -DCMAKE_INSTALL_PREFIX=%{_prefix} \
-DCMAKE_BUILD_WITH_INSTALL_RPATH=1 \
-DCMAKE_C_COMPILER_LAUNCHER=ccache \
-DCMAKE_CXX_COMPILER_LAUNCHER=ccache \
-DGCC_INSTALL_PREFIX=/opt/gcc/x86_64/8.3.0a/ \
-DCMAKE_CXX_LINK_FLAGS="-L/opt/gcc/x86_64/8.3.0a/lib64" \
-DCMAKE_INSTALL_RPATH=$ORIGIN/../lib:%{gccpath}/lib64 \
-DCMAKE_CROSSCOMPILING=True -DCMAKE_BUILD_TYPE=Release \
-DLLVM_EXTERNAL_CLANG_SOURCE_DIR=../../cfe-%{version0}.src \
-DLLVM_EXTERNAL_CLANG_TOOLS_EXTRA_SOURCE_DIR=../../clang-tools-extra-%{version0}.src
-DLLVM_EXTERNAL_COMPILER_RT_SOURCE_DIR=../../compiler-rt-%{version0}.src
-Wno-dev --enable-zlib -DCMAKE_BUILD_TYPE=Release --enable-gold
--enable-plugins -DLLVM_ENABLE_ZLIB:BOOL=ON ..
make -j10 install DESTDIR="${RPM_BUILD_ROOT}"
It would be great if anyone help us here.
--
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 42370] New: lld-link fails to link pgo-instrumented clang with "error: relocation against symbol in discarded section: __profd_..."
https://bugs.llvm.org/show_bug.cgi?id=42370 Bug ID: 42370 Summary: lld-link fails to link pgo-instrumented clang with "error: relocation against symbol in discarded section: __profd_..." Product: new-bugs Version: trunk Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: new bugs Assignee: unassignedb...@nondot.org Reporter: h...@chromium.org CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org, r...@google.com To repro: (I used the monorepo at bb6d0b8e7b0d815710a71b8012438a586e986450 / r364169) build.foo>set CC=\src\llvm.monorepo\build.release\bin\clang-cl.exe build.foo>set CXX=\src\llvm.monorepo\build.release\bin\clang-cl.exe build.foo>cmake -GNinja -DCMAKE_LINKER=/src/llvm.monorepo/build.release/bin/lld-link -DCMAKE_BUILD_TYPE=Release -DLLVM_BUILD_INSTRUMENTED=IR -DLLVM_ENABLE_PROJECTS=clang ../llvm build.foo>ninja bin\Remarks.dll FAILED: bin/Remarks.dll lib/Remarks.lib cmd.exe /C "cd . && "C:\Program Files\CMake\bin\cmake.exe" -E vs_link_dll --intdir=tools\remarks-shlib\CMakeFiles\Remarks.dir --manifests -- \src\llvm.monorepo\build.release\bin\lld-link /nologo tools\remarks-shlib\CMakeFiles\Remarks.dir\libremarks.cpp.obj tools\remarks-shlib\CMakeFiles\Remarks.dir\__\__\resources\windows_version_resource.rc.res /out:bin\Remarks.dll /implib:lib\Remarks.lib /pdb:bin\Remarks.pdb /dll /version:0.0 /machine:x64 -fprofile-generate='C:\src\llvm.monorepo\build.foo\profiles' /INCREMENTAL:NO /DEF:"C:/src/llvm.monorepo/build.foo/tools/remarks-shlib/Remarks.def" lib\LLVMRemarks.lib lib\LLVMSupport.lib psapi.lib shell32.lib ole32.lib uuid.lib advapi32.lib delayimp.lib -delayload:shell32.dll -delayload:ole32.dll lib\LLVMDemangle.lib kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib && cd ." LINK: command "\src\llvm.monorepo\build.release\bin\lld-link /nologo tools\remarks-shlib\CMakeFiles\Remarks.dir\libremarks.cpp.obj tools\remarks-shlib\CMakeFiles\Remarks.dir\__\__\resources\windows_version_resource.rc.res /out:bin\Remarks.dll /implib:lib\Remarks.lib /pdb:bin\Remarks.pdb /dll /version:0.0 /machine:x64 -fprofile-generate='C:\src\llvm.monorepo\build.foo\profiles' /INCREMENTAL:NO /DEF:C:/src/llvm.monorepo/build.foo/tools/remarks-shlib/Remarks.def lib\LLVMRemarks.lib lib\LLVMSupport.lib psapi.lib shell32.lib ole32.lib uuid.lib advapi32.lib delayimp.lib -delayload:shell32.dll -delayload:ole32.dll lib\LLVMDemangle.lib kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib /MANIFEST /MANIFESTFILE:bin\Remarks.dll.manifest" failed (exit code 1) with the following output: lld-link: warning: ignoring unknown argument '-fprofile-generate='C:\src\llvm.monorepo\build.foo\profiles'' lld-link: error: relocation against symbol in discarded section: __profd_?append@?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@QEAAAEAV12@QEBD_K@Z.40465189888 >>> referenced by LLVMSupport.lib(Triple.cpp.obj):(public: static class >>> std::basic_string, class >>> std::allocator> __cdecl llvm::Triple::normalize(class >>> llvm::StringRef)) lld-link: error: relocation against symbol in discarded section: __profd_??$append@PEADX@?$SmallVectorImpl@D@llvm@@QEAAXPEAD0@Z.37713126052 >>> referenced by LLVMSupport.lib(APInt.cpp.obj):(public: void __cdecl >>> llvm::APInt::toString(class llvm::SmallVectorImpl &, unsigned int, >>> bool, bool) const) lld-link: error: relocation against symbol in discarded section: __profd_?assign@?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@QEAAAEAV12@QEBD@Z.40465189888 >>> referenced by LLVMSupport.lib(Debug.cpp.obj):(void __cdecl >>> llvm::setCurrentDebugTypes(char const **, unsigned int)) lld-link: error: relocation against symbol in discarded section: __profd_??$append@PEBDX@?$SmallVectorImpl@D@llvm@@QEAAXPEBD0@Z.37713126052 >>> referenced by LLVMSupport.lib(Path.cpp.obj):(void __cdecl >>> llvm::sys::path::append(class llvm::SmallVectorImpl &, enum >>> llvm::sys::path::Style, class llvm::Twine const &, class llvm::Twine const >>> &, class llvm::Twine const &, class llvm::Twine const &)) >>> referenced by LLVMSupport.lib(Path.cpp.obj):(void __cdecl >>> llvm::sys::path::append(class llvm::SmallVectorImpl &, enum >>> llvm::sys::path::Style, class llvm::Twine const &, class llvm::Twine const >>> &, class llvm::Twine const &, class llvm::Twine const &)) >>> referenced by LLVMSupport.lib(Path.cpp.obj):(void __cdecl >>> llvm::sys::path::replace_extension(class llvm::SmallVectorImpl &, >>> class llvm::Twine const &, enum llvm::sys::path::Style)) >>> referenced by LLVMSupport.lib(Path.cpp.obj):(bool __cdecl >>> llvm::sys::path::remove_dots(class llvm::SmallVectorImpl &, bool, >>> enum llvm::sys::path::Style)) >>> refer
[llvm-bugs] [Bug 42371] New: pgo-instrumented tblgen fails to run on windows
https://bugs.llvm.org/show_bug.cgi?id=42371 Bug ID: 42371 Summary: pgo-instrumented tblgen fails to run on windows Product: new-bugs Version: trunk Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: new bugs Assignee: unassignedb...@nondot.org Reporter: h...@chromium.org CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org, r...@google.com To repro: (I used the monorepo at bb6d0b8e7b0d815710a71b8012438a586e986450 / r364169) C:\src\llvm.monorepo\build.nana>set CC=\src\llvm.monorepo\build.release\bin\clang-cl.exe C:\src\llvm.monorepo\build.nana>set CXX=\src\llvm.monorepo\build.release\bin\clang-cl.exe C:\src\llvm.monorepo\build.nana>cmake -GNinja -DCMAKE_BUILD_TYPE=Release -DLLVM_BUILD_INSTRUMENTED=IR -DLLVM_ENABLE_PROJECTS=clang ../llvm C:\src\llvm.monorepo\build.nana>ninja include/llvm/IR/IntrinsicImpl.inc [191/192] Linking CXX executable bin\llvm-tblgen.exe LINK : warning LNK4044: unrecognized option '/fprofile-generate='C:\src\llvm.monorepo\build.nana\profiles''; ignored msvcrt.lib(initializers.obj) : warning LNK4098: defaultlib 'libcmt.lib' conflicts with use of other libs; use /NODEFAULTLIB:library [192/192] Building IntrinsicImpl.inc... FAILED: include/llvm/IR/IntrinsicImpl.inc cmd.exe /C "cd /D C:\src\llvm.monorepo\build.nana && C:\src\llvm.monorepo\build.nana\bin\llvm-tblgen.exe -gen-intrinsic-impl -I C:/src/llvm.monorepo/llvm/include/llvm/IR -I C:/src/llvm.monorepo/llvm/include C:/src/llvm.monorepo/llvm/include/llvm/IR/Intrinsics.td -o include/llvm/IR/IntrinsicImpl.inc -d include/llvm/IR/IntrinsicImpl.inc.d" ninja: build stopped: subcommand failed. -- 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 13993 in oss-fuzz: llvm/llvm-dwarfdump-fuzzer: Abrt in llvm::llvm_unreachable_internal
Updates: Labels: Deadline-Approaching Comment #2 on issue 13993 by sheriff...@chromium.org: llvm/llvm-dwarfdump-fuzzer: Abrt in llvm::llvm_unreachable_internal https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=13993#c2 This bug is approaching its deadline for being fixed, and will be automatically derestricted within 7 days. If a fix is planned within 2 weeks after the deadline has passed, a grace extension can be granted. - Your friendly Sheriffbot -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 14022 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-loop_vectorize: ASSERT: !(Rewrite.second).empty() && "Expected to find Predicates"
Updates: Labels: Deadline-Approaching Comment #2 on issue 14022 by sheriff...@chromium.org: llvm/llvm-opt-fuzzer--x86_64-loop_vectorize: ASSERT: !(Rewrite.second).empty() && "Expected to find Predicates" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=14022#c2 This bug is approaching its deadline for being fixed, and will be automatically derestricted within 7 days. If a fix is planned within 2 weeks after the deadline has passed, a grace extension can be granted. - Your friendly Sheriffbot -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 13980 in oss-fuzz: llvm/clang-fuzzer: ASSERT: Result.isInvalid() && "C++ binary operator overloading is missing candidates!"
Updates: Labels: Deadline-Approaching Comment #2 on issue 13980 by sheriff...@chromium.org: llvm/clang-fuzzer: ASSERT: Result.isInvalid() && "C++ binary operator overloading is missing candidates!" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=13980#c2 This bug is approaching its deadline for being fixed, and will be automatically derestricted within 7 days. If a fix is planned within 2 weeks after the deadline has passed, a grace extension can be granted. - Your friendly Sheriffbot -- 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 42372] New: Segfault when parsing use of static data member template with deduced type dependent on class template template parameter
https://bugs.llvm.org/show_bug.cgi?id=42372
Bug ID: 42372
Summary: Segfault when parsing use of static data member
template with deduced type dependent on class template
template parameter
Product: clang
Version: trunk
Hardware: PC
OS: All
Status: NEW
Severity: enhancement
Priority: P
Component: Frontend
Assignee: unassignedclangb...@nondot.org
Reporter: era...@eml.cc
CC: llvm-bugs@lists.llvm.org, neeil...@live.com,
richard-l...@metafoo.co.uk
The following example (https://gcc.godbolt.org/z/lrNU6I):
template int C = 0;
template typename T>
struct S
{
template
static auto const X = C>;
int x = X;
};
Produces a stack dump (omitted program arguments flags due to verbosity; see
the Compiler Explorer link above for full message):
Stack dump:
0. Program arguments: ...
1. parser at end of file
2. :4:1: parsing struct/union/class body 'S'
#0 0x55eb13de3c4a llvm::sys::PrintStackTrace(llvm::raw_ostream&)
(/opt/compiler-explorer/clang-trunk-20190624/bin/clang-9+0x2754c4a)
#1 0x55eb13de1a14 llvm::sys::RunSignalHandlers()
(/opt/compiler-explorer/clang-trunk-20190624/bin/clang-9+0x2752a14)
#2 0x55eb13de1b52 SignalHandler(int)
(/opt/compiler-explorer/clang-trunk-20190624/bin/clang-9+0x2752b52)
#3 0x7ff38b971890 __restore_rt
(/lib/x86_64-linux-gnu/libpthread.so.0+0x12890)
clang-9: error: unable to execute command: Segmentation fault (core dumped)
clang-9: error: clang frontend command failed due to signal (use -v to see
invocation)
Compiler returned: 254
The type of the static data member must be deduced (e.g. replacing `auto` with
`int` avoids the segfault; `decltype(auto)` also works in place of `auto`). The
static data member must be used (`X`) to induce the segfault (e.g.
removing `int x = X;` avoids the segfault).
--
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 41908] Allow --disassemble-functions to take demangled names
https://bugs.llvm.org/show_bug.cgi?id=41908 Yuanfang Chen changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #7 from Yuanfang Chen --- Fixed in llvm-svn: 364121 -- 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 41648] Release note: API change to DIBuilder::createFunction etc
https://bugs.llvm.org/show_bug.cgi?id=41648 Tom Stellard changed: What|Removed |Added Resolution|--- |FIXED Fixed By Commit(s)||r363027 Status|NEW |RESOLVED -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 41221] [meta] 8.0.1 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=41221 Bug 41221 depends on bug 41648, which changed state. Bug 41648 Summary: Release note: API change to DIBuilder::createFunction etc https://bugs.llvm.org/show_bug.cgi?id=41648 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 42294] [mssa-loop-dep] wrong code
https://bugs.llvm.org/show_bug.cgi?id=42294 Alina Sbirlea changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #6 from Alina Sbirlea --- Fixed by r363982. -- 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 15478 in oss-fuzz: llvm/llvm-isel-fuzzer--x86_64-O2: ASSERT: isa(Val) && "cast() argument of incompatible type!"
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com, igm...@gmail.com, mit...@google.com, bigchees...@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 OS-Linux Proj-llvm Reported-2019-06-24 Type: Bug New issue 15478 by ClusterFuzz-External: llvm/llvm-isel-fuzzer--x86_64-O2: ASSERT: isa(Val) && "cast() argument of incompatible type!" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=15478 Detailed report: https://oss-fuzz.com/testcase?key=5471576125865984 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: ASSERT Crash Address: Crash State: isa(Val) && "cast() argument of incompatible type!" getEHPadFromPredecessor calculateCXXStateNumbers Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201712190608:201712210617 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5471576125865984 Issue filed automatically. See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for instructions to reproduce this bug locally. -- 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 41221] [meta] 8.0.1 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=41221 Bug 41221 depends on bug 42332, which changed state. Bug 42332 Summary: merge r359094 into 8.0 https://bugs.llvm.org/show_bug.cgi?id=42332 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 42331] [PowerPC64] relocation R_PPC64_REL24 out of range when building LLDB
https://bugs.llvm.org/show_bug.cgi?id=42331 Bug 42331 depends on bug 42332, which changed state. Bug 42332 Summary: merge r359094 into 8.0 https://bugs.llvm.org/show_bug.cgi?id=42332 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 42332] merge r359094 into 8.0
https://bugs.llvm.org/show_bug.cgi?id=42332 Tom Stellard changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED Fixed By Commit(s)|r359094 |r359094 r364209 --- Comment #2 from Tom Stellard --- Merged: r364209 -- 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 41947] Dynamic zero-sized and non-function symbols should be included in disassembly
https://bugs.llvm.org/show_bug.cgi?id=41947 Yuanfang Chen changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #5 from Yuanfang Chen --- fixed in llvm-svn: 364211 -- 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 41221] [meta] 8.0.1 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=41221 Bug 41221 depends on bug 41942, which changed state. Bug 41942 Summary: Merge r360861 to the 8.0 branch https://bugs.llvm.org/show_bug.cgi?id=41942 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 41942] Merge r360861 to the 8.0 branch
https://bugs.llvm.org/show_bug.cgi?id=41942 Tom Stellard changed: What|Removed |Added Fixed By Commit(s)|r360861 |r360861 r364217 Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #4 from Tom Stellard --- Merged: r364217 -- 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 42373] New: AARCH64 ADRP/ADD Code Size Regression between v6 and v7
https://bugs.llvm.org/show_bug.cgi?id=42373 Bug ID: 42373 Summary: AARCH64 ADRP/ADD Code Size Regression between v6 and v7 Product: new-bugs Version: 7.0 Hardware: PC OS: Linux Status: NEW Severity: normal Priority: P Component: new bugs Assignee: unassignedb...@nondot.org Reporter: rrmi...@gmail.com CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org Created attachment 22134 --> https://bugs.llvm.org/attachment.cgi?id=22134&action=edit Example of simple code the reproduces issue In developing for an extremely memory-constrained AARCH64 embedded environment, I noticed a code size regression between versions 6 and 7. Specifically, I see the regression when performing accesses into global structures. Earlier versions (6 and older) would compile a single ADRP/ADD to the front of the global struct at the beginning of a function. Accesses into the structures would then be LDR/STR with offsets to the original calculated address. Later versions are doing ADRP/ADD (followed by STR/LDR) combos on every access into the struct. The issue seems to come up in LLC. The IR produced by versions 6/7/8 seem fundamentally identical. Furthermore, I can feed IR generated by llvm 6 into LLC for versions 6, 7, and 8, and 7/8 produce the larger code.In all cases I am compiling with '-Oz' I have a bit more info in this thread on the llvm mailing list. I have also attached a trivial example in which versions 7 and later will produce larger code than versions 6 and older. LLVM Mailing list thread: http://lists.llvm.org/pipermail/llvm-dev/2019-May/132424.html -- 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 42374] New: Windows Clang fsanitize option crash clang-cl
https://bugs.llvm.org/show_bug.cgi?id=42374 Bug ID: 42374 Summary: Windows Clang fsanitize option crash clang-cl Product: clang Version: 7.0 Hardware: PC OS: other Status: NEW Severity: normal Priority: P Component: C++ Assignee: unassignedclangb...@nondot.org Reporter: adam.alli...@codekfoundries.com CC: blitzrak...@gmail.com, dgre...@apple.com, erik.pilking...@gmail.com, llvm-bugs@lists.llvm.org, richard-l...@metafoo.co.uk Created attachment 22135 --> https://bugs.llvm.org/attachment.cgi?id=22135&action=edit VSCode_All.zip, auto generated files from clang reporter Simple VSCode for Windows with -fsanitize=memory and/or -fsanitize=address will fail to compile. -- 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 42239] GNU binary conditional operator reporting result unused warning
https://bugs.llvm.org/show_bug.cgi?id=42239 Nick Desaulniers changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #2 from Nick Desaulniers --- Fixed: https://reviews.llvm.org/rL363857 Thanks Nathan! -- 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 42375] New: UpgradeDebugInfo doesn't process function-level debug info in lazy load path
https://bugs.llvm.org/show_bug.cgi?id=42375
Bug ID: 42375
Summary: UpgradeDebugInfo doesn't process function-level debug
info in lazy load path
Product: new-bugs
Version: trunk
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P
Component: new bugs
Assignee: unassignedb...@nondot.org
Reporter: jctremou...@gmail.com
CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org
I'm hitting an error (failure to correctly auto-upgrade) processing a .bc file
generated by an older clang with a newer llvm-link. I'm not sure if LTO can
hit the same error or not.
The issue with the older clang is the issue with loop metadata maintenance
during inlining that was fixed with r361149.
***To reproduce:
Start with the cpp code that the testcase which r361149 added
(llvm/test/Transforms/Inline/inlined-loop-metadata.ll) is reduced from:
--inlined.cpp
extern int *Array;
static int bar(unsigned x)
{
int Ret = 0;
for (unsigned i = 0; i < x; ++i)
{
Ret += Array[i] * i;
}
return Ret;
}
int foo(unsigned x)
{
int Bar = bar(x);
return Bar;
}
--end file---
Compile it to a .bc file with clang (older than r361149) and appropriate
optimization flags:
> clang-6.0 -c -emit-llvm -gmlt -O2 inlined.cpp -o inlined.bc
Then use llvm-link (newer than r363725) to link that .bc file (don't need to
link it to anything else):
> llvm-link inlined.bc -o linked.bc
***Observed results:
llvm-link fails with a verifier error on the linked module (i.e. the output of
llvm-link):
!dbg attachment points at wrong subprogram for function
!7 = distinct !DISubprogram(name: "foo", scope: !1, file: !1, line: 12, type:
!8, scopeLine: 13, flags: DIFlagPrototyped, spFlags: DISPFlagDefinition |
DISPFlagOptimized, unit: !0, retainedNodes: !2)
i32 (i32)* @_Z3fooj
br i1 %49, label %50, label %16, !dbg !17, !llvm.loop !23
!24 = !DILocation(line: 5, column: 3, scope: !10)
!10 = distinct !DISubprogram(name: "bar", scope: !1, file: !1, line: 2, type:
!8, scopeLine: 3, flags: DIFlagPrototyped, spFlags: DISPFlagLocalToUnit |
DISPFlagDefinition | DISPFlagOptimized, unit: !0, retainedNodes: !2)
!10 = distinct !DISubprogram(name: "bar", scope: !1, file: !1, line: 2, type:
!8, scopeLine: 3, flags: DIFlagPrototyped, spFlags: DISPFlagLocalToUnit |
DISPFlagDefinition | DISPFlagOptimized, unit: !0, retainedNodes: !2)
llvm-link: error: linked module is broken!
^ the error above is the issue
***Expected results:
llvm-link should have stripped the broken debug info when it read in the input
module. Note that this is the behavior of tools such as llvm-dis (as seen in
the testcase added with r363725, which uses llvm-as):
> llvm-dis inlined.bc -o inlined.ll
!dbg attachment points at wrong subprogram for function
!7 = distinct !DISubprogram(name: "foo", scope: !1, file: !1, line: 12, type:
!8, scopeLine: 13, flags: DIFlagPrototyped, spFlags: DISPFlagDefinition |
DISPFlagOptimized, unit: !0, retainedNodes: !2)
i32 (i32)* @_Z3fooj
br i1 %49, label %50, label %16, !dbg !17, !llvm.loop !23
!24 = !DILocation(line: 5, column: 3, scope: !10)
!10 = distinct !DISubprogram(name: "bar", scope: !1, file: !1, line: 2, type:
!8, scopeLine: 3, flags: DIFlagPrototyped, spFlags: DISPFlagLocalToUnit |
DISPFlagDefinition | DISPFlagOptimized, unit: !0, retainedNodes: !2)
!10 = distinct !DISubprogram(name: "bar", scope: !1, file: !1, line: 2, type:
!8, scopeLine: 3, flags: DIFlagPrototyped, spFlags: DISPFlagLocalToUnit |
DISPFlagDefinition | DISPFlagOptimized, unit: !0, retainedNodes: !2)
llvm-dis: warning: ignoring invalid debug info in inlined.bc
^ the warning above is ok
***Other info:
Looking at this in the debugger, I can see that when UpgradeDebugInfo gets
called in the non-lazy case (the one that llvm-dis always uses, and the one
that llvm-link uses with an explicit -disable-lazy-loading), the verifier
reports the error to it as expected, the warning is emitted, and the debug info
is stripped. But in the lazy case (llvm-link's default), when the verifier
processes the function with the bad debug info, since it hasn't been
materialized, the verifier doesn't visit the debug locs, so the bad debug info
doesn't get stripped but instead gets propagated to the output module, where
the verifier eventually notices it and an error gets reported.
--
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 42376] New: Improve handling of archives without symbol tables
https://bugs.llvm.org/show_bug.cgi?id=42376 Bug ID: 42376 Summary: Improve handling of archives without symbol tables Product: lld Version: unspecified Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: wasm Assignee: unassignedb...@nondot.org Reporter: s...@chromium.org CC: llvm-bugs@lists.llvm.org, s...@chromium.org With wasm its (as with LTO) its fairly common that the system `ar` tool fail to add a symbol table. Currently we ignore such archives. We should try to do better in some way. The ELF backend with process individual archive entries if the are all LTO objects. GNU ld will bail out with "error adding symbols: Archive has no index; run ranlib to add one". -- 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 42377] New: static linkage ignored with alias attribute
https://bugs.llvm.org/show_bug.cgi?id=42377
Bug ID: 42377
Summary: static linkage ignored with alias attribute
Product: clang
Version: 8.0
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P
Component: C
Assignee: unassignedclangb...@nondot.org
Reporter: equinox-l...@diac24.net
CC: blitzrak...@gmail.com, dgre...@apple.com,
erik.pilking...@gmail.com, llvm-bugs@lists.llvm.org,
richard-l...@metafoo.co.uk
Hi,
when compiling this 2-liner:
$ cat > test.c
static int x;
static int y __attribute__((alias("x")));
$ clang-8 -c -o test.o test.c
$ objdump -t test.o
test.o: file format elf64-x86-64
SYMBOL TABLE:
ldf *ABS* test.c
l O .bss 0004 x
g O .bss 0004 y
The "y" symbol ends up global (g) instead of the expected static (l).
ELF visibility attributes don't seem to work either.
Behaviour is the same on
* clang version 8.0.0 (tags/RELEASE_800/final)
* clang version 7.0.1-8 (tags/RELEASE_701/final)
Cheers,
David
--
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 42378] New: ThinLTO index only generates very large index files
https://bugs.llvm.org/show_bug.cgi?id=42378 Bug ID: 42378 Summary: ThinLTO index only generates very large index files Product: libraries Version: trunk Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: Interprocedural Optimizations Assignee: unassignedb...@nondot.org Reporter: l...@inglorion.net CC: llvm-bugs@lists.llvm.org While trying to make distributed ThinLTO work for Chrome, I noticed that the index (.thinlto.bc) files generated by -plugin-opt=thinlto-index-only can get very large. When linking chrome on Linux, every .o file in the link gets a .thinlto.bc file about 10MB in size, which with the number of object files taking part in that link adds up to a lot of disk space. A smaller but hopefully still interesting case is to apply https://crrev.com/c/1654198 to Chromium, configuring with args.gn: is_debug = false is_official_build = true strip_absolute_paths_from_debug_symbols = true and building with ninja base_unittests printing_unittests This gives the following sizes: 137K lto.base_unittests/obj/base/i18n/number_formatting.o 0 lto.base_unittests/obj/base/i18n/number_formatting.o.imports 660K lto.base_unittests/obj/base/i18n/number_formatting.o.thinlto.bc 560 lto.printing_unittests/obj/base/i18n/number_formatting.o 0 lto.printing_unittests/obj/base/i18n/number_formatting.o.imports 124 lto.printing_unittests/obj/base/i18n/number_formatting.o.thinlto.bc (If needed, larger files can be obtained by building different targets.) A quick look with llvm-bcanalyzer --dump shows about 95% of the larger files to be taken up by the strtab. These numbers were obtained with LLVM r363966 and Chromium https://crrev.com/c/1663415. Similar results can be obtained with older versions, so this doesn't appear to be a recent introduction. -- 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 42360] MachOReader "strict-aliasing rule violation" warning
https://bugs.llvm.org/show_bug.cgi?id=42360 Seiya Nuta changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #4 from Seiya Nuta --- Landed: https://reviews.llvm.org/rL364252 -- 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 41221] [meta] 8.0.1 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=41221 Bug 41221 depends on bug 41934, which changed state. Bug 41934 Summary: Please backport r361114 to 8.0 https://bugs.llvm.org/show_bug.cgi?id=41934 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] [Bug 41934] Please backport r361114 to 8.0
https://bugs.llvm.org/show_bug.cgi?id=41934 Tom Stellard changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Fixed By Commit(s)|r361114 |r361114 r364257 --- Comment #3 from Tom Stellard --- Merged: r364257 -- 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 41935] LLDB :: SymbolFile/NativePDB/globals-fundamental.cpp fails on 8.0 branch w/ LLDB_DISABLE_PYTHON
https://bugs.llvm.org/show_bug.cgi?id=41935 Bug 41935 depends on bug 41934, which changed state. Bug 41934 Summary: Please backport r361114 to 8.0 https://bugs.llvm.org/show_bug.cgi?id=41934 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] [Bug 42368] LLVM failed to run 2 Tests 'Clang :: CodeGenCXX/tail-padding.cpp' and 'Clang :: OpenMP/parallel_codegen.cpp' on both x86|debug and x86|release configuration on windows with MSV
https://bugs.llvm.org/show_bug.cgi?id=42368 Reid Kleckner changed: What|Removed |Added Resolution|--- |WORKSFORME Status|NEW |RESOLVED CC||r...@google.com --- Comment #1 from Reid Kleckner --- I attempted to reproduce this, but it works fine. I compiled with VS 2019. Without an error message, it's unclear what's going wrong. If you can get a stack trace of the point of exit, we could do more, but without that, I don't think we can take any action. -- 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 41314] Merge r355033 to the 8.0 branch
https://bugs.llvm.org/show_bug.cgi?id=41314 Tom Stellard changed: What|Removed |Added Status|NEW |RESOLVED Fixed By Commit(s)|r355033 |r355033 r364258 Resolution|--- |FIXED --- Comment #1 from Tom Stellard --- Merged: r364258 -- 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 41221] [meta] 8.0.1 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=41221 Bug 41221 depends on bug 41314, which changed state. Bug 41314 Summary: Merge r355033 to the 8.0 branch https://bugs.llvm.org/show_bug.cgi?id=41314 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 42368] LLVM failed to run 2 Tests 'Clang :: CodeGenCXX/tail-padding.cpp' and 'Clang :: OpenMP/parallel_codegen.cpp' on both x86|debug and x86|release configuration on windows with MSV
https://bugs.llvm.org/show_bug.cgi?id=42368 Richard Smith changed: What|Removed |Added Resolution|WORKSFORME |FIXED --- Comment #2 from Richard Smith --- These tests both had test assertions that failed on 32-bit hosts. For tail-padding.cpp, this was fixed in r364157. For parallel_codegen.cpp, this was fixed in r364189. -- 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 41059] [WebAssembly] Load and store alignment is not disassembled by objdump
https://bugs.llvm.org/show_bug.cgi?id=41059 Wouter van Oortmerssen changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WONTFIX --- Comment #1 from Wouter van Oortmerssen --- This is by design: InstPrinter prints the p2align operand only if it is not the natural alignment: https://github.com/root-project/root/blob/7b4b88c7a234f23ad2f9a93fdd8bf7eba4089b5e/interpreter/llvm/src/lib/Target/WebAssembly/InstPrinter/WebAssemblyInstPrinter.cpp#L195-L203 The AsmParser also implements this same behavior. Presumably whoever originally wrote that code judged that it would reduce on noise, given that 99% of load/stores use natural alignment. -- 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 15483 in oss-fuzz: llvm/clang-fuzzer: Stack-overflow in clang::DeclSpec::Finish
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com, igm...@gmail.com, mit...@google.com, bigchees...@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 OS-Linux Proj-llvm Reported-2019-06-25 Type: Bug New issue 15483 by ClusterFuzz-External: llvm/clang-fuzzer: Stack-overflow in clang::DeclSpec::Finish https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=15483 Detailed report: https://oss-fuzz.com/testcase?key=5734976336691200 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: 0x7ffca824bd80 Crash State: clang::DeclSpec::Finish clang::Parser::ParseTypeQualifierListOpt clang::Parser::ParseBracketDeclarator Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201906220300:201906230301 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5734976336691200 Issue filed automatically. See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for instructions to reproduce this bug locally. -- 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 27149] llvm-config --obj-root and --prefix same output
https://bugs.llvm.org/show_bug.cgi?id=27149 Yuanfang Chen changed: What|Removed |Added Resolution|--- |INVALID Status|NEW |RESOLVED -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
