Re: [lldb-dev] [Release-testers] [9.0.0 Release] Release Candidate 3 is here
On 30 Aug 2019, at 18:38, Hans Wennborg via Release-testers wrote: > > 9.0.0-rc3 was tagged today from the release_90 branch at r370450. In > the Git monorepo, it's tagged as llvmorg-9.0.0-rc3. For this rc, I used two patches, from: * https://bugs.llvm.org/show_bug.cgi?id=42892 - After r356631, Sanitizer-i386-Test faills to link on FreeBSD * https://bugs.llvm.org/show_bug.cgi?id=42894 - FreeBSD needs -pthread link flag for dynamic ASan tests Uploaded: SHA256 (clang+llvm-9.0.0-rc3-amd64-unknown-freebsd11.tar.xz) = 4b5f1e9c62985fdb397ec66e52a24cef0a20a458cd482f7ae318f6c8aab082b5 SHA256 (clang+llvm-9.0.0-rc3-i386-unknown-freebsd11.tar.xz) = d040218dc6db3a6e5d5e520047582c6b006905221725d9a503697a3b74763f96 Main test results on amd64-freebsd11: Unexpected Passing Tests (6): AddressSanitizer-i386-freebsd-dynamic :: TestCases/interception_failure_test.cc AddressSanitizer-x86_64-freebsd-dynamic :: TestCases/interception_failure_test.cc lldb-Suite :: api/multiple-targets/TestMultipleTargets.py lldb-Suite :: functionalities/data-formatter/data-formatter-skip-summary/TestDataFormatterSkipSummary.py lldb-Suite :: lang/cpp/namespace/TestNamespaceLookup.py lldb-Suite :: python_api/thread/TestThreadAPI.py Failing Tests (401): AddressSanitizer-Unit :: ./Asan-i386-calls-Dynamic-Test/AddressSanitizer.ShadowGapTest AddressSanitizer-Unit :: ./Asan-i386-inline-Dynamic-Test/AddressSanitizer.ShadowGapTest AddressSanitizer-i386-freebsd :: TestCases/Posix/fread_fwrite.cc AddressSanitizer-i386-freebsd-dynamic :: TestCases/Posix/fread_fwrite.cc Builtins-i386-freebsd :: floatundixf_test.c LLDB :: ExecControl/StopHook/stop-hook-threads.test LLDB :: ExecControl/StopHook/stop-hook.test LLDB :: SymbolFile/DWARF/find-basic-function.cpp LLDB :: SymbolFile/DWARF/find-basic-namespace.cpp LLDB :: SymbolFile/DWARF/find-basic-variable.cpp LLDB :: SymbolFile/DWARF/find-variable-file.cpp LLDB :: tools/lldb-mi/exec/exec-next.test LLDB :: tools/lldb-mi/exec/exec-step-instruction.test LLVM :: tools/yaml2obj/elf-override-shoffset.yaml LLVM :: tools/yaml2obj/elf-override-shsize.yaml MemorySanitizer-Unit :: ./Msan-x86_64-Test/MemorySanitizer.SmallPreAllocatedStackThread MemorySanitizer-Unit :: ./Msan-x86_64-Test/MemorySanitizer.bind_getsockname MemorySanitizer-Unit :: ./Msan-x86_64-Test/MemorySanitizer.confstr MemorySanitizer-Unit :: ./Msan-x86_64-Test/MemorySanitizer.mbrtowc MemorySanitizer-Unit :: ./Msan-x86_64-Test/MemorySanitizer.swprintf MemorySanitizer-Unit :: ./Msan-x86_64-Test/MemorySanitizer.valloc MemorySanitizer-Unit :: ./Msan-x86_64-with-call-Test/MemorySanitizer.SmallPreAllocatedStackThread MemorySanitizer-Unit :: ./Msan-x86_64-with-call-Test/MemorySanitizer.bind_getsockname MemorySanitizer-Unit :: ./Msan-x86_64-with-call-Test/MemorySanitizer.confstr MemorySanitizer-Unit :: ./Msan-x86_64-with-call-Test/MemorySanitizer.mbrtowc MemorySanitizer-Unit :: ./Msan-x86_64-with-call-Test/MemorySanitizer.swprintf MemorySanitizer-Unit :: ./Msan-x86_64-with-call-Test/MemorySanitizer.valloc MemorySanitizer-X86_64 :: dtls_test.c SanitizerCommon-asan-i386-FreeBSD :: Posix/devname_r.cc SanitizerCommon-asan-i386-FreeBSD :: Posix/weak_hook_test.cc SanitizerCommon-asan-x86_64-FreeBSD :: Posix/weak_hook_test.cc SanitizerCommon-msan-x86_64-FreeBSD :: FreeBSD/capsicum.cc SanitizerCommon-msan-x86_64-FreeBSD :: Posix/dedup_token_length_test.cc SanitizerCommon-msan-x86_64-FreeBSD :: Posix/weak_hook_test.cc SanitizerCommon-tsan-x86_64-FreeBSD :: FreeBSD/capsicum.cc SanitizerCommon-tsan-x86_64-FreeBSD :: FreeBSD/fdevname.cc SanitizerCommon-tsan-x86_64-FreeBSD :: Posix/arc4random.cc SanitizerCommon-tsan-x86_64-FreeBSD :: Posix/dedup_token_length_test.cc SanitizerCommon-tsan-x86_64-FreeBSD :: Posix/devname.cc SanitizerCommon-tsan-x86_64-FreeBSD :: Posix/devname_r.cc SanitizerCommon-tsan-x86_64-FreeBSD :: Posix/dump_instruction_bytes.cc SanitizerCommon-tsan-x86_64-FreeBSD :: Posix/fpe.cc SanitizerCommon-tsan-x86_64-FreeBSD :: Posix/fputc_putc_putchar.cc SanitizerCommon-tsan-x86_64-FreeBSD :: Posix/fputs_puts.cc SanitizerCommon-tsan-x86_64-FreeBSD :: Posix/fseek.cc SanitizerCommon-tsan-x86_64-FreeBSD :: Posix/fts.cc SanitizerCommon-tsan-x86_64-FreeBSD :: Posix/funopen.cc SanitizerCommon-tsan-x86_64-FreeBSD :: Posix/getfsent.cc SanitizerCommon-tsan-x86_64-FreeBSD :: Posix/getmntinfo.cc SanitizerCommon-tsan-x86_64-FreeBSD :: Posix/getpass.cc SanitizerCommon-tsan-x86_64-FreeBSD :: Posix/getusershell.cc SanitizerCommon-tsan-x86_64-FreeBSD :: Posix/illegal_read_test.cc SanitizerCommon-tsan-x86_64-FreeBSD :: Posix/illegal_write_test.cc SanitizerComm
Re: [lldb-dev] [Openmp-dev] [llvm-dev] [cfe-dev] Instructions for requesting GitHub commit access
On 09/04/2019 07:19 AM, via Openmp-dev wrote: > > >> -Original Message- >> From: llvm-dev [mailto:llvm-dev-boun...@lists.llvm.org] On Behalf Of David >> Zarzycki via llvm-dev >> Sent: Wednesday, September 04, 2019 8:07 AM >> To: David Greene >> Cc: llvm-dev; LLDB Dev; cfe-dev; openmp-dev (openmp-...@lists.llvm.org) >> Subject: Re: [llvm-dev] [cfe-dev] [Openmp-dev] Instructions for requesting >> GitHub commit access >> >> One is expected to use `git llvm push`. For more information, please see: >> >> https://llvm.org/docs/GettingStarted.html#for-developers-to-commit- >> changes-from-git > > FTR, that page is written to describe the current situation (with the > git-to-svn loop behind the scenes), and doesn't say anything about what > happens after the changeover. > > https://bugs.llvm.org/show_bug.cgi?id=42430 does suggest that we will > keep using `git llvm push` after the changeover, and it will just do > different things (like guaranteeing no merge commits get pushed). > --paulr > This is correct, we will continue to use `git llvm push` after transitioning to GitHub. -Tom >> >> >>> On Sep 3, 2019, at 7:06 PM, David Greene via cfe-dev > d...@lists.llvm.org> wrote: >>> >>> What is the expected way to do commits? Do we push directly to master >>> after a rebase? I know there has been talk of using GitHub pull >>> requests and I would be in favor of that. What's the status of those >>> discussions? >>> >>> -David >>> >>> Tom Stellard via Openmp-dev writes: >>> Hi, I've created a text file[1] in the SVN repository that developers can update in order to request commit access to the GitHub repository. All you need to do is add a line in the form of $SVN_USERNAME:$GITHUB_USERNAME Please add your information to this file before SVN becomes readonly on October 21 to avoid a gap in commit access. More details can be >> found in the phabriactor review[2] that updates the developer policy. We will be verifying that the svn committer matches the username in the file, so you can only request access for yourself and not someone else Thanks, Tom [1] https://llvm.org/viewvc/llvm-project/meta/trunk/github- >> usernames.txt?view=markup [2] https://reviews.llvm.org/D66840 ___ Openmp-dev mailing list openmp-...@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/openmp-dev >>> ___ >>> cfe-dev mailing list >>> cfe-...@lists.llvm.org >>> https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev >> >> ___ >> LLVM Developers mailing list >> llvm-...@lists.llvm.org >> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev > ___ > Openmp-dev mailing list > openmp-...@lists.llvm.org > https://lists.llvm.org/cgi-bin/mailman/listinfo/openmp-dev > ___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
[lldb-dev] GDB JIT interface on LLDB for Windows
I'm trying to locate more information about the subject. I'm working on enabling debugging for wasmtime [1]. The wasmtime is a runtime for WebAssembly code -- a JIT, for purpose of this discussion. Currently, I'm successfully generate ELF images to be registered using the JIT interface [2]. It works well on Linux [3] and Mac OS, and now there is a need to extend it to Windows. It will be less work for me (and other JIT vendors) if LLDB on Windows could support ELF/DWARF format. Is or can it be the case? If not, what will be a preferable format for Windows object file image to be used in JIT interface, and will it work via __jit_debug_register_code? Thank you, Yury [1] https://github.com/CraneStation/wasmtime/ [2] https://www-zeuthen.desy.de/unix/unixguide/infohtml/gdb/JIT-Interface.html [3] https://hacks.mozilla.org/2019/09/debugging-webassembly-outside-of-the-browser/ ___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
