Mailing lists matching lists.llvm.org
cfe-commits lists.llvm.orglldb-commits lists.llvm.org
llvm-branch-commits lists.llvm.org
llvm-bugs lists.llvm.org
RE: 3.8 Merge Request: r259776
Hi, last possible ping as changes are required to be merged by tomorrow... Cheers, Jonas > -Original Message- > From: llvm-commits [mailto:llvm-commits-boun...@lists.llvm.org] On Behalf > Of Hahnfeld, Jonas via llvm-commits > Sent: Monday, May 23, 2016 8:13 AM > To: To
Re: [PATCH] D17741: adds __FILE_BASENAME__ builtin macro
On Thu, Mar 3, 2016 at 4:28 PM, Joerg Sonnenberger via cfe-commits < cfe-commits@lists.llvm.org> wrote: > On Thu, Mar 03, 2016 at 02:09:17PM -0800, Nico Weber via cfe-commits wrote: > > On Thu, Mar 3, 2016 at 1:50 PM, Joerg Sonnenberger via cfe-commits < > > cfe-commi
Re: [PATCH][modules][PR26237]
ge rather than only citing the bug number On Jan 30, 2016 6:49 AM, "Vassil Vassilev via cfe-commits" mailto:cfe-commits@lists.llvm.org>> wrote: Attaching a fix to https://llvm.org/bugs/show_bug.cgi?id=26237 Please review.
Re: [cfe-users] General Question
cfe-users@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-users ___ cfe-users mailing list cfe-users@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-users ___ cfe-users mailin
Re: [lldb-dev] [Release-testers] [3.8 Release] 'final' has been tagged
3f68b54a7c9be391c8908b0bb2d67e7a87107dc4 clang+llvm-3.8.0-x86_64-opensuse13.2.tar.xz On Fri, Mar 4, 2016 at 12:07 PM, Brian Cain via Release-testers < release-test...@lists.llvm.org> wrote: > > > On Wed, Mar 2, 2016 at 6:33 PM, Hans Wennborg via Release-testers < > release-test...@
Re: [lldb-dev] unaligned cast in TCPSocket::Connect
t;> >> >> Anyone have any thoughts on this? >> >> >> >> -- >> >> Qualcomm Innovation Center, Inc. >> >> The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a >> Linux Foundation Collaborative Pr
Re: [lldb-dev] [Release-testers] [5.0.0 Release] Release Candidate 1 tagged
agged. >> >> Please build, test and upload binaries to the sftp. Let me know if >> there are any issues. >> >> I'll upload sources, docs, and your binaries to the pre-release >> website once they're ready. >> >> Thanks, >&g
Re: [lldb-dev] Forcing lldb to refresh process state
to remote gdb process stub (via `process plugin packet >>> send`). This works, but if the command alters debuggee state, lldb won't >>> know about it. >>> ___ >>> lldb-dev mailing list >>> lldb-dev@lists.ll
Re: [lldb-dev] [cfe-dev] [Release-testers] [6.0.0 Release] Release Candidate 3 tagged
and upload binaries. >> >> Thanks, >> Hans >> ___ >> Release-testers mailing list >> release-test...@lists.llvm.org >> http://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
Re: [lldb-dev] [cfe-dev] [7.0.0 Release] rc1 has been tagged
ot familiar with "git llvm", but I suspect it doesn't work for release branches. Can you just svn commit it instead? Thanks, Hans >> -Original Message- >> From: cfe-dev [mailto:cfe-dev-boun...@lists.llvm.org] On Behalf Of Hans >> Wennborg via cfe-dev >
Re: [lldb-dev] "error: summary string parsing error" on Fedora 30
Behavior of the -g variants is probably better discussed on llvm-dev. --paulr > -Original Message- > From: lldb-dev [mailto:lldb-dev-boun...@lists.llvm.org] On Behalf Of Greg > Clayton via lldb-dev > Sent: Monday, July 22, 2019 5:38 PM > To: Bob Eastbrook > Cc: lldb-
Re: [lldb-dev] [cfe-dev] [llvm-dev] RFC: Switching from Bugzilla to Github Issues [UPDATED]
On Wed, 22 Apr 2020 at 09:45, Philip Reames via cfe-dev < cfe-...@lists.llvm.org> wrote: > On 4/21/20 6:50 PM, Richard Smith wrote: > > On Tue, 21 Apr 2020 at 17:00, Tom Stellard via llvm-dev < > llvm-...@lists.llvm.org> wrote: > >> On 04/21/2020 03:36 PM,
Re: r326168 - Attempt to fix greendragon bot after r326141
ary 26, 2018 at 9:51 PM > To: Shoaib Meenai > Cc: Zachary Turner , "cfe-commits@lists.llvm.org" > , Reid Kleckner > Subject: Re: r326168 - Attempt to fix greendragon bot after r326141 > > Yep. > > > On Feb 26, 2018, at 9:50 PM, Shoaib Meenai <mailto:smee.
Re: [lldb-dev] [cfe-dev] [llvm-dev] FYI: Landing the initial draft for an LLVM Code of Conduct
nts to the board, etc. If none of that works, getting out of here is the obvious choice. But that will take an impressive amount of abuse and carelessness, and the community will be already fragmented by then. My tuppence. Renato On 30 Jun 2016 11:11 p.m., "Daniel Berlin via cfe-dev&qu
Re: [PATCH] D31363: [libc++] Remove cmake glob for source files
There’s clearly a need to reuse certain low level things and not keep > reinventing the wheel > On Wed, Oct 4, 2017 at 9:22 PM Duncan P. N. Exon Smith <mailto:dexonsm...@apple.com>> wrote: > Thanks correct. > > > On Oct 4, 2017, at 18:49, Shoaib Meenai via Phab
Re: Patch bug 27628 (clang-tidy should exit with a failure code when there are errors)
er via llvm-commits wrote: Hello. I've fixed the bug 27628: https://bugs.llvm.org/show_bug.cgi?id=27628 I attached the patch. Thanks. ___ llvm-commits mailing list llvm-commits at lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo
Re: [PATCH] D30691: [analyzer] Support for naive cross translational unit analysis
llvm-commits < llvm-comm...@lists.llvm.org> wrote: > > > 2018. márc. 1. 14:58 ezt írta ("Ilya Biryukov" ): > > I replied to a commit in the wrong thread ( > https://reviews.llvm.org/rL326323), sorry. > Here are the important bits: > > This change i
Re: [PATCH] D36112: [ubsan] Have -fsanitize=vptr emit a null check if -fsanitize=null isn't available
Jul 31, 2017 at 4:43 PM, Vedant Kumar via Phabricator via cfe-commits > mailto:cfe-commits@lists.llvm.org>> wrote: > vsk created this revision. > > In r309007, I made -fsanitize=null a hard prerequisite for -fsanitize=vptr. I > did not see the need for the two checks to have
Re: [clang] 43606ef - Suppress an "unused variable" warning in release build
ress an "unused variable" warning in > release build > > Does "isIntegerConstantExpr" have side effects that are desired/necessary? > Otherwise please change this to roll the isIntegerConstantExpr into the > assert (so that it is only executed when asserts are enabled) > > On T
Re: r329445 - Revert "[analyzer] Remove an unused variable"
On Fri, Apr 6, 2018 at 12:16 PM George Karpenkov via cfe-commits > mailto:cfe-commits@lists.llvm.org>> wrote: > Author: george.karpenkov > Date: Fri Apr 6 12:14:05 2018 > New Revision: 329445 > > URL: http://llvm.org/viewvc/llvm-project?rev=329445&view=rev > <ht
Re: [PATCH] D39208: [Analyzer] Do not use static storage to for implementations created in BodyFarm.cpp
> On Oct 30, 2017, at 8:40 AM, David Blaikie wrote: > > > > On Mon, Oct 23, 2017 at 5:01 PM George Karpenkov via Phabricator via > cfe-commits mailto:cfe-commits@lists.llvm.org>> > wrote: > george.karpenkov added a comment. > > @dcoughlin the con
Re: [PATCH] D27180: Testbed and skeleton of a new expression parser
vert my patches since they're pretty self-contained. Sean > On Dec 19, 2016, at 8:55 AM, David Blaikie wrote: > > > > On Thu, Dec 15, 2016 at 2:18 PM Sean Callanan via Phabricator via cfe-commits > mailto:cfe-commits@lists.llvm.org>> wrote: > spyffe updated this
Re: r298027 - [Serialization] Follow-up to r297972, deserialize name/loc in separate statements to make sure they deserialize in defined order.
*b* at the gcc bots, those are the worst… :-P > On Mar 16, 2017, at 6:39 PM, Eric Christopher wrote: > > Also gcc bots fwiw :) > > -eric > > On Thu, Mar 16, 2017 at 6:01 PM Argyrios Kyrtzidis via cfe-commits > mailto:cfe-commits@lists.llvm.org>> wrote: &g
Re: r306692 - Initialize variable and silence potentially uninitialized warning.
constructors that do not mention it. Indeed. Do you have a solution in mind? The only way I see to fix this is by using an llvm::Optional. On Thu, Jun 29, 2017 at 9:08 AM, Vassil Vassilev via cfe-commits mailto:cfe-commits@lists.llvm.org>> wrote: Author: vvassilev Date: Thu Jun 29 09
RE: [ReviewRequest] [Sema/Parser] GCC Compatibility Patch: Support for __final specifier
Thanks for the quick review! I’ve updated the patch with the name changes in the attached diff file. From: David Majnemer [mailto:david.majne...@gmail.com] Sent: Monday, July 25, 2016 12:40 PM To: Keane, Erich Cc: cfe-commits@lists.llvm.org Subject: Re: [ReviewRequest] [Sema/Parser] GCC
RE: r269411 - [mips] Consult triple's vendor field before using musl's interpreter.
Thanks for pointing that out. Test Added in r269651. - Vasileios From: Daniel Sanders Sent: 13 May 2016 17:33 To: Vasileios Kalintiris; cfe-commits@lists.llvm.org Subject: RE: r269411 - [mips] Consult triple's vendor field before using musl's i
RE: 3.8 Merge Request: r259776
Assuming I got it right... > -Original Message- > From: Alexey Bataev [mailto:a.bat...@hotmail.com] > Sent: Monday, May 30, 2016 1:31 PM > To: Hahnfeld, Jonas > Cc: cfe-commits@lists.llvm.org; Tom Stellard > Subject: Re: 3.8 Merge Request: r259776 > > I can try t
Re: 3.8 Merge Request: r259776
ay, May 30, 2016 1:31 PM > > To: Hahnfeld, Jonas > > Cc: cfe-commits@lists.llvm.org; Tom Stellard > > Subject: Re: 3.8 Merge Request: r259776 > > > > I can try to rebase it to 3.8.1 but Tom wants an approve from Richard. > > Ping him! > > > >
Re: [cfe-users] libclang: Spelling on typedefs lacks namespaces
While it generates some ugly code I found it easier to simply use the canonical names for all types. I spent tens of hours fighting this and never found a good way. On Tuesday, September 27, 2016, Michael via cfe-users < cfe-users@lists.llvm.org> wrote: > Nobody? Wrong list? Any i
Re: [cfe-users] inconsistent compilation error inside constexpr if
Thanks Richard and David for your replies. That was helpful. Regards, Manu From: Richard Smith Sent: Sunday, August 23, 2020 11:56 PM To: Manu agarwal Cc: cfe-users@lists.llvm.org Subject: Re: [cfe-users] inconsistent compilation error inside constexpr if On
Re: [Lldb-commits] [lldb] r341080 - Remove redundant initialization
30, 2018 at 8:39 AM, Adrian Prantl via lldb-commits > mailto:lldb-commits@lists.llvm.org>> wrote: > Author: adrian > Date: Thu Aug 30 08:39:08 2018 > New Revision: 341080 > > URL: http://llvm.org/viewvc/llvm-project?rev=341080&view=rev > <http://llvm.org/view
Re: [Lldb-commits] [lldb] r300610 - Fix Windows bot failure
t;https://msdn.microsoft.com/en-us/library/mt633792.aspx> > > I suspect somebody had suppressed it for some reason. > > On Tue, Apr 18, 2017 at 2:47 PM, Chris Bieneman via lldb-commits > mailto:lldb-commits@lists.llvm.org>> wrote: > Author: cbieneman > Date: Tue Apr 1
Re: [lldb-dev] [Release-testers] [3.9 Release] Release Candidate 3 source and binaries available
+llvm-3.9.0-rc3-x86_64-linux-gnu-debian8.tar.xz No regressions and no new test failures since 3.9.0-rc2. From: Release-testers [release-testers-boun...@lists.llvm.org] on behalf of Hans Wennborg via Release-testers [release-test...@lists.llvm.org] Sen
Re: [lldb-dev] [Release-testers] [3.9 Release] Release Candidate 3 source and binaries available
__ > From: Release-testers [release-testers-boun...@lists.llvm.org] on behalf of > Hans Wennborg via Release-testers [release-test...@lists.llvm.org] > Sent: 26 August 2016 22:29 > To: llvm-dev; cfe-dev; LLDB Dev; openmp-dev (openmp-...@lists.llvm.org) > Cc: Relea
Re: [lldb-dev] Python3 compatibility for the API
S and minor version are you planning to use? > > On Mon, Aug 29, 2016 at 3:15 PM Peter Gebhard via lldb-dev > mailto:lldb-dev@lists.llvm.org>> wrote: > Hello, > > I am developing a tool which is written in Python3 due to its use of some > libraries which require it. I
Re: [lldb-dev] [Release-testers] [3.9 Release] 'final' has been tagged
> problem. I'll run it tomorrow and I'll report back *if* there's any > unexpected problem. > > - V. Kalintiris > ____ > From: Release-testers [release-testers-boun...@lists.llvm.org] on behalf of > Hans Wennborg via Release-t
Re: [lldb-dev] LLDB 4.0.0 crashes on Windows 7
I have never seen either of those problems, but I can test it out and see if I can reproduce. On Tue, Dec 6, 2016 at 7:59 AM Eli Zaretskii via lldb-dev < lldb-dev@lists.llvm.org> wrote: > > Date: Tue, 15 Nov 2016 18:08:03 +0200 > > Cc: lldb-dev@lists.llvm.org > > From: El
Re: [lldb-dev] LLDB bare-metal and 'load' command
: lldb-dev [mailto:lldb-dev-boun...@lists.llvm.org] On Behalf Of Abid, > Hafiz via lldb-dev > Sent: Friday, December 16, 2016 11:00 AM > To: Greg Clayton (gclay...@apple.com) > Cc: lldb-dev@lists.llvm.org > Subject: [lldb-dev] LLDB bare-metal and 'load' command > > Hi Gre
Re: [lldb-dev] Emacs LLDB support & the GDB/MI Interface
Bugzilla at http://bugs.llvm.org . Ted -- Qualcomm Innovation Center, Inc. The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project > -Original Message- > From: lldb-dev [mailto:lldb-dev-boun...@lists.llvm.org] On Behalf Of
Re: [lldb-dev] Phabricator repository
st. --paulr > > - Raphael > Am Mi., 1. Aug. 2018 um 09:11 Uhr schrieb : > > > > Email to llvm-admin should do it. > > --paulr > > > > > -Original Message- > > > From: lldb-dev [mailto:lldb-dev-boun...@lists.llvm.org] On Behalf Of > P
Re: [lldb-dev] [cfe-dev] [7.0.0 Release] rc1 has been tagged
> -Original Message- > From: hwennb...@google.com [mailto:hwennb...@google.com] On Behalf Of Hans > Wennborg > Sent: Friday, August 03, 2018 9:40 AM > To: Robinson, Paul > Cc: Release-testers; llvm-dev; openmp-dev (openmp-...@lists.llvm.org); > LLDB Dev > Subje
Re: [lldb-dev] [Release-testers] 8.0.1-rc4 release has been tagged.
> mailto:release-test...@lists.llvm.org>> > wrote: > > On 11 Jul 2019, at 05:24, Tom Stellard via Release-testers > mailto:release-test...@lists.llvm.org>> > wrote: > > > > I've tagged the 8.0.1-rc4 release, please begin testing. This wi
Re: [lldb-dev] Compiling LLDB on Centos 5 (dont judge me)
it via DCMAKE_C_COMPILER and DCMAKE_CXX_COMPILER flags? It might be a problem with sysroot setup since some headers are not found - you can try to pass a custom sysroot with -DCMAKE_CXX_FLAGS="--sysroot=..." On Tue, Oct 27, 2015 at 2:05 PM, Mark Chandler via lldb-dev mailto:lldb-dev@lists.
Re: [Lldb-commits] [lldb] 8a6333e - [lldb/REPL] Fix unhandled switch case
toast. So just returning an error is fine. Jim > On May 21, 2020, at 11:23 PM, Jonas Devlieghere wrote: > > Jim, does this look correct to you? > > On Thu, May 21, 2020 at 11:22 PM Jonas Devlieghere via lldb-commits > mailto:lldb-commits@lists.llvm.org>> w
Re: [lldb-dev] [llvm-dev] [cfe-dev] What version comes after 3.9? (Was: [3.9 Release] Release plan and call for testers)
as 3.1. On Thu, Jun 16, 2016 at 2:46 AM, Bruce Hoult via lldb-dev < lldb-dev@lists.llvm.org> wrote: > Bug in cmake (or more likely the makefile?), pure and simple. Version > numbers aren't strings, and they aren't floating point numbers, they are a > series of integers se
Re: [lldb-dev] llvm changing line table info from DWARF 2 to DWARF 4
a lot of assumptions that if you’re on Darwin you built with Xcode, which results in lots of tests not executing at all. -Chris > > On Thu, Oct 20, 2016 at 8:09 PM Tim Hammerquist via lldb-dev > mailto:lldb-dev@lists.llvm.org>> wrote: > IIRC, the only reason the LLDB pytho
Re: [lldb-dev] [llvm-dev] [cfe-dev] RFC: Switching from Bugzilla to Github Issues [UPDATED]
On 04/21/2020 03:36 PM, Richard Smith via llvm-dev wrote: > On Tue, 21 Apr 2020 at 11:04, Philip Reames via cfe-dev > mailto:cfe-...@lists.llvm.org>> wrote: > > +1 to James's take > > I'd prefer simplicity of implementation over perfection here. >
Re: Fwd: patch file for bug 38557
cgi?id=38557). > > Thanks, > Owen > > > ___ > cfe-commits mailing list > cfe-commits@lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits ___ cfe-commits maili
Re: clang extra refactor tweaks link patch
ommits > wrote: > > > > A pretty trivial patch to successfully build clang. > > ___ > > cfe-commits mailing list > > cfe-commits@lists.llvm.org > > https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits _
[PATCH] D68076: [AArch64] Enable unwind tables by default for Gnu targets
tellenbach added a comment. This patch would fix PR37240 but is probably not the most optimal solution. For other ideas see http://lists.llvm.org/pipermail/llvm-dev/2019-September/135433.html <http://lists.llvm.org/pipermail/llvm-dev/2019-September/135433.html>. I'll leave this
Re: patch: clean up in EmitValueForIvarAtOffset
uld different from the Qualifiers in an > LValue. No functionality change. > > Please review! > > Nick > > ___ > cfe-commits mailing list > cfe-commits@lists.llvm.org > http://lis
Re: [clang] Honor -fno-sanitize-link-runtime for libclang_rt.asan_static (PR #66414)
elp review this change? > > https://github.com/llvm/llvm-project/pull/66414 > ___ > cfe-commits mailing list > cfe-commits@lists.llvm.org > https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits > _
Re: [PATCH] D67983: [ObjC] Diagnose implicit type coercion from ObjC 'Class' to object pointer types.
gt; Repository: > rG LLVM Github Monorepo > > CHANGES SINCE LAST ACTION > https://reviews.llvm.org/D67983/new/ > > https://reviews.llvm.org/D67983 > > > > ___ > cfe-commits mailing list > cfe-commits@lists.llvm.or
Re: [PATCH] D32914: Introduce Wzero-as-null-pointer-constant.
arns in that case too (?) Also, the warning is off by default. > > > https://reviews.llvm.org/D32914 > > > > ___ > cfe-commits mailing list > cfe-commits@lists.llvm.org > http://
Re: [analyzer] Add support for __builtin_constant_p to BuiltinFunctionChecker
lts: > > Testing Time: 335.63s > Expected Passes : 11769 > Expected Failures : 19 > Unsupported Tests : 50 > > - > felix<0001-analyzer-add-builtin_constant_p-support.patch>_______ > cfe-commits mailing list > cfe-comm
Re: [cfe-users] LLVM docs links broken
/docs/doxygen/html/classllvm_1_1InsertValueInst.html > > -- > Thanks & Regards, > > Dipanjan > ___ > cfe-users mailing list > cfe-users@lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-users signa
Re: [cfe-users] No macros in DI metadata
M1Yf7v > > Please let me know what I'm missing. > > Many Thanks. > > ___ > cfe-users mailing list > cfe-users@lists.llvm.org > https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-users __
Re: [Lldb-commits] [PATCH] D50290: Fix a bug in VMRange
ny pointers to it? > > > Repository: > rLLDB LLDB > > https://reviews.llvm.org/D50290 > > > > ___ > lldb-commits mailing list > lldb-commits@lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commit
Re: [Lldb-commits] [PATCH] D14816: Use thumb instruction set for ldb-server on android arm
dded a comment. > > LGTM > > > http://reviews.llvm.org/D14816 > > > > ___ > lldb-commits mailing list > lldb-commits@lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits __
Re: [Lldb-commits] [PATCH] D18848: Add PDBASTParser and parse type information from PDB
http://reviews.llvm.org/D18848 > > > > ___ > lldb-commits mailing list > lldb-commits@lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits ___ lldb-co
[llvm-bugs] [Bug 28948] New: TestNamespaceDefinitions fails with gcc < 4.9
mal Priority: P Component: All Bugs Assignee: lldb-...@lists.llvm.org Reporter: lab...@google.com CC: llvm-bugs@lists.llvm.org Classification: Unclassified gcc-4.9 is fine. Probably some issue with the generated debug info. -- You are receiv
[llvm-bugs] [Bug 44431] New: TestSettings hang on Windows (a.out hangs)
Priority: P Component: All Bugs Assignee: lldb-...@lists.llvm.org Reporter: compn...@compnerd.org CC: jdevliegh...@apple.com, llvm-bugs@lists.llvm.org It seems that the inferior is not terminating causing the test to timeout. -- You are receiving
[llvm-bugs] [Bug 44432] New: TestSourceManager failure on Windows (unable to set breakpoint by absolute path)
Status: NEW Severity: enhancement Priority: P Component: All Bugs Assignee: lldb-...@lists.llvm.org Reporter: compn...@compnerd.org CC: jdevliegh...@apple.com, llvm-bugs@lists.llvm.org test_set_breakpoint_with_absolute_path
[llvm-bugs] [Bug 51805] New: Cherry-pick 8901f8beea3a70f92be8c0b80313260502f03727 into 13.x branch
Status: NEW Severity: release blocker Priority: P Component: All Bugs Assignee: lldb-...@lists.llvm.org Reporter: omair.jav...@linaro.org CC: jdevliegh...@apple.com, llvm-bugs@lists.llvm.org commit
[llvm-bugs] [Bug 52451] New: SBPlatform::Kill does not seem to work on windows
: normal Priority: P Component: All Bugs Assignee: lldb-...@lists.llvm.org Reporter: lab...@google.com CC: jdevliegh...@apple.com, llvm-bugs@lists.llvm.org TestPlatformKill fails. -- You are receiving this mail because: You are on the CC list for
[llvm-bugs] [Bug 24737] New: CreateDuringInstructionStep is flaky on arm
Priority: P Component: All Bugs Assignee: lldb-...@lists.llvm.org Reporter: lab...@google.com CC: llvm-bugs@lists.llvm.org Classification: Unclassified After a thread.StepInstruction(), thread.GetStopReason() sometimes reports eStopReasonNone
[llvm-bugs] [Bug 24813] New: TestBatchMode is not remote-ready
: P Component: All Bugs Assignee: lldb-...@lists.llvm.org Reporter: lab...@google.com CC: llvm-bugs@lists.llvm.org Classification: Unclassified The test fails for remote platforms as it does not know how to run processes remotely. -- You are
[llvm-bugs] [Bug 24843] New: "ninja lldb-server" on OS X reports "error: unknown target 'lldb-server'"
intosh OS: All Status: NEW Severity: normal Priority: P Component: All Bugs Assignee: lldb-...@lists.llvm.org Reporter: todd.fi...@gmail.com CC: llvm-bugs@lists.llvm.org Classification: Unclassified -
[llvm-bugs] [Bug 39330] New: 7.0.1 backport: Assertion failed: (!m_first_die || m_first_die == m_die_array.front())…
Status: NEW Severity: normal Priority: P Component: All Bugs Assignee: lldb-...@lists.llvm.org Reporter: jan.kratoch...@redhat.com CC: llvm-bugs@lists.llvm.org Please backport: Fix: Assertion failed: (!m_first_die
[llvm-bugs] [Bug 40450] New: LLDB missing link with -lutil
Priority: P Component: All Bugs Assignee: lldb-...@lists.llvm.org Reporter: n...@gmx.com CC: llvm-bugs@lists.llvm.org Fixed in trunk in: [lldb] [Process/NetBSD] Add missing linkage to -lutil https://reviews.llvm.org/D57193 -- You are receiving this mail
[llvm-bugs] [Bug 34419] New: TopLevelExpressionsTestCase-test_top_level_expressions_dwarf fails on fedora
Status: NEW Severity: enhancement Priority: P Component: All Bugs Assignee: lldb-...@lists.llvm.org Reporter: dav...@freebsd.org CC: llvm-bugs@lists.llvm.org It took me quite a bit to reproduce, the log is attached. -- You
[llvm-bugs] [Bug 36741] New: Fix tests which check the lldb-mi -symbol-xxx commands
: normal Priority: P Component: All Bugs Assignee: lldb-...@lists.llvm.org Reporter: v...@apple.com CC: llvm-bugs@lists.llvm.org Virtually everything in TestMiSymbol.py has been xfailed for a while. -- You are receiving this mail because: You are
[llvm-bugs] [Bug 37656] New: lit/Expr/TestIRMemoryMap.test does not work on Windows
: normal Priority: P Component: All Bugs Assignee: lldb-...@lists.llvm.org Reporter: v...@apple.com CC: llvm-bugs@lists.llvm.org lldb-test fails to create a process that's usable by the JIT. -- You are receiving this mail because: You are on t
[llvm-bugs] [Bug 25785] New: TestReturnValue fails remotely windows->android
mal Priority: P Component: All Bugs Assignee: lldb-...@lists.llvm.org Reporter: lab...@google.com CC: llvm-bugs@lists.llvm.org Classification: Unclassified I will XFAIL the test until we get a chance to investigate the root cause. -- You
[llvm-bugs] [Bug 27073] New: TestReturnValue.test_with_python fails with hard float abi on android device
Status: NEW Severity: normal Priority: P Component: All Bugs Assignee: lldb-...@lists.llvm.org Reporter: chy...@google.com CC: llvm-bugs@lists.llvm.org Classification: Unclassified Xfail the test. -- You are receiving
[llvm-bugs] [Bug 27074] New: TestCallUserAnonTypedef.py fails with hard float abi on android arm
Status: NEW Severity: normal Priority: P Component: All Bugs Assignee: lldb-...@lists.llvm.org Reporter: chy...@google.com CC: llvm-bugs@lists.llvm.org Classification: Unclassified xfail the test for hard float abi. -- You are
[llvm-bugs] [Bug 27075] New: TestLldbGdbServer.software_breakpoint_set_and_remove_work fails on android arm with -mthumb
OS: Linux Status: NEW Severity: normal Priority: P Component: All Bugs Assignee: lldb-...@lists.llvm.org Reporter: chy...@google.com CC: llvm-bugs@lists.llvm.org Classification: Unclassified xfail
[llvm-bugs] [Bug 27863] New: TestGlobalVariables.py test_c_global_variables_gmodules() fails on OS X
Status: NEW Severity: normal Priority: P Component: All Bugs Assignee: lldb-...@lists.llvm.org Reporter: todd.fi...@gmail.com CC: llvm-bugs@lists.llvm.org Classification: Unclassified Once http://reviews.llvm.org/D19998 lands
[llvm-bugs] [Bug 31160] New: Merge r283123 into 3.9.1
Component: new bugs Assignee: unassignedb...@nondot.org Reporter: mehdi.am...@apple.com CC: llvm-bugs@lists.llvm.org Classification: Unclassified See http://lists.llvm.org/pipermail/llvm-dev/2016-November/107481.html -- You are receiving this mail because
[lldb-dev] [Bug 25785] New: TestReturnValue fails remotely windows->android
mal Priority: P Component: All Bugs Assignee: lldb-dev@lists.llvm.org Reporter: lab...@google.com CC: llvm-b...@lists.llvm.org Classification: Unclassified I will XFAIL the test until we get a chance to investigate the root cause. -- You
[lldb-dev] [Bug 27073] New: TestReturnValue.test_with_python fails with hard float abi on android device
Status: NEW Severity: normal Priority: P Component: All Bugs Assignee: lldb-dev@lists.llvm.org Reporter: chy...@google.com CC: llvm-b...@lists.llvm.org Classification: Unclassified Xfail the test. -- You are receiving
[lldb-dev] [Bug 27074] New: TestCallUserAnonTypedef.py fails with hard float abi on android arm
Status: NEW Severity: normal Priority: P Component: All Bugs Assignee: lldb-dev@lists.llvm.org Reporter: chy...@google.com CC: llvm-b...@lists.llvm.org Classification: Unclassified xfail the test for hard float abi. -- You are
[lldb-dev] [Bug 27863] New: TestGlobalVariables.py test_c_global_variables_gmodules() fails on OS X
Status: NEW Severity: normal Priority: P Component: All Bugs Assignee: lldb-dev@lists.llvm.org Reporter: todd.fi...@gmail.com CC: llvm-b...@lists.llvm.org Classification: Unclassified Once http://reviews.llvm.org/D19998 lands
[lldb-dev] [Bug 28948] New: TestNamespaceDefinitions fails with gcc < 4.9
mal Priority: P Component: All Bugs Assignee: lldb-dev@lists.llvm.org Reporter: lab...@google.com CC: llvm-b...@lists.llvm.org Classification: Unclassified gcc-4.9 is fine. Probably some issue with the generated debug info. -- You are receiv
[lldb-dev] [Bug 26322] Core load hangs
-dev@lists.llvm.org |hhell...@uk.ibm.com --- Comment #1 from Howard Hellyer --- This looks like a problem reading the signals for each thread from the core file. See the discussion under: http://lists.llvm.org/pipermail/lldb-dev/2016-November/011578.html I'll try to submit a patch sh
[lldb-dev] [Bug 36741] New: Fix tests which check the lldb-mi -symbol-xxx commands
: normal Priority: P Component: All Bugs Assignee: lldb-dev@lists.llvm.org Reporter: v...@apple.com CC: llvm-b...@lists.llvm.org Virtually everything in TestMiSymbol.py has been xfailed for a while. -- You are receiving this mail because: You are
[lldb-dev] [Bug 37656] New: lit/Expr/TestIRMemoryMap.test does not work on Windows
: normal Priority: P Component: All Bugs Assignee: lldb-dev@lists.llvm.org Reporter: v...@apple.com CC: llvm-b...@lists.llvm.org lldb-test fails to create a process that's usable by the JIT. -- You are receiving this mail because: You ar
[lldb-dev] [Bug 37995] New: LLDB only supports GPR registers on Windows
Priority: P Component: All Bugs Assignee: lldb-dev@lists.llvm.org Reporter: sti...@microsoft.com CC: llvm-b...@lists.llvm.org Only GPR registers are supported in LLDB on Windows. There is no support for floating point registers. -- You are receiving
[lldb-dev] [Bug 39330] New: 7.0.1 backport: Assertion failed: (!m_first_die || m_first_die == m_die_array.front())…
Status: NEW Severity: normal Priority: P Component: All Bugs Assignee: lldb-dev@lists.llvm.org Reporter: jan.kratoch...@redhat.com CC: llvm-b...@lists.llvm.org Please backport: Fix: Assertion failed: (!m_first_die
Re: [lldb-dev] [cfe-dev] 7.0.1-final has been tagged
: > > Hi, > > I've tagged the 7.0.1 final release. Testers may begin uploading binaries. > > -Tom > ___ > cfe-dev mailing list > cfe-...@lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev build_llvm_701-f
[lldb-dev] [Bug 40450] New: LLDB missing link with -lutil
Priority: P Component: All Bugs Assignee: lldb-dev@lists.llvm.org Reporter: n...@gmx.com CC: llvm-b...@lists.llvm.org Fixed in trunk in: [lldb] [Process/NetBSD] Add missing linkage to -lutil https://reviews.llvm.org/D57193 -- You are receiving this mail
Re: [lldb-dev] Making LLVM_DEFAULT_TARGET_TRIPLE available to lldb's cmakery
FAULT_TARGET_TRIPLE}) > > string(REGEX MATCH "^[^-]*" LLDB_DEBUGSERVER_ARCH > > "${LLVM_DEFAULT_TARGET_TRIPLE}") > > #else() > > # set(LLDB_DEBUGSERVER_ARCH "") > > #endif() > > > > _____
[lldb-dev] [Bug 44431] New: TestSettings hang on Windows (a.out hangs)
Priority: P Component: All Bugs Assignee: lldb-dev@lists.llvm.org Reporter: compn...@compnerd.org CC: jdevliegh...@apple.com, llvm-b...@lists.llvm.org It seems that the inferior is not terminating causing the test to timeout. -- You are receiving
[lldb-dev] [Bug 44432] New: TestSourceManager failure on Windows (unable to set breakpoint by absolute path)
Status: NEW Severity: enhancement Priority: P Component: All Bugs Assignee: lldb-dev@lists.llvm.org Reporter: compn...@compnerd.org CC: jdevliegh...@apple.com, llvm-b...@lists.llvm.org test_set_breakpoint_with_absolute_path
Re: [lldb-dev] [llvm-dev] LLVM 11.0.1-rc2 has been tagged
wrote: > > Hi, > > I've just tagged LLVM 11.0.1-rc2, hopefully this will be the last > release candidate. Testers can begin testing and uploading binaries. > > -Tom > > ___ > LLVM Developers mailing list > llvm-...@lists
Re: [lldb-dev] LLVM 11.0.1-final has been tagged
Stellard via lldb-dev wrote: > > Hi, > > I've tagged LLVM 11.0.1-final. Testers can upload the final binaries now. > > -Tom > > ___ > lldb-dev mailing list > lldb-dev@lists.llvm.org > https://lists.llvm
Re: [lldb-dev] [Openmp-dev] LLVM 12.0.0-rc5 has been tagged
wrote: > > Hi, > > I've tagged 12.0.0-rc5, testers can begin testing and upload binaries. > > -Tom > > ___ > Openmp-dev mailing list > openmp-...@lists.llvm.org > https://lists.llvm.org/cgi-bin/mailman/listinfo/
[lldb-dev] [Bug 51805] New: Cherry-pick 8901f8beea3a70f92be8c0b80313260502f03727 into 13.x branch
Status: NEW Severity: release blocker Priority: P Component: All Bugs Assignee: lldb-dev@lists.llvm.org Reporter: omair.jav...@linaro.org CC: jdevliegh...@apple.com, llvm-b...@lists.llvm.org commit
[lldb-dev] [Bug 52451] New: SBPlatform::Kill does not seem to work on windows
: normal Priority: P Component: All Bugs Assignee: lldb-dev@lists.llvm.org Reporter: lab...@google.com CC: jdevliegh...@apple.com, llvm-b...@lists.llvm.org TestPlatformKill fails. -- You are receiving this mail because: You are the assignee for
[lldb-dev] [Bug 24737] New: CreateDuringInstructionStep is flaky on arm
Priority: P Component: All Bugs Assignee: lldb-dev@lists.llvm.org Reporter: lab...@google.com CC: llvm-b...@lists.llvm.org Classification: Unclassified After a thread.StepInstruction(), thread.GetStopReason() sometimes reports eStopReasonNone
