Re: [lldb-dev] [llvm-dev] [3.9 Release] Release plan and call for testers

On Fri, Jun 10, 2016 at 01:38:22PM -0700, Hans Wennborg via llvm-dev wrote: > Hello everyone, > > It's time to start planning for the 3.9 release. > > Please let me know if you'd like to help providing binaries and > testing for your favourite platform. > > I propose the following schedule: > >

Re: [lldb-dev] [llvm-dev] [3.9 Release] Release plan and call for testers

On Mon, Jun 13, 2016 at 09:14:43AM -0400, Rafael Espíndola wrote: > > The 4.1 release gives us the opportunity to drop support for 3.x > > bitcode formats, so I don't think we should move to 4.x until we have > > older bitcode features that we really want to drop. There should > > probably be a s

Re: [lldb-dev] [llvm-dev] [Release-testers] [3.9 Release] Release Candidate 1 has been tagged

Hi Bernhard, Can you file a bug for this at www.llvm.org/bugs? Make sure to set the version to 3.8 and assign it to me. You should also reference PR27071 in the bug report. -Tom On Mon, Aug 01, 2016 at 09:44:07AM -0700, Hans Wennborg wrote: > Ouch :-( > > Well, if we ever do a 3.8.2, that shou

Re: [lldb-dev] [cfe-dev] [Release-testers] [Openmp-dev] [4.0 Release] Schedule and call for testers

On Mon, Dec 05, 2016 at 06:58:01PM +, Renato Golin via cfe-dev wrote: > On 5 December 2016 at 18:42, Dimitry Andric via Release-testers > wrote: > > Maybe I didn't pay enough attention, but where is the general outline > > for this versioning scheme documented? And are we still going to do >

[lldb-dev] Tips for building with LLVM_LINK_LLVM_DYLIB=ON

Hi, We've been having trouble with some strange lldb failures when building lldb with -DLLVM_LINK_LLVM_DYLIB=ON. For example, this command segfaults with -DLLVM_LINK_LLVM_DYLIB=ON but not if we omit that option: echo "int main(void) { return 0; }" | gcc -x c -g - && \ lldb -b a.out -o 'b ma

[lldb-dev] Reminder: Today is the deadline for 5.0.1 Merge Requests

Hi, Today is the official deadline for making 5.0.1 merge requests. Any merge request made before the end of today is guaranteed to get into the 5.0.1 release if it is approved by the code owner and release manager. After today, I will still accept merge requests, but they must be approved by

Re: [lldb-dev] [cfe-dev] [6.0.0 Release] Scheduling the release

On 12/06/2017 09:28 AM, Hans Wennborg via cfe-dev wrote: > Hello everyone, > > It's time to start making plans for the 6.0.0 release. > > Following our regular schedule, the branch would occur about two weeks > into January, on Wednesday 17 January 2018, with the goal of shipping > early March. T

Re: [lldb-dev] [RFC] LLVM bug lifecycle BoF - triaging

On 10/04/2018 02:55 AM, Kristof Beyls via lldb-dev wrote: > Hi all, > > I’d like to share a few thoughts and analysis results on the LLVM bug life > cycle, especially the reporting/triaging part. > > As one of the few people creating llvm bugzilla accounts when people request > an account, I st

[lldb-dev] Updates on SVN to GitHub migration

TLDR: Official monorepo repository will be published on Tuesday, Oct 23, 2018. After this date, you should modify your workflows to use the monorepo ASAP. Current workflows will be supported for at most 1 more year. Hi, We had 2 round-tables this week at the Developer Meeting to discuss the SVN

Re: [lldb-dev] Updates on SVN to GitHub migration

On 10/19/2018 05:47 PM, Tom Stellard via lldb-dev wrote: > TLDR: Official monorepo repository will be published on > Tuesday, Oct 23, 2018. After this date, you should modify > your workflows to use the monorepo ASAP. Current workflows > will be supported for at most 1 more y

Re: [lldb-dev] [Openmp-dev] [llvm-dev] Updates on SVN to GitHub migration

;one source of truth'? I'd strongly vote for yes, but I'm >> not sure how that's going to work on a technical level. >> >> Thanks, >> Jonas >> >> On 2018-10-20 03:14, Tom Stellard via llvm-dev wrote: >>> On 10/19/2018 05:47 PM, Tom Stel

[lldb-dev] LLVM 7.0.1-rc1 release on Thursday

Hi, I'm planning to do the LLVM 7.0.1-rc1 release on Thursday. This is really just a snapshot release of the current release branch, but It's still important that it gets testing. You still have until Nov 21 to get patches into the final release, so you can keep sending me merge requests. I wou

Re: [lldb-dev] [llvm-dev] [cfe-dev] [RFC] LLVM bug lifecycle BoF - triaging

On 10/31/2018 06:27 AM, Kristof Beyls wrote: > > >> On 26 Oct 2018, at 17:26, Kristof Beyls > > wrote: >> >> >> >>> On 26 Oct 2018, at 16:25, Kristof Beyls via llvm-dev >>> mailto:llvm-...@lists.llvm.org>> wrote: >>> >>> >>> On 26 Oct 2018, at 04:26, Richard Sm

[lldb-dev] 7.0.1-rc2 release has been tagged please begin testing

Hi, The 7.0.1-rc2 release has been tagged and is ready for testing. I forgot to bump the version number to 7.0.1 before I tagged -rc1, which is why we are now on -rc2. Remember, you can continue to submit merge requests up until Nov, 21, so keep testing and submitting fixes. Thanks, Tom __

[lldb-dev] 7.0.1 Release Schedule Update: Merge Request Deadline Nov 30

Hi, The merge request deadline was supposed to be last Wednesday, but there are still a few outstanding issue, so I'm going to push the deadline back to this Friday, Nov 30. If you have any fixes you want to get in, please file bugs and mark them as blockers for the release-7.0.1 metabug. Thanks

[lldb-dev] LLVM 7.0.1-rc3 has been tagged.

Hi, I've just tagged 7.0.1-rc3. This will hopefully be the last release candidate. Please test and report results. Thanks, Tom ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] [cfe-dev] [llvm-dev] Updates on SVN to GitHub migration

es the 'one > source of truth'? I'd strongly vote for yes, but I'm not sure how that's > going to work on a technical level. > > Thanks, > Jonas > > On 2018-10-20 03:14, Tom Stellard via llvm-dev wrote: > > On 10/19/201

[lldb-dev] 7.0.1-final has been tagged

Hi, I've tagged the 7.0.1 final release. Testers may begin uploading binaries. -Tom ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] [Release-testers] [cfe-dev] 7.0.1-final has been tagged

On 01/08/2019 11:36 AM, Ian Tessier via Release-testers wrote: > Can the ubuntu tarballs be published to the download site? They're not > available yet. > These are up on the download site now. -Tom > On Mon, Dec 24, 2018 at 7:38 AM Brian Cain via cfe-dev > mailto:cfe-...@lists.llvm.org>> wro

Re: [lldb-dev] [Release-testers] [cfe-dev] 7.0.1-final has been tagged

On 01/09/2019 05:03 AM, Brian Cain wrote: > > > On Tue, Jan 8, 2019 at 11:25 PM Tom Stellard > wrote: > > On 01/08/2019 11:36 AM, Ian Tessier via Release-testers wrote: > > Can the ubuntu tarballs be published to the download site? They're not > available ye

[lldb-dev] [Github] RFC: linear history vs merge commits

Hi, As part of the migration of LLVM's source code to github, we need to update our developer policy with instructions about how to interact with the new git repository. There are a lot of different topics we will need to discuss, but I would like to start by initiating a discussion about our mer

Re: [lldb-dev] [Openmp-dev] [Github] RFC: linear history vs merge commits

On 01/29/2019 02:48 PM, David Greene wrote: > Tom Stellard via Openmp-dev writes: > >> As part of the migration of LLVM's source code to github, we need to update >> our developer policy with instructions about how to interact with the new git >> repository. There are a lot of different topics w

Re: [lldb-dev] [llvm-dev] [cfe-dev] [Github] RFC: linear history vs merge commits

On 01/30/2019 10:53 PM, Mehdi AMINI via llvm-dev wrote: > > > On Wed, Jan 30, 2019 at 1:19 PM Eric Christopher via cfe-dev > mailto:cfe-...@lists.llvm.org>> wrote: > > On Wed, Jan 30, 2019 at 12:42 PM David Greene via cfe-dev > mailto:cfe-...@lists.llvm.org>> wrote: > > > > Bruc

Re: [lldb-dev] [llvm-dev] [cfe-dev] [Github] RFC: linear history vs merge commits

On 01/31/2019 09:51 AM, Roman Lebedev via llvm-dev wrote: > On Thu, Jan 31, 2019 at 8:29 PM David Greene via cfe-dev > wrote: >> >> Mehdi AMINI writes: >> >>> What is the practical plan to enforce the lack of merges? When we >>> looked into this GitHub would not support this unless also forcing >

[lldb-dev] LLVM 7.1.0 release - Please test the branch

Hi, The release_70 branch is ready for the 7.1.0 release. I have updated the version and pushed a fix for https://bugs.llvm.org/show_bug.cgi?id=39427, which is the only bug we will be fixing in this release. Since this is an ABI breaking changing and also we are introducing a minor version for t

Re: [lldb-dev] [Release-testers] LLVM 7.1.0 release - Please test the branch

On 02/05/2019 08:07 AM, Michał Górny wrote: > On Tue, 2019-02-05 at 07:36 -0800, Tom Stellard via Release-testers > wrote: >> Hi, >> >> The release_70 branch is ready for the 7.1.0 release. I have updated the >> version and pushed a fix for https://bugs.llvm.org/show_bug.cgi?id=39427, >> which is

Re: [lldb-dev] [Release-testers] LLVM 7.1.0 release - Please test the branch

On 02/05/2019 11:26 AM, Michał Górny wrote: > On Tue, 2019-02-05 at 11:23 -0800, Tom Stellard wrote: >> On 02/05/2019 08:07 AM, Michał Górny wrote: >>> On Tue, 2019-02-05 at 07:36 -0800, Tom Stellard via Release-testers >>> wrote: Hi, The release_70 branch is ready for the 7.1.0 rele

Re: [lldb-dev] [Release-testers] LLVM 7.1.0 release - Please test the branch

On 02/05/2019 11:32 AM, Tom Stellard via Release-testers wrote: > On 02/05/2019 11:26 AM, Michał Górny wrote: >> On Tue, 2019-02-05 at 11:23 -0800, Tom Stellard wrote: >>> On 02/05/2019 08:07 AM, Michał Górny wrote: On Tue, 2019-02-05 at 07:36 -0800, Tom Stellard via Release-testers wrote

Re: [lldb-dev] [Release-testers] LLVM 7.1.0 release - Please test the branch

On 02/05/2019 10:41 PM, Michał Górny wrote: > On Tue, 2019-02-05 at 16:13 -0800, Tom Stellard wrote: >> On 02/05/2019 11:32 AM, Tom Stellard via Release-testers wrote: >>> On 02/05/2019 11:26 AM, Michał Górny wrote: On Tue, 2019-02-05 at 11:23 -0800, Tom Stellard wrote: > On 02/05/2019 08:

Re: [lldb-dev] [Release-testers] LLVM 7.1.0 release - Please test the branch

On 02/06/2019 10:57 PM, Michał Górny wrote: > On Wed, 2019-02-06 at 14:09 -0800, Tom Stellard wrote: >> On 02/05/2019 10:41 PM, Michał Górny wrote: >>> On Tue, 2019-02-05 at 16:13 -0800, Tom Stellard wrote: On 02/05/2019 11:32 AM, Tom Stellard via Release-testers wrote: > On 02/05/2019 11:

[lldb-dev] [GitHub] RFC: Enforcing no merge commit policy

Hi, I would like to follow up on the previous thread[1], where there was a consensus to disallow merge commits in the llvm github repository, and start a discussion about how we should enforce this policy. Unfortunately, GitHub does not provide a convenient way to fully enforce this policy. We c

Re: [lldb-dev] [GitHub] RFC: Enforcing no merge commit policy

On 03/20/2019 10:41 AM, Zachary Turner wrote: > > > On Tue, Mar 19, 2019 at 12:00 PM Tom Stellard via lldb-dev > mailto:lldb-dev@lists.llvm.org>> wrote: > > Hi, > > I would like to follow up on the previous thread[1], where there was a > consensus &

Re: [lldb-dev] [cfe-dev] [GitHub] RFC: Enforcing no merge commit policy

om Stellard via cfe-dev > mailto:cfe-...@lists.llvm.org>> wrote: > > On 03/20/2019 10:41 AM, Zachary Turner wrote: > > > > On Tue, Mar 19, 2019 at 12:00 PM Tom Stellard via lldb-dev > mailto:lldb-dev@lists.llvm.org> >

Re: [lldb-dev] [llvm-dev] [cfe-dev] [GitHub] RFC: Enforcing no merge commit policy

On 03/21/2019 10:32 AM, Pavel Labath via llvm-dev wrote: > On 21/03/2019 13:12, David Chisnall via lldb-dev wrote: >> On 20 Mar 2019, at 18:23, Arthur O'Dwyer via cfe-dev >> wrote: >>> >>> Server-side hooks are the answer to this problem. There is no problem. You >>> just use a server-side hook.

[lldb-dev] Release 7.1.0 -rc1 has been tagged

Hi, I've just tagged 7.1.0-rc1. Testers, please begin testing and reporting results. Thanks, Tom ___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] [Openmp-dev] [GitHub] RFC: Enforcing no merge commit policy

On 03/19/2019 11:59 AM, Tom Stellard via Openmp-dev wrote: > Hi, > > I would like to follow up on the previous thread[1], where there was a > consensus > to disallow merge commits in the llvm github repository, and start a > discussion > about how we should enforce this policy. > > Unfortunatel

[lldb-dev] LLVM 7.1.0-final has been tagged

Hi, I've just tagged LLVM 7.1.0-final. Testers, please upload the final binaries. Thanks, Tom ___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

[lldb-dev] LLVM 8.0.1 Release Schedule

Hi, Here is the proposed release schedule for 8.0.1: May 16: -rc1 June 6: -rc2 June 20: -final release If there are no objections, I will post this on the website. If you would like to propose a fix for the 8.0.1 release, please file a bug and put release-8.0.1 in the 'Blocks' field. If you

[lldb-dev] Last call for bug fixes for the 8.0.1 release

Hi, I'm planning to do 8.0.1-rc2 before the end of the week. If you have any fixes you want to get into the release let me know before then. After -rc2, I won't be accepting any new fixes unless they are critical. -Tom ___ lldb-dev mailing list lldb-d

Re: [lldb-dev] Last call for bug fixes for the 8.0.1 release

On 06/05/2019 11:41 AM, Tom Stellard wrote: > Hi, > > I'm planning to do 8.0.1-rc2 before the end of the week. If you have any > fixes > you want to get into the release let me know before then. After -rc2, I won't > be accepting any new fixes unless they are critical. > Update: I'm still wai

[lldb-dev] LLVM 8.0.1-rc2 has been tagged

Hi, I've tagged the 8.0.1-rc2 release, testers please begin testing and upload your binaries. There are still a few more bug fixes that I need to merge, so I'm planning to do one more release candidate before 8.0.1-final. -Tom ___ lldb-dev mailing list

[lldb-dev] LLVM 8.0.1-rc3

Hi, I've just tagged LLVM 8.0.1-rc3. Testers, please begin testing and report results. -Tom ___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

[lldb-dev] 8.0.1-rc4 release has been tagged.

Hi, I've tagged the 8.0.1-rc4 release, please begin testing. This will (hopefully) be the last release candidate. If all goes well, I will tag the final release next Wednesday. -Tom ___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.

[lldb-dev] Reminder: SVN will be retired on Oct 21, 2019 -- Please migrate your workflows to github ASAP.

Hi, We are still on track to retire SVN and complete the transition to GitHub by Oct 21, 2019 (This year's US Dev Meeting). Even though this 3+ months away, it is very important that you begin to migrate your workflows to GitHub as soon as possible. For developers, this means using the git-llvm

Re: [lldb-dev] Reminder: SVN will be retired on Oct 21, 2019 -- Please migrate your workflows to github ASAP.

On 07/12/2019 10:29 AM, paul.robin...@sony.com wrote: > Hi Tom, > > Thanks for driving this! It's a big project and it's great to see > the progress being made on it. My org's adaptation to the monorepo > is in progress as we speak. > > I had two hopefully easy questions. > 1) Can we get a link

Re: [lldb-dev] [Release-testers] 8.0.1-rc4 release has been tagged.

On 07/15/2019 05:40 PM, Brian Cain wrote: > I noticed tests that didn't terminate on ubuntu-14.04 x86_64. Is PR40761 > gating this release? > We weren't able to get a fix for that unfortunately. -Tom > On Fri, Jul 12, 2019 at 2:21 PM Dimitry Andric via Release-testers > mailto:release-test...

[lldb-dev] 8.0.1-final has been tagged

Hi, The 8.0.1 final release has been tagged. Testers please upload the final binaries. -Tom ___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

[lldb-dev] Instructions for requesting GitHub commit access

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 Oct

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

[lldb-dev] GitHub Migration Schedule and Plans

Hi, We're less than 2 weeks away from the developer meeting, so I wanted to give an update on the GitHub migration and what's (hopefully) going to happen during the developer meeting. Everyone who has added their information to the github-usernames.txt file in SVN before today should have receive

Re: [lldb-dev] [Openmp-dev] GitHub Migration Schedule and Plans

On 10/09/2019 10:16 PM, Tom Stellard via Openmp-dev wrote: > Hi, > > We're less than 2 weeks away from the developer meeting, so I wanted to > give an update on the GitHub migration and what's (hopefully) going to > happen during the developer meeting. > > Everyone who has added their information

Re: [lldb-dev] [cfe-dev] GitHub Migration Schedule and Plans

On 10/09/2019 11:05 PM, Mehdi AMINI wrote: > > > On Wed, Oct 9, 2019 at 10:16 PM Tom Stellard via cfe-dev > mailto:cfe-...@lists.llvm.org>> wrote: > > Hi, > > We're less than 2 weeks away from the developer meeting, so I wanted to > give an update on the GitHub migration and what's

Re: [lldb-dev] [cfe-dev] GitHub Migration Schedule and Plans

On 10/10/2019 11:40 AM, Mehdi AMINI wrote: > > > On Thu, Oct 10, 2019 at 10:59 AM Tom Stellard > wrote: > > On 10/09/2019 11:05 PM, Mehdi AMINI wrote: > > > > > > On Wed, Oct 9, 2019 at 10:16 PM Tom Stellard via cfe-dev > mailto:cfe-...@lists.llvm.or

Re: [lldb-dev] [llvm-dev] [cfe-dev] GitHub Migration Schedule and Plans

On 10/10/2019 03:50 PM, Mehdi AMINI wrote: > > > On Thu, Oct 10, 2019 at 1:14 PM Jordan Rupprecht > wrote: > > > > On Thu, Oct 10, 2019 at 12:29 PM Tom Stellard via llvm-dev > mailto:llvm-...@lists.llvm.org>> wrote: > > On 10/10/2019 11:40 AM, Mehdi

[lldb-dev] How soon after the GitHub migration should committing with git-llvm become optional?

Hi, I mentioned this in my email last week, but I wanted to start a new thread to get everyone's input on what to do about the git-llvm script after the GitHub migration. The original plan was to require the use of the git-llvm script when committing to GitHub even after the migration was complet

Re: [lldb-dev] [cfe-dev] How soon after the GitHub migration should committing with git-llvm become optional?

On 10/15/2019 12:20 AM, Roman Lebedev wrote: > On Tue, Oct 15, 2019 at 10:14 AM Tom Stellard via cfe-dev > wrote: >> >> Hi, >> >> I mentioned this in my email last week, but I wanted to start a new >> thread to get everyone's input on what to do about the git-llvm script >> after the GitHub migrat

Re: [lldb-dev] [cfe-dev] How soon after the GitHub migration should committing with git-llvm become optional?

On 10/15/2019 11:51 AM, Lei Huang wrote: > On 10/15/2019 12:20 AM, Roman Lebedev wrote: >> On Tue, Oct 15, 2019 at 10:14 AM Tom Stellard via cfe-dev >> wrote: >>> >>> Hi, >>> >>> I mentioned this in my email last week, but I wanted to start a new >>> thread to get everyone's input on what to do ab

[lldb-dev] Mailing list changes this week

Hi, We are going to start to switching from SVN commit emails to GitHub commit emails this week. The only real change you should notice is that the revision number in the subject will be replaced with a git hash and the diff links in the email will point to GitHub. Otherwise the content and form

Re: [lldb-dev] [cfe-dev] Mailing list changes this week

On 10/15/2019 09:24 PM, Mehdi AMINI wrote: > Hi Tom. > > One issue with this is that we don't have a clear "ordering" from linear > revision numbers from these emails. Have we looked into continuing to > generate our own emails per commits instead so that we control the format? > This actually

Re: [lldb-dev] [cfe-dev] Mailing list changes this week

On 10/15/2019 09:44 PM, Mehdi AMINI wrote: > > > On Tue, Oct 15, 2019 at 9:33 PM Tom Stellard > wrote: > > On 10/15/2019 09:24 PM, Mehdi AMINI wrote: > > Hi Tom. > > > > One issue with this is that we don't have a clear "ordering" from > linear revis

Re: [lldb-dev] [llvm-dev] [cfe-dev] Mailing list changes this week

On 10/16/2019 07:31 AM, Roman Lebedev wrote: > +1, please. > > Also, putting a tag on the *first* commit in the repo, > and doing `git describe --match FIRST_COMMIT_TAG` will be *great*! > Do we need to add a tag or is `git rev-list --count HEAD` good enough? -Tom > Roman. > > On Wed, Oct 16

Re: [lldb-dev] [llvm-dev] [cfe-dev] Mailing list changes this week

On 10/16/2019 12:02 PM, Roman Lebedev wrote: > On Wed, Oct 16, 2019 at 9:55 PM Tom Stellard wrote: >> >> On 10/16/2019 07:31 AM, Roman Lebedev wrote: >>> +1, please. >>> >>> Also, putting a tag on the *first* commit in the repo, >>> and doing `git describe --match FIRST_COMMIT_TAG` will be *great*

Re: [lldb-dev] [cfe-dev] Mailing list changes this week

On 10/16/2019 07:23 AM, Robinson, Paul wrote: > +1. And put it in the email (subject?). While it’s possible to derive a > count from a hash manually, better to have it in the email in the first > place. You can’t rely on order-of-email-delivery to reflect order-of-commit. > I spent some time

Re: [lldb-dev] [cfe-dev] Mailing list changes this week

On 10/16/2019 05:51 PM, Mehdi AMINI wrote: > > > On Wed, Oct 16, 2019 at 5:46 PM Tom Stellard > wrote: > > On 10/16/2019 07:23 AM, Robinson, Paul wrote: > > +1. And put it in the email (subject?). While it’s possible to derive > a count from a hash manuall

[lldb-dev] GitHub Migration Update

Hi, We are going to postpone the migration to Tuesday night PDT. I'll send out another email tomorrow when we start the process. Thanks, Tom ___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

[lldb-dev] GitHub Migration Starting Now

Hi, We're getting ready to start migrating to GitHub. SVN will be moved to read-only now and we'll begin the process of turning on GitHub commit access. I'll send an email when we're done. -Tom ___ lldb-dev mailing list lldb-dev@lists.llvm.org http

Re: [lldb-dev] [Openmp-dev] GitHub Migration Starting Now

On 10/22/2019 09:08 AM, Tom Stellard via Openmp-dev wrote: > Hi, > > We're getting ready to start migrating to GitHub. SVN will be moved to > read-only now and we'll > begin the process of turning on GitHub commit access. I'll send an email > when we're done. > The migration is complete now.

Re: [lldb-dev] [cfe-dev] [Openmp-dev] GitHub Migration Starting Now

On 10/23/2019 01:57 AM, Mikael Holmén wrote: > On Tue, 2019-10-22 at 09:57 -0700, Tom Stellard via cfe-dev wrote: >> On 10/22/2019 09:08 AM, Tom Stellard via Openmp-dev wrote: >>> Hi, >>> >>> We're getting ready to start migrating to GitHub. SVN will be >>> moved to read-only now and we'll >>> beg

[lldb-dev] GitHub committers moving from Collaborators to Team Members

Hi, I just sent out invites to all current LLVM 'Collaborators' on GitHub inviting them to be 'Team Members'. As 'Team Members', it will be much easier for us to manage permissions across the entire group of committers. Unfortunately, we can't just directly move people, so you will have to accept

Re: [lldb-dev] issue with lldb9 and python3.5

+ lldb-dev On 10/28/2019 07:06 AM, Tom Stellard wrote: > On 10/28/2019 03:50 AM, Romaric Jodin via lldb-dev wrote: >> Hi everyone, >> >> I have lldb crashing since I've updated to lldb9. Seems like there is a >> issue with python3.5. Everything seems to work fine with python3.7. >> Am I missing s

Re: [lldb-dev] issue with lldb9 and python3.5

-Tom > On Mon, Oct 28, 2019 at 7:06 AM Tom Stellard via lldb-dev > wrote: >> >> + lldb-dev >> >> On 10/28/2019 07:06 AM, Tom Stellard wrote: >>> On 10/28/2019 03:50 AM, Romaric Jodin via lldb-dev wrote: >>>> Hi everyone, >>>> >&g

[lldb-dev] RFC: Using GitHub Actions for CI testing on the release/* branches

Hi, I would like to start using GitHub Actions[1] for CI testing on the release/* branches. As far as I know we don't have any buildbots listening to the release branches, and I think GitHub Actions are a good way for us to quickly bring-up some CI jobs there. My proposal is to start by adding t

Re: [lldb-dev] [cfe-dev] RFC: Using GitHub Actions for CI testing on the release/* branches

to add an lldb builder. Would you be able to provide me with the cmake arguments plus a check target where all tests are expected to pass? Thanks, Tom > Thanks, > Jonas > > On Tue, Nov 12, 2019 at 2:35 AM Hans Wennborg via cfe-dev > wrote: >> >> On Tue, Nov 12, 20

[lldb-dev] 9.0.1 Release Schedule

Hi, Here is the planned schedule for the 9.0.1 Release: Nov 22: -rc1 Dec 2: -rc2/Deadline to request backports Dec 9: 9.0.1-final If you want to make sure a fix makes it into the 9.0.1 release, please file a bug at bugs.llvm.org and mark it as a blocker for the release-9.0.1 meta-bug. -Tom _

Re: [lldb-dev] RFC: Using GitHub Actions for CI testing on the release/* branches

On 11/11/2019 04:32 PM, Tom Stellard wrote: > Hi, > > I would like to start using GitHub Actions[1] for CI testing on the release/* > branches. As far as I know we don't have any buildbots listening to the > release branches, and I think GitHub Actions are a good way for us to quickly > bring-up

Re: [lldb-dev] [Openmp-dev] RFC: Using GitHub Actions for CI testing on the release/* branches

> Hi Tom, > > This sounds very interesting! +1 from me. > What does this imply for the release testers? > Would it be possible / desirable for us to add self-hosted runners for > other architectures? I'm assuming GitHub only provides x86, right? I > totally missed any details about that in their do

[lldb-dev] LLVM 9.0.1-rc1 Release has been tagged

Hi, I've tagged the LLVM 9.0.1-rc1 release. Testers can begin testing and upload binaries. I've also updated the test-release.sh script to pull from GitHub instead of SVN, if you run into any issues with the new script, let me know. -Tom ___ lldb-dev

Re: [lldb-dev] [Release-testers] LLVM 9.0.1-rc1 Release has been tagged

On 11/25/2019 11:35 PM, Tobias Hieta wrote: > Hello, > > I built for macOS - I can't upload via SFTP since I never got that > access. But the build can be downloaded here: > https://drive.google.com/file/d/1qULDWqHK5s1dHiCyS32BE2ZgxaTjlSSu/view?usp=sharing > > the SHA256 is: > 646b0acae090d09d74

[lldb-dev] LLVM 9.0.1-rc2 has been tagged

Hi, I've tagged LLVM 9.0.1-rc2. Testers can begin testing and uploading binaries. If all goes well, this will be the last -rc. -Tom ___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

[lldb-dev] LLVM 9.0.1-rc3 has been tagged

Hi, I've just tagged LLVM 9.0.1-rc3. Testers can begin testing and uploading binaries. This will be the last release candidate unless there is a major problem. I'm planning to tag the final release on Dec 19. -Tom ___ lldb-dev mailing list lldb-dev@

Re: [lldb-dev] [Release-testers] LLVM 9.0.1-rc3 has been tagged

On 12/16/2019 10:30 AM, Dimitry Andric wrote: > On 14 Dec 2019, at 07:34, Tom Stellard via Release-testers > wrote: >> >> I've just tagged LLVM 9.0.1-rc3. Testers can begin testing and uploading >> binaries. This will be the last release candidate unless there is a >> major problem. I'm planni

[lldb-dev] LLVM 9.0.1-final has been tagged

Hi, I've just tagged the 9.0.1-final release. Testers can begin uploading binaries. -Tom ___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] [cfe-dev] LLVM 9.0.1-final has been tagged

On 01/08/2020 09:24 AM, Brian Cain wrote: > Tom, the 9.0.1 final binaries didn't (yet?) make it to the github release > page https://github.com/llvm/llvm-project/releases/tag/llvmorg-9.0.1 > The binaries have been posted now. > I also checked https://releases.llvm.org/ because I recall some de

Re: [lldb-dev] [cfe-dev] LLVM 9.0.1-final has been tagged

On 01/09/2020 09:11 AM, Brian Cain wrote: > > > On Thu, Jan 9, 2020 at 12:29 AM Tom Stellard > wrote: > > On 01/08/2020 09:24 AM, Brian Cain wrote: > > Tom, the 9.0.1 final binaries didn't (yet?) make it to the github > release page https://github.com/llvm/l

Re: [lldb-dev] [cfe-dev] LLVM 9.0.1-final has been tagged

On 01/14/2020 08:59 AM, Russell Gallop wrote: > Hi Tom, Hans, > > I can't see LLVM-9.0.1-win*.exe from Hans on the GitHub release page > (https://github.com/llvm/llvm-project/releases/tag/llvmorg-9.0.1). Is this > still in progress? > Hans did you upload these? I don't see them on the server.

Re: [lldb-dev] [llvm-dev] RFC: Switching from Bugzilla to Github Issues

On 10/24/2019 07:54 PM, James Y Knight via llvm-dev wrote: > We held a round-table at the llvm dev conference about what other pieces of > Github infrastructure we may want to use. This thread in particular is about > switching to github issue tracking. Use of other parts of Github > functionali

Re: [lldb-dev] [cfe-dev] [llvm-dev] RFC: Switching from Bugzilla to Github Issues

On 01/30/2020 10:24 AM, Aaron Ballman wrote: > On Thu, Jan 30, 2020 at 1:21 PM Tom Stellard via cfe-dev > wrote: >> >> On 10/24/2019 07:54 PM, James Y Knight via llvm-dev wrote: >>> We held a round-table at the llvm dev conference about what other pieces of >>> Github infrastructure we may want t

Re: [lldb-dev] [cfe-dev] [llvm-dev] RFC: Switching from Bugzilla to Github Issues

On 01/30/2020 10:48 AM, Mehdi AMINI wrote: > Hi, > > > > > On Thu, Jan 30, 2020 at 10:21 AM Tom Stellard via cfe-dev > mailto:cfe-...@lists.llvm.org>> wrote: > > On 10/24/2019 07:54 PM, James Y Knight via llvm-dev wrote: > > We held a round-table at the llvm dev conference about what

Re: [lldb-dev] [llvm-dev] [cfe-dev] RFC: Switching from Bugzilla to Github Issues

On 01/31/2020 01:21 AM, James Henderson wrote: > My only concern is the ability to get auto-subscribed onto issues for > specific tools (i.e. the setup I currently have). If that can be resolved in > a satisfactory manner, then I'm all for this (although less than two weeks > seems like a rather

Re: [lldb-dev] [llvm-dev] [cfe-dev] RFC: Switching from Bugzilla to Github Issues

On 01/30/2020 12:47 PM, David Major wrote: > Would it make sense to wait until 10.0.0 is released, in order to keep all > the blockers in one place? > Yes, I think this makes sense, let's postpone until then. -Tom > > > On Thu, Jan 30, 2020 at 1:32 PM Tom Stellard via llvm-dev > mailto:llvm

Re: [lldb-dev] [llvm-dev] [cfe-dev] RFC: Switching from Bugzilla to Github Issues

On 02/10/2020 07:40 PM, Tom Stellard wrote: > On 01/30/2020 12:47 PM, David Major wrote: >> Would it make sense to wait until 10.0.0 is released, in order to keep all >> the blockers in one place? >> > > Yes, I think this makes sense, let's postpone until then. > Hi, 10.0.0-rc4 was just releas

Re: [lldb-dev] [cfe-dev] [llvm-dev] RFC: Switching from Bugzilla to Github Issues

On 03/16/2020 08:00 AM, James Henderson wrote: > > > On Mon, 16 Mar 2020 at 14:44, Tom Stellard via cfe-dev > mailto:cfe-...@lists.llvm.org>> wrote: > > On 02/10/2020 07:40 PM, Tom Stellard wrote: > > On 01/30/2020 12:47 PM, David Major wrote: > >> Would it make sense to wait until

Re: [lldb-dev] [llvm-dev] [cfe-dev] RFC: Switching from Bugzilla to Github Issues

On 03/16/2020 10:13 AM, Florian Hahn wrote: > Hi, > >> On Mar 16, 2020, at 14:43, Tom Stellard via llvm-dev >> mailto:llvm-...@lists.llvm.org>> wrote: >> >> I've also implemented a notification system using GitHub actions that will >> make >> it possible to subscribe to individual issue tags, so

Re: [lldb-dev] [cfe-dev] [llvm-dev] RFC: Switching from Bugzilla to Github Issues

On 03/16/2020 11:09 PM, Roman Lebedev wrote: > On Tue, Mar 17, 2020 at 6:07 AM Tom Stellard via cfe-dev > wrote: >> >> On 03/16/2020 10:13 AM, Florian Hahn wrote: >>> Hi, >>> On Mar 16, 2020, at 14:43, Tom Stellard via llvm-dev mailto:llvm-...@lists.llvm.org>> wrote: I've also

Re: [lldb-dev] [cfe-dev] [llvm-dev] RFC: Switching from Bugzilla to Github Issues

On 03/17/2020 06:39 AM, Roman Lebedev wrote: > On Tue, Mar 17, 2020 at 4:35 PM Tom Stellard wrote: >> >> On 03/16/2020 11:09 PM, Roman Lebedev wrote: >>> On Tue, Mar 17, 2020 at 6:07 AM Tom Stellard via cfe-dev >>> wrote: On 03/16/2020 10:13 AM, Florian Hahn wrote: > Hi, > >

Re: [lldb-dev] [cfe-dev] [llvm-dev] RFC: Switching from Bugzilla to Github Issues

On 03/16/2020 10:18 AM, Roman Lebedev wrote: > On Mon, Mar 16, 2020 at 8:13 PM Florian Hahn via cfe-dev > wrote: >> >> Hi, >> >> On Mar 16, 2020, at 14:43, Tom Stellard via llvm-dev >> wrote: >> >> I've also implemented a notification system using GitHub actions that will >> make >> it possible

Re: [lldb-dev] [cfe-dev] [llvm-dev] RFC: Switching from Bugzilla to Github Issues

On 03/16/2020 07:53 AM, Aaron Ballman wrote: > On Mon, Mar 16, 2020 at 10:44 AM Tom Stellard via cfe-dev > wrote: >> >> On 02/10/2020 07:40 PM, Tom Stellard wrote: >>> On 01/30/2020 12:47 PM, David Major wrote: Would it make sense to wait until 10.0.0 is released, in order to keep all t

[lldb-dev] Is ppc64 big-endian supported on Linux

Hi, I've been looking at lldb on ppc64 big-endian, and I noticed that big-endian binary detection was broken about 2.5 years ago by this commit: https://github.com/llvm/llvm-project/commit/37b1d7b36fa144b0733dfc1659defe80cf384b15 Even with that fixed, breakpoints on ppc64 big-endian seem to be i

[lldb-dev] RFC: Switching from Bugzilla to Github Issues [UPDATED]

Hi, I wanted to continue discussing the plan to migrate from Bugzilla to Github. It was suggested that I start a new thread and give a summary of the proposal and what has changed since it was originally proposed in October. == Here is the original proposal: http://lists.llvm.org/pipermail/llvm-

Re: [lldb-dev] [llvm-dev] RFC: Switching from Bugzilla to Github Issues [UPDATED]

On 04/20/2020 12:49 PM, Richard Smith wrote: > On Mon, 20 Apr 2020 at 12:31, Tom Stellard via llvm-dev > mailto:llvm-...@lists.llvm.org>> wrote: > > Hi, > > I wanted to continue discussing the plan to migrate from Bugzilla to > Github. > It was suggested that I start a new thread an

  1   2   3   >