Re: [lldb-dev] Mailman->Discourse Migration on February 1, 10am PST

[Tanya Lattner via lldb-dev]

As a reminder, this will be happening this morning. 

Thanks,
Tanya

> On Jan 29, 2022, at 8:29 AM, Tanya Lattner  wrote:
> 
> LLVM Community,
> 
> As referenced in this blog post 
> , we are getting 
> close to the deadline for migration for some Mailman lists to Discourse. If 
> you are receiving this email from a LLVM Mailman list, then this list will be 
> migrating to Discourse on February 1st.
> 
> We have gone through several test runs and feel that we are ready to do the 
> final migration on February 1st starting at 10 am PST. Once the migration 
> begins, the impacted Mailman lists and Discourse will be read only until it 
> has completed.
> 
> Here are the steps of the migration process on February 1st at 10 am PST:
> The Mailman lists that are migrating will be placed in “read-only” mode. No 
> mail will be accepted to the list. 
> Mailman will be shut down while the final archives are collected. We expect 
> this downtime to be about 15 minutes.
> The mailman archives are sent to Discourse for migration (15-20 minutes for 
> data transfer).
> The LLVM DIscourse is put into read-only mode. Given the size of our 
> archives, we expect the import to take 5 hours. 
> Sanity-checks will be made to ensure that everything looks as expected. We 
> estimate this will take 1 hour or less.
> The LLVM Discourse will be opened up again with all the archives imported.
> We will post on Discourse about how things went and any next steps in the 
> “Announcements” category.
> 
> We will use the Discourse Migration website 
>  to communicate where we 
> are in the process. 
> 
> We expect the LLVM Discourse to open by 5pm PST, but realize that even in the 
> best plans, there may be unexpected situations that arise that cause the 
> migration to take longer or possibly be stopped. If that occurs, we will 
> evaluate the best course of action and communicate to the community as 
> described above.
> 
> If you have any questions, please let me know.
> 
> Thanks,
> Tanya

___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] Mailman->Discourse Migration on February 1, 10am PST

[Tanya Lattner via lldb-dev]

Thank you Paul for pointing this out. I will get this information updated 
tonight.

-Tanya

> On Jan 29, 2022, at 9:58 AM, Paul Smith  wrote:
> 
> On Sat, 2022-01-29 at 08:29 -0800, Tanya Lattner via lldb-dev wrote:
>> We will use the Discourse Migration website to communicate where we
>> are in the process.
> 
> Just to point out that the "Setting up email interactions" section on
> this page could use some attention.
> 
> For example the first bullet links to a Mozilla help page which is
> obsolete; it describes modifying user preferences which don't exist in
> the current LLVM Discourse (maybe LLVM is using a newer version?), or
> at least they don't exist in my account.  I can't find any setting
> related to "Send me email notifications when I am active on the site",
> nor can I find any setting like "Mark posts as read when I'm emailed
> about them".
> 
> Also the link at "Quoting previous topics in an reply" points to an
> issue where the answer appears to be changing a site-wide setting, not
> a per-user setting, so there's not much that we can do about it
> individually.
> 

___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

[lldb-dev] Mailman->Discourse Migration on February 1, 10am PST

[Tanya Lattner via lldb-dev]

LLVM Community,

As referenced in this blog post 
, we are getting 
close to the deadline for migration for some Mailman lists to Discourse. If you 
are receiving this email from a LLVM Mailman list, then this list will be 
migrating to Discourse on February 1st.

We have gone through several test runs and feel that we are ready to do the 
final migration on February 1st starting at 10 am PST. Once the migration 
begins, the impacted Mailman lists and Discourse will be read only until it has 
completed.

Here are the steps of the migration process on February 1st at 10 am PST:
The Mailman lists that are migrating will be placed in “read-only” mode. No 
mail will be accepted to the list. 
Mailman will be shut down while the final archives are collected. We expect 
this downtime to be about 15 minutes.
The mailman archives are sent to Discourse for migration (15-20 minutes for 
data transfer).
The LLVM DIscourse is put into read-only mode. Given the size of our archives, 
we expect the import to take 5 hours. 
Sanity-checks will be made to ensure that everything looks as expected. We 
estimate this will take 1 hour or less.
The LLVM Discourse will be opened up again with all the archives imported.
We will post on Discourse about how things went and any next steps in the 
“Announcements” category.

We will use the Discourse Migration website 
 to communicate where we 
are in the process. 

We expect the LLVM Discourse to open by 5pm PST, but realize that even in the 
best plans, there may be unexpected situations that arise that cause the 
migration to take longer or possibly be stopped. If that occurs, we will 
evaluate the best course of action and communicate to the community as 
described above.

If you have any questions, please let me know.

Thanks,
Tanya___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

[lldb-dev] lldb-dev mailing list moving to LLVM Discourse

[Tanya Lattner via lldb-dev]

The lldb-dev mailing list will be moved to LLVM Discourse under the “LLDB” 
category (under Subprojects). All archives will be migrated. This list will be 
no longer be in use starting February 1, 2022. Please see this blog post for 
all details: https://blog.llvm.org/posts/2022-01-07-moving-to-discourse/ 


If you would like to continue to get notifications regarding LLDB, you must do 
the following:

1) Sign up for an account on LLVM Discourse (you may use your GitHub account):
https://llvm.discourse.group/ 

Note: If you are attempting to sign up after the mailing list archives have 
been migrated to Discourse (Feb 1), you may find that an account has been 
created for the email you used on the LLVM mailing list. If this is the case, 
click “Forgot password” to get access to this account.

2) Sign up for notifications to the “LLDB" category. 

Click on the “LLDB" category:




Click on the bell icon to set notifications. You can also modify these in your 
Account->Preferences->Notifications.




Thanks,
Tanya Lattner___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] [llvm-dev] RFC: Code Review Process

[Tanya Lattner via lldb-dev]

Hello! The purpose of this email is to start a discussion about our code review 
tools. No decisions have been made about changing tools. The idea behind a 
timeline is so that information could be gathered in a timely manner. The 
Infrastructure Working Group was formed to bring together community members who 
have an experience and/or passion regarding infrastructure. Anyone can 
participate in this working group and like the LLVM Foundation, the minutes are 
all made public. 

The LLVM Foundation’s mission is to support the LLVM project and help ensure 
the health and productivity of of the community and this is done through 
numerous ways including infrastructure. I do not think it is a negative thing 
that the foundation board of directors would be discussing our current tools 
and gathering information how how well they work and how we can make them 
better. As the legal entity who bares financial and legal responsibility for a 
lot of the infrastructure, this would make sense. This also makes sense because 
of the people involved who care a lot about LLVM and the project. But, the LLVM 
Foundation does not pay for Phabricator and we are very grateful for Google’s 
support of this critical piece of our infrastructure. 

Regarding Phabricator, there are a couple of pieces of information that were 
provided to the LLVM Foundation by maintainers (maybe previous it sounds like) 
of this instance and how we may need to look into alternative ways to support 
it.  In addition, Phacility itself has publicly stated that it is winding down 
operations. 
(https://admin.phacility.com/phame/post/view/11/phacility_is_winding_down_operations/).
 Lastly, there are questions about why we are not using GitHub pull requests as 
we are on GitHub and that might be the natural path to take for a number of 
reasons.

The above reasons are why the RFC was written. Perhaps it wasn’t written in the 
best way, but I also feel like it is being read in a negative way which is 
incredibly disappointing given I don’t feel there is a valid reason for this.

-Tanya






> On Oct 5, 2021, at 11:35 AM, Renato Golin via llvm-dev 
>  wrote:
> 
> On Tue, 5 Oct 2021 at 19:16, Tom Stellard  > wrote:
> However, it's not a good position for the Board to be responsible
> for something that it doesn't have control over.  If Google decided to stop 
> hosting
> Phabricator for some reason (unlikely, but not impossible), the Board would be
> responsible for finding a replacement.
> 
> Sorry, this is a very weak reason for such a strong worded "RFC".
> 
> I _cannot_ imagine "Google" stopping to support something so quickly as to 
> leave the foundation without recourse. And even if they did, *no one* would 
> blame the foundation for that.
> 
> Even if you ignore all the effort that hundreds of their engineers have done 
> over the past decade to the project, this would hurt Google more than anyone 
> else. It's a far fetched concern.
> 
> And if the foundation wants "control" of a piece of infrastructure that 
> Google has been maintaining for years, then this is a different discussion. 
> Hopefully one that doesn't involve unilateral decisions.
>  
> The main risk is that Phabricator is no longer maintained upstream.
> There was already an issue[1] recently where the arc tool stopped working and 
> won't
> be fixed upstream. Using unmaintained software is a bigger risk.
> 
> I don't like using unmaintained software either, but I think our Phab has had 
> more attention than the upstream project. And no one has to use arc, I 
> certainly never have.
> 
> Don't get me wrong, I don't like Phab and I think Github would bring new 
> people to the project, but it's gotta be done the right way, and pushing it 
> isn't it.
> 
> We, meaning the LLVM Board of Directors.  And really the problem isn't the 
> self-hosting
> so much as it's the lack of an enforceable maintenance agreement the 
> Foundation and the
> maintainers.
> 
> The problem isn't self-hosting at all, given that Google is doing that.  
> (apologies, I assumed otherwise earlier).
> 
> Neither is maintenance, given Google is doing that too.
> 
> The only thing that's left is control, and I don't really understand why this 
> is important, as I explained above.
> 
> cheers,
> --renato
> ___
> LLVM Developers mailing list
> llvm-...@lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev

___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

[lldb-dev] 2021 LLVM Developers' Meeting - Call for Talk Proposals DEADLINE TODAY (5pm PDT)

[Tanya Lattner via lldb-dev]

This is just a friendly reminder that the deadline is today at 5pm PDT.

Thanks,
Tanya

> On Sep 17, 2021, at 2:21 PM, Tanya Lattner  wrote:
> 
> Hello! This is an update to let you know that the deadline has been extended 
> to September 27th at 5pm PDT.
> 
> A couple of additional notes:
> - Notification will be on Oct 8th
> - Recordings will be happening as early as the first week of November (Nov 
> 1-5). We are finalizing the details in the next couple weeks on how this will 
> work. 
> 
> Thanks,
> Tanya 
> 
>> On Sep 7, 2021, at 10:13 PM, Tanya Lattner > > wrote:
>> 
>> All developers and users of LLVM and related sub-projects are invited to 
>> present at the 2021 LLVM Developers’ Meeting 
>> ! The conference will be held November 
>> 17-19. Due to the uncertainty of COVID-19, the conference will again be 
>> online only. Full conference details coming in the next couple weeks. There 
>> will be a Q session for proposal submission on September 9 at 10am and 
>> 10pm PDT. See the website  for details.
>> 
>> Submit your talk proposals here (but read on as some things have changed):
>> LLVM2021 Submissions 
>> This year, we will have a few changes to the program. First, we are 
>> introducing a new technical talk category called “Quick Technical Talks”. 
>> These talks are similar to full length technical talks or lightning talks 
>> except that the speakers are given only 10 minutes. Additionally, we will no 
>> longer have a poster session and encourage those interested to submit a 
>> lightning talk instead. The Student Research Competition has been modified 
>> to no longer be a competition, but a specific category for student 
>> presentations and full length papers are not required. Lastly, you will 
>> notice that Birds of a Feather (BoF) sessions have been removed as a 
>> category and we will share plans for these types of sessions at a later 
>> date. 
>> 
>> We are looking for the following proposals:
>> Technical Talks (20-25 minutes*):
>> Talks on:
>> LLVM Infrastructure,Clang and all related sub-projects
>> On uses of LLVM in academia or industry
>> On new projects using Clang or LLVM
>> Tutorials (60 minutes)
>> In depth talks on LLVM infrastructure or other core libraries, tools, etc. 
>> Demos encouraged.
>> Student Technical Talks (15-20 minutes*)
>> Talks from students using LLVM, Clang, and all sub-projects in research.
>> The audience usually votes on a winner.
>> Quick Technical Talks (10 minutes)
>>  Quick talks about a use or improvement of LLVM and other sub-projects.
>> Lightning Talks (5 minutes)
>> Lightning fast talks about a use or improvement of LLVM and other 
>> sub-projects.
>> Panels (45 minutes)
>> Panels may discuss any topic as long as it’s relevant to LLVM or related 
>> sub-projects. Panels can take many forms, but a common format is to begin 
>> with short introductions from each panel member, and follow with an 
>> interactive dialogue among the panelists and audience members. Panels should 
>> consist of at least 3 people and have a moderator.
>> 
>> * Exact times TBD after talks selected
>> 
>> Submission Requirements:
>> The submission deadline is September 20, 2021 at 5:00PM PDT.
>> 
>> Please submit your proposal here:
>> LLVM2021 Submissions 
>> For each proposal you must submit the following:
>> Talk title
>> Abstract
>> Submission type (Different than last year)
>> For technical talk submissions, you can indicate if you would give a shorter 
>> talk (ie. Lightning or Quick instead of full length Technical Talk)
>> Photo and bios for all speakers (NEW!)
>> Short abstract for the website
>> Extended PDF abstract (optional)
>> 
>> We highly recommend you consult and follow the guide below when submitting 
>> your proposal.
>> 
>> Additional details regarding notification and recording timeline will be 
>> communicated soon. If you have questions, please contact Tanya Lattner 
>> through Discourse, Discord, or email.
>> 
>> 
>> Thanks,
>> Tanya Lattner 
>> 
>> 
>> Detailed guidance on writing a proposal for the LLVM Developers’ Meeting
>> 
>> Writing a proposal for the LLVM Developers’ Meeting
>> 
>> This document is a guide to help you submit the best proposal and increase 
>> your chances of your proposal being accepted. The LLVM Developers’ Meeting 
>> program committee receives more proposals than can be accepted, so please 
>> read this guide carefully.
>> 
>> If you have never presented at an LLVM Developers’ Meeting, then do not fear 
>> this process. We are actively looking for new speakers who are excited about 
>> LLVM and helping grow the community through these educational talks! You do 
>> not need to be a long time developer to submit a proposal.
>> 
>> General Guidelines:
>> It should be clear from your abstract what your topic is, who your targeted 
>> audience is, 

Re: [lldb-dev] 2021 LLVM Developers' Meeting - Call for Talk Proposals DEADLINE EXTENDED to Sept 27

[Tanya Lattner via lldb-dev]

Hello! This is an update to let you know that the deadline has been extended to 
September 27th at 5pm PDT.

A couple of additional notes:
- Notification will be on Oct 8th
- Recordings will be happening as early as the first week of November (Nov 
1-5). We are finalizing the details in the next couple weeks on how this will 
work. 

Thanks,
Tanya 

> On Sep 7, 2021, at 10:13 PM, Tanya Lattner  wrote:
> 
> All developers and users of LLVM and related sub-projects are invited to 
> present at the 2021 LLVM Developers’ Meeting 
> ! The conference will be held November 
> 17-19. Due to the uncertainty of COVID-19, the conference will again be 
> online only. Full conference details coming in the next couple weeks. There 
> will be a Q session for proposal submission on September 9 at 10am and 10pm 
> PDT. See the website  for details.
> 
> Submit your talk proposals here (but read on as some things have changed):
> LLVM2021 Submissions 
> This year, we will have a few changes to the program. First, we are 
> introducing a new technical talk category called “Quick Technical Talks”. 
> These talks are similar to full length technical talks or lightning talks 
> except that the speakers are given only 10 minutes. Additionally, we will no 
> longer have a poster session and encourage those interested to submit a 
> lightning talk instead. The Student Research Competition has been modified to 
> no longer be a competition, but a specific category for student presentations 
> and full length papers are not required. Lastly, you will notice that Birds 
> of a Feather (BoF) sessions have been removed as a category and we will share 
> plans for these types of sessions at a later date. 
> 
> We are looking for the following proposals:
> Technical Talks (20-25 minutes*):
> Talks on:
> LLVM Infrastructure,Clang and all related sub-projects
> On uses of LLVM in academia or industry
> On new projects using Clang or LLVM
> Tutorials (60 minutes)
> In depth talks on LLVM infrastructure or other core libraries, tools, etc. 
> Demos encouraged.
> Student Technical Talks (15-20 minutes*)
> Talks from students using LLVM, Clang, and all sub-projects in research.
> The audience usually votes on a winner.
> Quick Technical Talks (10 minutes)
>   Quick talks about a use or improvement of LLVM and other sub-projects.
> Lightning Talks (5 minutes)
> Lightning fast talks about a use or improvement of LLVM and other 
> sub-projects.
> Panels (45 minutes)
> Panels may discuss any topic as long as it’s relevant to LLVM or related 
> sub-projects. Panels can take many forms, but a common format is to begin 
> with short introductions from each panel member, and follow with an 
> interactive dialogue among the panelists and audience members. Panels should 
> consist of at least 3 people and have a moderator.
> 
> * Exact times TBD after talks selected
> 
> Submission Requirements:
> The submission deadline is September 20, 2021 at 5:00PM PDT.
> 
> Please submit your proposal here:
> LLVM2021 Submissions 
> For each proposal you must submit the following:
> Talk title
> Abstract
> Submission type (Different than last year)
> For technical talk submissions, you can indicate if you would give a shorter 
> talk (ie. Lightning or Quick instead of full length Technical Talk)
> Photo and bios for all speakers (NEW!)
> Short abstract for the website
> Extended PDF abstract (optional)
> 
> We highly recommend you consult and follow the guide below when submitting 
> your proposal.
> 
> Additional details regarding notification and recording timeline will be 
> communicated soon. If you have questions, please contact Tanya Lattner 
> through Discourse, Discord, or email.
> 
> 
> Thanks,
> Tanya Lattner 
> 
> 
> Detailed guidance on writing a proposal for the LLVM Developers’ Meeting
> 
> Writing a proposal for the LLVM Developers’ Meeting
> 
> This document is a guide to help you submit the best proposal and increase 
> your chances of your proposal being accepted. The LLVM Developers’ Meeting 
> program committee receives more proposals than can be accepted, so please 
> read this guide carefully.
> 
> If you have never presented at an LLVM Developers’ Meeting, then do not fear 
> this process. We are actively looking for new speakers who are excited about 
> LLVM and helping grow the community through these educational talks! You do 
> not need to be a long time developer to submit a proposal.
> 
> General Guidelines:
> It should be clear from your abstract what your topic is, who your targeted 
> audience is, and what are the takeaways for attendees. The program committee 
> gets a lot of proposals and does not have time to read 10 page papers for 
> each submission.
> Talks about a use of LLVM (etc) should include details about how LLVM is used 
> and not only be about the resulting application.
> 

[lldb-dev] 2021 LLVM Developers' Meeting - Call for Talk Proposals (Deadline Sept 20)

[Tanya Lattner via lldb-dev]

All developers and users of LLVM and related sub-projects are invited to 
present at the 2021 LLVM Developers’ Meeting 
! The conference will be held November 17-19. 
Due to the uncertainty of COVID-19, the conference will again be online only. 
Full conference details coming in the next couple weeks. There will be a Q 
session for proposal submission on September 9 at 10am and 10pm PDT. See the 
website  for details.

Submit your talk proposals here (but read on as some things have changed):
LLVM2021 Submissions 
This year, we will have a few changes to the program. First, we are introducing 
a new technical talk category called “Quick Technical Talks”. These talks are 
similar to full length technical talks or lightning talks except that the 
speakers are given only 10 minutes. Additionally, we will no longer have a 
poster session and encourage those interested to submit a lightning talk 
instead. The Student Research Competition has been modified to no longer be a 
competition, but a specific category for student presentations and full length 
papers are not required. Lastly, you will notice that Birds of a Feather (BoF) 
sessions have been removed as a category and we will share plans for these 
types of sessions at a later date. 

We are looking for the following proposals:
Technical Talks (20-25 minutes*):
Talks on:
LLVM Infrastructure,Clang and all related sub-projects
On uses of LLVM in academia or industry
On new projects using Clang or LLVM
Tutorials (60 minutes)
In depth talks on LLVM infrastructure or other core libraries, tools, etc. 
Demos encouraged.
Student Technical Talks (15-20 minutes*)
Talks from students using LLVM, Clang, and all sub-projects in research.
The audience usually votes on a winner.
Quick Technical Talks (10 minutes)
Quick talks about a use or improvement of LLVM and other sub-projects.
Lightning Talks (5 minutes)
Lightning fast talks about a use or improvement of LLVM and other sub-projects.
Panels (45 minutes)
Panels may discuss any topic as long as it’s relevant to LLVM or related 
sub-projects. Panels can take many forms, but a common format is to begin with 
short introductions from each panel member, and follow with an interactive 
dialogue among the panelists and audience members. Panels should consist of at 
least 3 people and have a moderator.

* Exact times TBD after talks selected

Submission Requirements:
The submission deadline is September 20, 2021 at 5:00PM PDT.

Please submit your proposal here:
LLVM2021 Submissions 
For each proposal you must submit the following:
Talk title
Abstract
Submission type (Different than last year)
For technical talk submissions, you can indicate if you would give a shorter 
talk (ie. Lightning or Quick instead of full length Technical Talk)
Photo and bios for all speakers (NEW!)
Short abstract for the website
Extended PDF abstract (optional)

We highly recommend you consult and follow the guide below when submitting your 
proposal.

Additional details regarding notification and recording timeline will be 
communicated soon. If you have questions, please contact Tanya Lattner through 
Discourse, Discord, or email.


Thanks,
Tanya Lattner 


Detailed guidance on writing a proposal for the LLVM Developers’ Meeting

Writing a proposal for the LLVM Developers’ Meeting

This document is a guide to help you submit the best proposal and increase your 
chances of your proposal being accepted. The LLVM Developers’ Meeting program 
committee receives more proposals than can be accepted, so please read this 
guide carefully.

If you have never presented at an LLVM Developers’ Meeting, then do not fear 
this process. We are actively looking for new speakers who are excited about 
LLVM and helping grow the community through these educational talks! You do not 
need to be a long time developer to submit a proposal.

General Guidelines:
It should be clear from your abstract what your topic is, who your targeted 
audience is, and what are the takeaways for attendees. The program committee 
gets a lot of proposals and does not have time to read 10 page papers for each 
submission.
Talks about a use of LLVM (etc) should include details about how LLVM is used 
and not only be about the resulting application.
Tutorials on “how to use X” in LLVM (or other subproject) are greatly desired 
and beneficial to many developers. Entry level topics are encouraged as well.
Talks that have been presented at other technical conferences tend to not get 
accepted. If you have presented this topic before, make it clear what is new 
and different in your talk.


Technical Talk and Student Talk  Proposal Template:
** Include in the extended abstract PDF attachment **

Title:
This will be displayed on the website, schedule, and signs. Keep it short and 
catchy to attract attendees to your talks. A couple of examples 

[lldb-dev] IMPORTANT NOTICE - Subscription to Mailman lists disabled immediately

[Tanya Lattner via lldb-dev]

All,

We need to immediately disable subscription capabilities to all LLVM Mailman 
lists.

The current Mailman server is being abused by subscribing valid email addresses 
to our lists and because the list requires confirmation, the email address gets 
“spam”. An email address is subscribed upwards of 100 times in a short period 
of time in many cases. AWS has threatened to turn off our instance unless we 
take immediate action. Given the time frame of the situation (24 hours to 
resolve), we have no choice but to disable all new subscription capabilities as 
we can not distinguish between a real subscription attempt versus the abuse. 

Those currently subscribed should see no changes or impact to their workflow. 

I am sure this raises a lot of questions for the LLVM community and we are 
working hard and as quickly as possible on a permanent solution to this 
situation.

Thanks,
Tanya Lattner
LLVM Foundation

___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] 2020 Virtual LLVM Developers' Meeting - Call for presentations! (Deadline SOON)

[Tanya Lattner via lldb-dev]

A little more than 24 hours left for proposals! 

Submit your proposal here: LLVM2020 Submissions 


Thank you for your support of our first virtual LLVM Developers’ Meeting!

-Tanya

> On Jul 12, 2020, at 9:51 AM, Tanya Lattner  wrote:
> 
> The deadline has been extended until July 20 11:59PM PDT.
> 
> Thanks,
> Tanya
> 
>> On Jun 12, 2020, at 5:07 PM, Tanya Lattner > > wrote:
>> 
>> All developers and users of LLVM and related sub-projects are invited to 
>> present at the first virtual 2020 LLVM Developers’ Meeting 
>> !
>> 
>> We are looking for the following proposals:
>> Technical Talks (25-30 minutes including Q):
>> Talks on:
>> LLVM Infrastructure,Clang and all related sub-projects
>> On uses of LLVM in academia or industry
>> On new projects using Clang or LLVM
>> Tutorials (60 minutes)
>> In depth talks on LLVM infrastructure or other core libraries, tools, etc. 
>> Demos encouraged.
>> Student Research Competition Technical Talks & Poster (20-25 minutes 
>> including Q)
>> Talks from students using LLVM, Clang, and all sub-projects in research.
>> The audience usually votes on a winner.
>> Lightning Talks (5 minutes, no questions, no discussions)
>> Quick talks about a use or improvement of LLVM and other sub-projects.
>> Birds of a Feather 
>>  (30 minutes)
>> Historically these are informal and ad-hoc, but at our meeting they are 
>> prepared in advance and are guided discussions (usually with a slide deck) 
>> about a specific topic. For informal and ad-hoc, please consider a Round 
>> Table (details to come). 
>> Panels (30-60 minutes)
>> Panels may discuss any topic as long as it’s relevant to LLVM or related 
>> sub-projects. Panels can take many forms, but a common format is to begin 
>> with short introductions from each panel member, and follow with an 
>> interactive dialogue among the panelists and audience members. Panels should 
>> consist of at least 3 people and have a moderator.
>> Posters (1 hour session)
>> Posters presenting work using LLVM and related subprojects. Poster 
>> presenters will answer questions from attendees and give mini presentations. 
>> 
>> As this conference is virtual and our very first, we are still working out 
>> the numerous details. The length of the talk types below are subject to 
>> change, but the above gives you an idea of what we expect. The majority of 
>> the talks will be pre-recorded except for panels, birds of a feather, 
>> posters, and possibly lightning talks.  In addition, we will be requiring 
>> most speakers to participate in some form of live Q Time zones are a huge 
>> challenge with a virtual conference and we will do our best to be reasonable 
>> in our expectations. 
>> 
>> The timeframe for submission is also much tighter due to allowing time for 
>> speakers to record and us to process videos. We apologize for the 
>> inconvenience. 
>> 
>> Submission Requirements:
>> The submission deadline is July 15, 2020 at 11:59PM PDT.
>> 
>> Please submit your proposal here:
>> LLVM2020 Submissions 
>> For each proposal, please submit a title, short abstract, submission type, 
>> abstract for the website, include who the speakers or panel 
>> member/moderators are, and provide a more detailed description of the talk 
>> through an extended PDF abstract. We highly recommend you consult and follow 
>> the guide at the end of this CFP when submitting your proposal.
>> 
>> FAQ
>> 
>> When will I be notified of acceptance?
>> 
>> Our goal is to notify all submissions by July 31, 2020.
>> 
>> When is the conference?
>> 
>> In order to not conflict with another large virtual conference, we have 
>> moved the 2020 LLVM Developers’ Meeting to October 6-8. The exact times of 
>> the conference are still under discussion.
>> 
>> Should I register if I have submitted a proposal?
>> 
>> Given this is a virtual conference and we have less space restrictions and a 
>> different fee structure, you can register at any time before the 
>> registration deadline. We will be providing details on registration in July. 
>> 
>> When will the recordings be due?
>> 
>> Recordings should be completed by September 14.
>> 
>> Will I be required to have a video camera?
>> 
>> We do not want the lack of recording equipment to prevent submissions and 
>> will be sorting out options to help those without recording equipment 
>> available. Please stay tuned for details. 
>> 
>> When will my live Q be?
>> 
>> As the conference is virtual, our attendees and speakers will be in many 
>> different time zones. We won’t know the program until closer to the event 
>> and then we can start to form a schedule. Our schedule will attempt to meet 
>> the needs of many time zones, but will not be a perfect solution. You may be 
>> asked to give a live Q early in the morning, late at 

Re: [lldb-dev] 2020 Virtual LLVM Developers' Meeting - Call for presentations! (Deadline EXTENDED)

[Tanya Lattner via lldb-dev]

The deadline has been extended until July 20 11:59PM PDT.

Thanks,
Tanya

> On Jun 12, 2020, at 5:07 PM, Tanya Lattner  wrote:
> 
> All developers and users of LLVM and related sub-projects are invited to 
> present at the first virtual 2020 LLVM Developers’ Meeting 
> !
> 
> We are looking for the following proposals:
> Technical Talks (25-30 minutes including Q):
> Talks on:
> LLVM Infrastructure,Clang and all related sub-projects
> On uses of LLVM in academia or industry
> On new projects using Clang or LLVM
> Tutorials (60 minutes)
> In depth talks on LLVM infrastructure or other core libraries, tools, etc. 
> Demos encouraged.
> Student Research Competition Technical Talks & Poster (20-25 minutes 
> including Q)
> Talks from students using LLVM, Clang, and all sub-projects in research.
> The audience usually votes on a winner.
> Lightning Talks (5 minutes, no questions, no discussions)
> Quick talks about a use or improvement of LLVM and other sub-projects.
> Birds of a Feather 
>  (30 minutes)
> Historically these are informal and ad-hoc, but at our meeting they are 
> prepared in advance and are guided discussions (usually with a slide deck) 
> about a specific topic. For informal and ad-hoc, please consider a Round 
> Table (details to come). 
> Panels (30-60 minutes)
> Panels may discuss any topic as long as it’s relevant to LLVM or related 
> sub-projects. Panels can take many forms, but a common format is to begin 
> with short introductions from each panel member, and follow with an 
> interactive dialogue among the panelists and audience members. Panels should 
> consist of at least 3 people and have a moderator.
> Posters (1 hour session)
> Posters presenting work using LLVM and related subprojects. Poster presenters 
> will answer questions from attendees and give mini presentations. 
> 
> As this conference is virtual and our very first, we are still working out 
> the numerous details. The length of the talk types below are subject to 
> change, but the above gives you an idea of what we expect. The majority of 
> the talks will be pre-recorded except for panels, birds of a feather, 
> posters, and possibly lightning talks.  In addition, we will be requiring 
> most speakers to participate in some form of live Q Time zones are a huge 
> challenge with a virtual conference and we will do our best to be reasonable 
> in our expectations. 
> 
> The timeframe for submission is also much tighter due to allowing time for 
> speakers to record and us to process videos. We apologize for the 
> inconvenience. 
> 
> Submission Requirements:
> The submission deadline is July 15, 2020 at 11:59PM PDT.
> 
> Please submit your proposal here:
> LLVM2020 Submissions 
> For each proposal, please submit a title, short abstract, submission type, 
> abstract for the website, include who the speakers or panel member/moderators 
> are, and provide a more detailed description of the talk through an extended 
> PDF abstract. We highly recommend you consult and follow the guide at the end 
> of this CFP when submitting your proposal.
> 
> FAQ
> 
> When will I be notified of acceptance?
> 
> Our goal is to notify all submissions by July 31, 2020.
> 
> When is the conference?
> 
> In order to not conflict with another large virtual conference, we have moved 
> the 2020 LLVM Developers’ Meeting to October 6-8. The exact times of the 
> conference are still under discussion.
> 
> Should I register if I have submitted a proposal?
> 
> Given this is a virtual conference and we have less space restrictions and a 
> different fee structure, you can register at any time before the registration 
> deadline. We will be providing details on registration in July. 
> 
> When will the recordings be due?
> 
> Recordings should be completed by September 14.
> 
> Will I be required to have a video camera?
> 
> We do not want the lack of recording equipment to prevent submissions and 
> will be sorting out options to help those without recording equipment 
> available. Please stay tuned for details. 
> 
> When will my live Q be?
> 
> As the conference is virtual, our attendees and speakers will be in many 
> different time zones. We won’t know the program until closer to the event and 
> then we can start to form a schedule. Our schedule will attempt to meet the 
> needs of many time zones, but will not be a perfect solution. You may be 
> asked to give a live Q early in the morning, late at night, or multiple 
> times. 
> 
> Who is on the program committee?
> 
> The program committee is composed of active developers of the LLVM, Clang, 
> and related sub-communities. The website will be updated with the list of the 
> program committee members.
> 
> I have a question, who do I contact?
> 
> Please email the LLVM Dev Mtg Organizers (devmtg-organiz...@lists.llvm.org 
> 

[lldb-dev] 2020 Virtual LLVM Developers' Meeting - Call for presentations!

[Tanya Lattner via lldb-dev]

All developers and users of LLVM and related sub-projects are invited to 
present at the first virtual 2020 LLVM Developers’ Meeting 
!

We are looking for the following proposals:
Technical Talks (25-30 minutes including Q):
Talks on:
LLVM Infrastructure,Clang and all related sub-projects
On uses of LLVM in academia or industry
On new projects using Clang or LLVM
Tutorials (60 minutes)
In depth talks on LLVM infrastructure or other core libraries, tools, etc. 
Demos encouraged.
Student Research Competition Technical Talks & Poster (20-25 minutes including 
Q)
Talks from students using LLVM, Clang, and all sub-projects in research.
The audience usually votes on a winner.
Lightning Talks (5 minutes, no questions, no discussions)
Quick talks about a use or improvement of LLVM and other sub-projects.
Birds of a Feather 
 (30 minutes)
Historically these are informal and ad-hoc, but at our meeting they are 
prepared in advance and are guided discussions (usually with a slide deck) 
about a specific topic. For informal and ad-hoc, please consider a Round Table 
(details to come). 
Panels (30-60 minutes)
Panels may discuss any topic as long as it’s relevant to LLVM or related 
sub-projects. Panels can take many forms, but a common format is to begin with 
short introductions from each panel member, and follow with an interactive 
dialogue among the panelists and audience members. Panels should consist of at 
least 3 people and have a moderator.
Posters (1 hour session)
Posters presenting work using LLVM and related subprojects. Poster presenters 
will answer questions from attendees and give mini presentations. 

As this conference is virtual and our very first, we are still working out the 
numerous details. The length of the talk types below are subject to change, but 
the above gives you an idea of what we expect. The majority of the talks will 
be pre-recorded except for panels, birds of a feather, posters, and possibly 
lightning talks.  In addition, we will be requiring most speakers to 
participate in some form of live Q Time zones are a huge challenge with a 
virtual conference and we will do our best to be reasonable in our 
expectations. 

The timeframe for submission is also much tighter due to allowing time for 
speakers to record and us to process videos. We apologize for the 
inconvenience. 

Submission Requirements:
The submission deadline is July 15, 2020 at 11:59PM PDT.

Please submit your proposal here:
LLVM2020 Submissions 
For each proposal, please submit a title, short abstract, submission type, 
abstract for the website, include who the speakers or panel member/moderators 
are, and provide a more detailed description of the talk through an extended 
PDF abstract. We highly recommend you consult and follow the guide at the end 
of this CFP when submitting your proposal.

FAQ

When will I be notified of acceptance?

Our goal is to notify all submissions by July 31, 2020.

When is the conference?

In order to not conflict with another large virtual conference, we have moved 
the 2020 LLVM Developers’ Meeting to October 6-8. The exact times of the 
conference are still under discussion.

Should I register if I have submitted a proposal?

Given this is a virtual conference and we have less space restrictions and a 
different fee structure, you can register at any time before the registration 
deadline. We will be providing details on registration in July. 

When will the recordings be due?

Recordings should be completed by September 14.

Will I be required to have a video camera?

We do not want the lack of recording equipment to prevent submissions and will 
be sorting out options to help those without recording equipment available. 
Please stay tuned for details. 

When will my live Q be?

As the conference is virtual, our attendees and speakers will be in many 
different time zones. We won’t know the program until closer to the event and 
then we can start to form a schedule. Our schedule will attempt to meet the 
needs of many time zones, but will not be a perfect solution. You may be asked 
to give a live Q early in the morning, late at night, or multiple times. 

Who is on the program committee?

The program committee is composed of active developers of the LLVM, Clang, and 
related sub-communities. The website will be updated with the list of the 
program committee members.

I have a question, who do I contact?

Please email the LLVM Dev Mtg Organizers (devmtg-organiz...@lists.llvm.org 
), or the LLVM Developers’ Meeting 
mailing list. http://lists.llvm.org/mailman/listinfo/llvm-devmeeting 


Detailed guidance on writing a proposal for the LLVM Developers’ Meeting

Writing a proposal for the LLVM Developers’ Meeting

This document is a guide to help you submit 

[lldb-dev] New Dates for 2020 Virtual LLVM Dev Mtg

[Tanya Lattner via lldb-dev]

In order to not conflict with the Grace Hopper Conference, which has now gone 
virtual and is occurring the whole last week of September, we are moving the 
2020 Virtual LLVM Developer’s Conference to October 6-8. The conference will 
span 3 days and the exact times are still being determined.

Thanks,
Tanya Lattner
LLVM Dev Mtg Organizer
President - LLVM Foundation___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

[lldb-dev] 2020 US LLVM Developers' Meeting - Announcement & Feedback Needed

[Tanya Lattner via lldb-dev]

LLVM Community,

The LLVM Foundation board has been continuing to discuss the upcoming 2020 US 
LLVM Developers' Meeting in San Jose, CA and the impact by COVID-19. This event 
is currently scheduled to occur on September 28-29, and special events on 
September 27. 

Last year’s US LLVM Developers’ meeting had over 600 attendees, and given past 
trends, we had expected this number to grow for 2020. However, an event this 
size is difficult to hold given the COVID-19 situation. The Governor of 
California recently announced the four stage plan to reopen California 
(https://www.sacbee.com/news/coronavirus/article242339301.html 
). Conferences 
such as ours, are in Stage 4 and he stated that “Stage 4 won’t arrive until 
treatments for the coronavirus have been developed.” 

Given this announcement and the uncertainty of the timing of Stage 4, we feel 
that continuing to plan an in person event is not in our best interest. We want 
presenters to feel confident to submit a proposal and know if an event is going 
to happen or not. We want our attendees to feel safe while traveling to and 
attending our event. In addition, planning a different kind of event is going 
to take a lot of time and we want to make sure we do our best to make it great.

With this said, we are moving forward with the intent to host the first ever 
virtual LLVM Developers’ Meeting. However, we need your help! We are interested 
in hearing your feedback on a few different format options and also sharing 
your experiences with other virtual events. We have created a survey that we 
hope you can take a few minutes to fill out: 
https://forms.gle/iuHRwS3mBrns7XwD6 
Your input will help guide us with the format and length of our first virtual 
conference. 

We realize that this may be a disappointment to many in our community and 
honestly, we feel the same way. We strongly believe that the most valuable part 
of our conferences is the in person “hallway” discussions, round tables, 
networking, and socialization. An LLVM Developers’ Meeting might be one of the 
few times you see your LLVM Project co-workers in person. While a virtual event 
will not be the same, we do hope to make it as great as we can and to bring our 
community together to share each other’s successes, ideas, and advice.

If you have any questions, please feel free to reach out to me personally or on 
the mailing lists. 

Thank you,
Tanya Lattner
President
LLVM Foundation___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

[lldb-dev] 2020 US LLVM Developers' Meeting - September 28-29

[Tanya Lattner via lldb-dev]

The LLVM Foundation is pleased to announce the 14th annual LLVM Developers’ 
Meeting in the Bay Area  on September 28-29 
in San Jose, CA. We will have additional events on September 27th in the 
afternoon/evening which be announced when available.

The LLVM Developers' Meeting is a bi-annual 2 day gathering of the entire LLVM 
Project community. The conference is organized by the LLVM Foundation and many 
volunteers within the LLVM community. Developers and users of LLVM, Clang, and 
related subprojects will enjoy attending interesting talks, impromptu 
discussions, and networking with the many members of our community. Whether you 
are a new to the LLVM project or a long time member, there is something for 
each attendee.

Given the current situation regarding COVID-19, we feel it is best to be 
totally transparent with our planning process. We are closely monitoring the 
news regarding restrictions on travel and large gatherings and also following 
the World Health Organization's advice. It takes about 9-12 months of planning 
for our developers’ meetings and given we do not know the situation in 
September, we are moving forward with the hope that it will be safe to host our 
event. 

What can you expect at a LLVM Developers' Meeting?

Technical Talks: These 20-30 minute talks cover all topics from core 
infrastructure talks, to project's using LLVM's infrastructure. Attendees will 
take away technical information that could be pertinent to their project or 
general interest. 
Tutorials: Tutorials are 50 minute sessions that dive down deep into a 
technical topic. Expect in depth examples and explanations.
Lightning Talks: These are fast 5 minute talks that give you a taste of a 
project or topic. Attendees will hear a wide range of topics and probably leave 
you wanting to learn more.
Panels: Panel sessions are guided discussions about a specific topic. The panel 
consists of ~3 developers who discuss a topic through prepared questions from a 
moderator. The audience is also given the opportunity to ask questions of the 
panel.
Birds of a Feather: Large round table discussions with a more formal directed 
discussion.
Student Research Competition: Students present their research using LLVM or 
related subprojects. These are usually 20 minute technical presentations with 
Q The audience will vote at the end for the winning presentation and paper.
Poster Session: An hour long session where selected posters are on display for 
attendees to ask questions and discuss.
Round Table Discussions: Informal and impromptu discussions on a specific 
topic. During the conference there are set time slots where groups can organize 
to discuss a problem or topic.
Evening Reception (September 28): After a full day of technical talks and 
discussions, join your fellow attendees for an evening reception to continue 
the conversation and meet even more attendees.

What types of people attend?
• Active developers of projects in the LLVM Umbrella (LLVM core, Clang, 
LLDB, libc++, compiler_rt, klee, lld, etc).
• Anyone interested in using these as part of another project.
• Students and Researchers
• Compiler, programming language, and runtime enthusiasts.
• Those interested in using compiler and toolchain technology in novel 
and interesting ways.

More information regarding call for papers, registration, travel grants,etc, 
will be coming in the next month.

For future announcements or questions: Please sign up for the LLVM Developers’ 
Meeting mailing list 
.

___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

[lldb-dev] Code of Conduct Next Steps - Community feedback needed

[Tanya Lattner via lldb-dev]

LLVM Community,

The LLVM Code of Conduct has been in draft mode for several years now. In order 
to finalize the Code of Conduct, there are 3 steps left to complete:

Draft an Incident Response Guide. 
This guide is intended for someone who is considering reporting a potential 
code of conduct violation. You can view and comment on the proposed guide here 
(or by email if you prefer): 
https://docs.google.com/document/d/10LClyw1x1e4OIiKFFRqklbZ2D_xwZz85HZ7kWwZ_yys/edit?usp=sharing
 


Draft a Response Guide. 
This guide is intended for members of the code of conduct committee or 
organizers of an event. You can view and comment on the proposed guide here (or 
by email if you prefer):
https://docs.google.com/document/d/1dEvF9NwZdaDLQNPVBudipdFiZ0E553Lz3qOqeCsfpNk/edit?usp=sharing
 

Form code of conduct committee. 
This committee will be responsible for responding to code of conduct reports as 
described in the response guide. The LLVM Foundation board will propose the 
initial members of this committee and provide a period of time to collect 
feedback from members of the community. 


In order to keep this process running smoothly and moving forward, we would 
appreciate getting any  community feedback within the next two weeks.. 

Some previous Code of Conduct discussions have been difficult - please remember 
to treat others with respect and kindness in your response. 

Thanks,
Tanya___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] [llvm-dev] [cfe-dev] December LLVM bay-area social is this Thursday!

[Tanya Lattner via lldb-dev]

In case Steins doesn't work out.. BJs in Cupertino has a large space for groups 
but that would mean closer to Cupertino area. 

-Tanya

> On Dec 28, 2019, at 8:50 PM, Eric Christopher via llvm-dev 
>  wrote:
> 
> Still a bit of a Twitter thread too. A few more options maybe if we want to 
> move to downtown San Jose. 
> 
> On Sat, Dec 28, 2019, 8:47 PM Chandler Carruth via llvm-dev 
> mailto:llvm-...@lists.llvm.org>> wrote:
> +1, i'm just glad you're making progress on a promising option!
> 
> On Sat, Dec 28, 2019 at 8:33 PM JF Bastien  > wrote:
> The guy on the phone said that wouldn’t be a problem 路‍♂️ 
> I hope that stays correct! Ideally we’d have the same deal: indeterminate 
> number of people, ordering off the menu. I’ll check with you if that’s not 
> the case. 
> 
> 
>> On Dec 28, 2019, at 7:41 PM, Chandler Carruth > > wrote:
>> 
>> 
>> Mostly worried because we talked to them before and they wanted us to buy a 
>> banquet menu at  A lot of dollars.
>> 
>> On Sat, Dec 28, 2019, 19:15 JF Bastien via cfe-dev > > wrote:
>> I reached out to Steins (which is right across the street) to see if they 
>> can host us. I’ll keep y’all posted, it seemed optimistic in our phone chat.
>> 
>> 
>>> On Dec 24, 2019, at 11:06 AM, George Burgess IV via cfe-dev 
>>> mailto:cfe-...@lists.llvm.org>> wrote:
>>> 
>>> Oof. :(
>>> 
>>> Offhand, I can’t think of any place in particular. As one might imagine, 
>>> accommodating 50+ people isn’t always super easy for places to do. 
>>> 
>>> Suggestions welcome!
>>> 
>>> On Tue, Dec 24, 2019 at 10:27 AM Sean Silva >> > wrote:
>>> It looks like Tied House will be shutting down :( Do we have a replacement 
>>> venue?
>>> 
>>> https://www.mv-voice.com/blogs/p/2019/12/23/facing-monthslong-closure-due-to-chemical-contamination-mountain-view-brewery-tied-house-calls-it-quits
>>>  
>>> 
>>> 
>>> On Wed, Dec 4, 2019 at 12:49 PM George Burgess IV via llvm-dev 
>>> mailto:llvm-...@lists.llvm.org>> wrote:
>>> We'll be at Tied House as usual, starting on Thursday the 5th at 7pm!
>>> 
>>> If you can, help us plan and RSVP here: 
>>> https://www.meetup.com/LLVM-Bay-Area-Social/events/kncsjlyzqbhb 
>>> 
>>> 
>>> See everyone there!
>>> ___
>>> LLVM Developers mailing list
>>> llvm-...@lists.llvm.org 
>>> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev 
>>> 
>>> ___
>>> cfe-dev mailing list
>>> cfe-...@lists.llvm.org 
>>> https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-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 
> 
> ___
> LLVM Developers mailing list
> llvm-...@lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev

___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] LLDB Website is not being updated

[Tanya Lattner via lldb-dev]

I’ll have to check the status of moving the scripts over and what is going on. 
But yes, this is all related to moving to GitHub and modifying scripts that 
used to be either on a post-commit hook or nightly cron.

-Tanya

> On Nov 21, 2019, at 3:04 PM, Jonas Devlieghere  wrote:
> 
> I see a bunch of eros here:
> http://lists.llvm.org/pipermail/www-scripts/2019-November/thread.html
> 
> Is this possibly related to the Github/monorepo transition?
> 
> -- Jonas
> 
> On Thu, Nov 21, 2019 at 10:52 AM Adrian Prantl via lldb-dev
>  wrote:
>> 
>> Hello Tanya,
>> 
>> it looks like the cron job that is supposed to be updating the LLDB website 
>> isn't running or is otherwise blocked at the moment. You can see on 
>> https://lldb.llvm.org that it says "Welcome to the LLDB version 8 
>> documentation!". We also recently removed the "Why a New Debugger?" headline 
>> and that change isn't showing up either.
>> 
>> Would you mind taking a look?
>> 
>> thanks for your help,
>> Adrian
>> ___
>> lldb-dev mailing list
>> lldb-dev@lists.llvm.org
>> https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

[lldb-dev] (Deadline Monday!) Re: 2019 LLVM Dev Mtg (Bay Area) - Call for presentations

[Tanya Lattner via lldb-dev]

This is just a friendly reminder that the deadline is on Monday, August 12th. 

Thanks,
Tanya

> On Jul 2, 2019, at 8:54 AM, Tanya Lattner  wrote:
> 
> All developers and users of LLVM and related sub-projects are invited to 
> present at the 2019 LLVM Developers’ Meeting - Bay Area 
> .
> 
> We are looking for the following proposals:
> Technical Talks (25-30 minutes including Q):
> - On LLVM Infrastructure,Clang and all related sub-projects
> - On uses of LLVM in academia or industry
> - On new projects using Clang or LLVM
> Tutorials (60 minutes)
> - In depth talks on LLVM infrastructure or other core libraries
> Student Research Competition Technical Talks & Poster (20-25 minutes 
> including Q)
> Lightning Talks (5 minutes, no questions, no discussions)
> Birds of a Feather 
>  (30 minutes)**
> Panels (30-60 minutes)**
> Posters (1 hour)
> 
> 
> ** As the LLVM Developers’ Meeting as grown in size, we are moving away from 
> formal Birds of a Feather sessions in favor of smaller informal round table 
> discussions. These round table topics can be proposed closer to the LLVM 
> Developers’ Meeting and are designed for a smaller and more engaged group of 
> developers. Therefore, we are encouraging and recommending that instead of a 
> birds of a feather sessions, that developers consider proposing a panel 
> discussion. This would mean that several experts on a topic (and a moderator) 
> would get together and have an open discussion in front of an audience with 
> prepared questions and also questions from the audience. The program 
> committee will be looking for these proposals and giving favor to them over 
> more traditional birds of a feather proposals that we have had in the past.
> 
> Submission Requirements:
> The submission deadline is August 12, 2019 at 11:59PM PDT.
> 
> Please submit your proposal here:
> LLVM2019 Home 
> For each proposal, please submit a title, short abstract, submission type, 
> abstract for the website, include who the speakers or panel member/moderators 
> are, and provide a more detailed description of the talk through an extended 
> PDF abstract. We highly recommend you consult and follow the guide at the end 
> of this CFP when submitting your proposal.
> 
> Student Research Competition (SRC):
> We will again have a Student Research Competition (SRC). The SRC offers 
> students doing LLVM related research a non-academic platform to announce and 
> advertise their work as well as to discuss it with other researchers, 
> developers and users of LLVM. Students are asked to submit a proposal for a 
> 20-25 minute technical talk. There will be a prize for the best SRC talk.
> 
> FAQ
> 
> When will I be notified of acceptance?
> 
> Our goal is to notify all submissions by August 27, 2019.
> 
> What are panels?
> 
> Panels may discuss any topic as long as it’s relevant to LLVM or related 
> sub-projects. Panels can take many forms, but a common format is to begin 
> with short introductions from each panel member, and follow with an 
> interactive dialogue among the panelists and audience members. Panels should 
> consist of 3 people including a moderator.
> 
> Should I register if I have submitted a proposal?
> 
> We have 1 complimentary reserved  registration for each accepted technical 
> talk, BoF, or student research competition talk. Accepted tutorials have been 
> reserved 2 complimentary registrations. Panels have up to 3 reserved 
> registrations. There are no reserved registration spots for posters or 
> lightning talks. So please register any additional speakers or if you do not 
> have a reserved registration slot.
> 
> What if I registered and my talk got accepted?
> 
> We can refund your registration fee and instructions will be sent following 
> notification.  If you plan to attend even if your proposal is not accepted 
> and are worried about the event selling out, we suggest registering before 
> notification of acceptance.
> 
> What if I registered and my talk DID NOT get accepted?
> 
> We can refund your registration fee if you no longer wish to attend if you 
> contact the organizer by September 22, 2019.
> 
> What will be recorded?
> 
> All technical talks, tutorials, SRC talks, panels, and lightning talks will 
> be recorded. By submitting your proposal, you are giving us permission to 
> record if you present at the meeting. For SRC talks, you have the option to 
> delay publication of the slides and video for you talk for up to 12 months.
> 
> Who is on the program committee?
> 
> Our program committee chair is David Blaikie. The program committee is 
> composed of active developers of the LLVM, Clang, and related 
> sub-communities. The website will be updated with the list of the program 
> committee members.
> 
> I have a question, who do I contact?
> 
> Please email the LLVM Dev Mtg Organizers 

[lldb-dev] 2019 LLVM Dev Mtg (Bay Area) - Call for presentations

[Tanya Lattner via lldb-dev]

All developers and users of LLVM and related sub-projects are invited to 
present at the 2019 LLVM Developers’ Meeting - Bay Area 
.

We are looking for the following proposals:
Technical Talks (25-30 minutes including Q):
- On LLVM Infrastructure,Clang and all related sub-projects
- On uses of LLVM in academia or industry
- On new projects using Clang or LLVM
Tutorials (60 minutes)
- In depth talks on LLVM infrastructure or other core libraries
Student Research Competition Technical Talks & Poster (20-25 minutes including 
Q)
Lightning Talks (5 minutes, no questions, no discussions)
Birds of a Feather 
 (30 minutes)**
Panels (30-60 minutes)**
Posters (1 hour)


** As the LLVM Developers’ Meeting as grown in size, we are moving away from 
formal Birds of a Feather sessions in favor of smaller informal round table 
discussions. These round table topics can be proposed closer to the LLVM 
Developers’ Meeting and are designed for a smaller and more engaged group of 
developers. Therefore, we are encouraging and recommending that instead of a 
birds of a feather sessions, that developers consider proposing a panel 
discussion. This would mean that several experts on a topic (and a moderator) 
would get together and have an open discussion in front of an audience with 
prepared questions and also questions from the audience. The program committee 
will be looking for these proposals and giving favor to them over more 
traditional birds of a feather proposals that we have had in the past.

Submission Requirements:
The submission deadline is August 12, 2019 at 11:59PM PDT.

Please submit your proposal here:
LLVM2019 Home 
For each proposal, please submit a title, short abstract, submission type, 
abstract for the website, include who the speakers or panel member/moderators 
are, and provide a more detailed description of the talk through an extended 
PDF abstract. We highly recommend you consult and follow the guide at the end 
of this CFP when submitting your proposal.

Student Research Competition (SRC):
We will again have a Student Research Competition (SRC). The SRC offers 
students doing LLVM related research a non-academic platform to announce and 
advertise their work as well as to discuss it with other researchers, 
developers and users of LLVM. Students are asked to submit a proposal for a 
20-25 minute technical talk. There will be a prize for the best SRC talk.

FAQ

When will I be notified of acceptance?

Our goal is to notify all submissions by August 27, 2019.

What are panels?

Panels may discuss any topic as long as it’s relevant to LLVM or related 
sub-projects. Panels can take many forms, but a common format is to begin with 
short introductions from each panel member, and follow with an interactive 
dialogue among the panelists and audience members. Panels should consist of 3 
people including a moderator.

Should I register if I have submitted a proposal?

We have 1 complimentary reserved  registration for each accepted technical 
talk, BoF, or student research competition talk. Accepted tutorials have been 
reserved 2 complimentary registrations. Panels have up to 3 reserved 
registrations. There are no reserved registration spots for posters or 
lightning talks. So please register any additional speakers or if you do not 
have a reserved registration slot.

What if I registered and my talk got accepted?

We can refund your registration fee and instructions will be sent following 
notification.  If you plan to attend even if your proposal is not accepted and 
are worried about the event selling out, we suggest registering before 
notification of acceptance.

What if I registered and my talk DID NOT get accepted?

We can refund your registration fee if you no longer wish to attend if you 
contact the organizer by September 22, 2019.

What will be recorded?

All technical talks, tutorials, SRC talks, panels, and lightning talks will be 
recorded. By submitting your proposal, you are giving us permission to record 
if you present at the meeting. For SRC talks, you have the option to delay 
publication of the slides and video for you talk for up to 12 months.

Who is on the program committee?

Our program committee chair is David Blaikie. The program committee is composed 
of active developers of the LLVM, Clang, and related sub-communities. The 
website will be updated with the list of the program committee members.

I have a question, who do I contact?

Please email the LLVM Dev Mtg Organizers (devmtg-organiz...@lists.llvm.org), or 
the LLVM Developers’ Meeting mailing list. 
http://lists.llvm.org/mailman/listinfo/llvm-devmeeting 


Detailed guidance on writing a proposal for the LLVM Developers’ Meeting

Writing a proposal for the LLVM Developers’ Meeting

This document is a guide to help you submit the best 

[lldb-dev] 2019 LLVM Developers' Meeting (Bay Area) - Registration open

[Tanya Lattner via lldb-dev]

The LLVM Foundation is pleased to announce the 13th annual LLVM Developers’ 
Meeting in the Bay Area  on October 22-23, 
2019 in San Jose, CA. Registration is now open!
https://www.eventbrite.com/e/2019-llvm-developers-meeting-bay-area-tickets-63481303287
 


The LLVM Developers' Meeting is a bi-annual 2 day gathering of the entire LLVM 
Project community. The conference is organized by the LLVM Foundation and many 
volunteers within the LLVM community. Developers and users of LLVM, Clang, and 
related subprojects will enjoy attending interesting talks, impromptu 
discussions, and networking with the many members of our community. Whether you 
are a new to the LLVM project or a long time member, there is something for 
each attendee.

Tickets for the 2-day conference & reception are $350, and $300 for just the 
2-day conference. Student tickets are $75/$50 and we ask that you use your 
student email during registration. Please note that early registration will end 
on September 22 at 11:59 PDT and a late registration (and increased rates) will 
go into effect after this date. We highly encourage you to register early. 

Our ticket prices are subsidized by almost 50% by generous corporate sponsors 
 and public donations. However, for 
those in a position to pay the full ticket cost (or your employer), we invite 
you to select the Supporter Ticket option during registration. This ticket 
price is based upon our estimated cost for the event per person. By purchasing 
this ticket, it will allow us to keep ticket prices low and fund other programs 
such as more Educational Outreach, Travel Grants & Scholarships, Women in 
Compilers & Tools, and LLVM project infrastructure. 

New this year: We will have a newcomers orientation 

 on October 21, from 5:45-6:30PM. This is a short session for those attending 
the LLVM Developers' Meeting for the first time or for those who have not 
attended in awhile. This orientation will provide a conference overview, and 
useful information on how to participate and get involved during the 
conference. If you are interested in networking and meeting other new LLVM 
Developers, then you should attend this event. There is a separate EventBrite 
page 

 to register.

There will also be a Women in Compilers and Tools Workshop the day before on 
October 21st (~12:30-6:30pm). Details will be coming soon on this event.

What can you can expect at an LLVM Developers' Meeting?

• Technical Talks: These 20-30 minute talks cover all topics from core 
infrastructure talks, to project's using LLVM's infrastructure. Attendees will 
take away technical information that could be pertinent to their project or 
general interes. 
• Tutorials: Tutorials are 50 minute sessions that dive down deep into 
a technical topic. Expect in depth examples and explanations.
• Lightning Talks: These are fast 5 minute talks that give you a taste 
of a project or topic. Attendees will hear a wide range of topics and probably 
leave wanting to learn more.
• Panels: Panel sessions are guided discussions about a specific topic. 
The panel consists of ~3 developers who discuss a topic through prepared 
questions from a moderator. The audience is also given the opportunity to ask 
questions of the panel.
• Student Research Competition: Students present their research using 
LLVM or related subproject. These are usually 20 minute technical presentations 
with Q The audience will vote at the end for the winning presentation and 
paper.
• Poster Session: An hour long poster session where selected posted are 
on display.
• Round Table Discussions: Informal and impromptu discussions on a 
specific topic. During the conference there are set time slots where groups can 
organize to discuss a problem or topic.
• Evening Reception (October 22): After a full day if technical talks 
and discussions, join your fellow attendees for an evening reception to 
continue the conversation and meet even more attendees.

What types of people attend?
• Active developers of projects in the LLVM Umbrella (LLVM core, Clang, 
LLDB, libc++, compiler_rt, klee, lld, etc).
• Anyone interested in using these as part of another project.
• Students and Researchers
• Compiler, programming language, and runtime enthusiasts.
• Those interested in using compiler and toolchain technology in novel 
and interesting ways.

For future announcements or questions: Please sign up for the LLVM Developers’ 
Meeting mailing list 

Re: [lldb-dev] LLDB Website

[Tanya Lattner via lldb-dev]

> On May 7, 2019, at 4:48 PM, Jonas Devlieghere  wrote:
> 
> Thanks Tanya! I can see the website was updated. I've added a timestamp to 
> the Sphinx configuration, but it doesn't show up on the website. I'm not sure 
> whether that's because I did something wrong or because the site is still not 
> generated post-commit. 
> 

You are right. I needed to change one more thing to trigger the script. Can you 
try to change one thing now? 

> Did you change anything to where the Doxygen is generated? I updated all the 
> links to remove the /html/ form the URL and put a redirect in place, but now 
> the cpp docs are back at their old location: 
> https://lldb.llvm.org/cpp_reference/html/index.html 
> 
Yes! I forgot we had this conversation. Sorry about that. I just changed it 
back.

-Tanya



> 
> Thank,
> Jonas
> 
> On Tue, May 7, 2019 at 4:08 PM Tanya Lattner  > wrote:
> Ok, I believe everything should be working. So the cpp ref and python ref are 
> generated nightly. Sphinx/web is done post-commit. I just ran it by hand and 
> you can see the script output: 
> http://lists.llvm.org/pipermail/www-scripts/2019-May/007606.html 
> 
> 
> Is it possible for you to add a timestamp to the bottom of the sphinx 
> generated webpages? That would also make it easy to spot if it hasn’t run 
> recently. 
> 
> If you aren’t seeing something updated, please let me know. If you add new 
> targets, I have to do that manually as it's not automatic.
> 
> Thanks,
> Tanya
> 
> 
>> On May 7, 2019, at 9:28 AM, Jonas Devlieghere > > wrote:
>> 
>> Hey Tanya,
>> 
>> That's great. I see the Python documentation is online now! 
>> 
>> Unfortunately it appears that the Sphinx part still isn't updating. I pushed 
>> a bunch of changes last week and none have made it to the homepage yet. I 
>> checked the www-scripts mailing list but I don't see any failures for LLDB. 
>> Do you know what's up here?
>> 
>> Thanks,
>> Jonas
>> 
>> On Tue, May 7, 2019 at 12:19 AM Tanya Lattner > > wrote:
>> Ignore this. svn wasn’t actually updating the src tree. It works! I just 
>> need doxygen script to finish and it will be confirmed tonight.
>> 
>> 
>> -Tanya
>> 
>>> On May 6, 2019, at 11:55 PM, Tanya Lattner >> > wrote:
>>> 
>>> I’m not sure it is working. To clarify, nothing in LLVM should be compiled 
>>> to build the python docs correct? 
>>> 
>>> So I shouldn’t see this?
>>> Scanning dependencies of target liblldb_exports
>>> [  0%] Creating export file for liblldb
>>> [  0%] Built target liblldb_exports
>>> Scanning dependencies of target LLVMDemangle
>>> [  0%] Building CXX object 
>>> lib/Demangle/CMakeFiles/LLVMDemangle.dir/Demangle.cpp.o
>>> [  0%] Building CXX object 
>>> lib/Demangle/CMakeFiles/LLVMDemangle.dir/ItaniumDemangle.cpp.o
>>> [  0%] Building CXX object 
>>> lib/Demangle/CMakeFiles/LLVMDemangle.dir/MicrosoftDemangle.cpp.o
>>> [  0%] Building CXX object 
>>> lib/Demangle/CMakeFiles/LLVMDemangle.dir/MicrosoftDemangleNodes.cpp.o
>>> [  0%] Linking CXX static library ../libLLVMDemangle.a
>>> [  0%] Built target LLVMDemangle
>>> Scanning dependencies of target LLVMSupport
>>> [  0%] Building CXX object 
>>> lib/Support/CMakeFiles/LLVMSupport.dir/AArch64TargetParser.cpp.o
>>> [  0%] Building CXX object 
>>> lib/Support/CMakeFiles/LLVMSupport.dir/ARMTargetParser.cpp.o
>>> [  0%] Building CXX object 
>>> lib/Support/CMakeFiles/LLVMSupport.dir/AMDGPUMetadata.cpp.o
>>> [  0%] Building CXX object 
>>> lib/Support/CMakeFiles/LLVMSupport.dir/APFloat.cpp.o
>>> [  0%] Building CXX object 
>>> lib/Support/CMakeFiles/LLVMSupport.dir/APInt.cpp.o
>>> 
>>> Do I need any additional config options?
>>> 
>>> Thanks,
>>> Tanya
>>> 
 On May 3, 2019, at 8:58 AM, Jonas Devlieghere >>> > wrote:
 
 Hey Tanya,
 
 It appears the website is still stuck. It hasn't picked up my changes from 
 earlier this week. Please let me know if there's anything I can do to help.
 
 Thanks,
 Jonas
 
 On Wed, May 1, 2019 at 10:40 PM Tanya Lattner >>> > wrote:
 I will give this a shot. I did remove the changes before to prevent any 
 issue.
 
 -Tanya
 
> On Apr 29, 2019, at 10:26 AM, Jonas Devlieghere  > wrote:
> 
> I've merged the aforementioned patch. 
> 
> Tanya, can you give generating the python docs another shot?
> 
> Thanks,
> Jonas
> 
> On Fri, Apr 26, 2019 at 4:29 PM Jonas Devlieghere  > wrote:
> I've put up a patch to make it possible to generate the python reference 
> without building lldb at all: https://reviews.llvm.org/D61216 
> 
> 
> PS: The 

Re: [lldb-dev] LLDB Website

[Tanya Lattner via lldb-dev]

Ok, I believe everything should be working. So the cpp ref and python ref are 
generated nightly. Sphinx/web is done post-commit. I just ran it by hand and 
you can see the script output: 
http://lists.llvm.org/pipermail/www-scripts/2019-May/007606.html

Is it possible for you to add a timestamp to the bottom of the sphinx generated 
webpages? That would also make it easy to spot if it hasn’t run recently. 

If you aren’t seeing something updated, please let me know. If you add new 
targets, I have to do that manually as it's not automatic.

Thanks,
Tanya


> On May 7, 2019, at 9:28 AM, Jonas Devlieghere  wrote:
> 
> Hey Tanya,
> 
> That's great. I see the Python documentation is online now! 
> 
> Unfortunately it appears that the Sphinx part still isn't updating. I pushed 
> a bunch of changes last week and none have made it to the homepage yet. I 
> checked the www-scripts mailing list but I don't see any failures for LLDB. 
> Do you know what's up here?
> 
> Thanks,
> Jonas
> 
> On Tue, May 7, 2019 at 12:19 AM Tanya Lattner  > wrote:
> Ignore this. svn wasn’t actually updating the src tree. It works! I just need 
> doxygen script to finish and it will be confirmed tonight.
> 
> 
> -Tanya
> 
>> On May 6, 2019, at 11:55 PM, Tanya Lattner > > wrote:
>> 
>> I’m not sure it is working. To clarify, nothing in LLVM should be compiled 
>> to build the python docs correct? 
>> 
>> So I shouldn’t see this?
>> Scanning dependencies of target liblldb_exports
>> [  0%] Creating export file for liblldb
>> [  0%] Built target liblldb_exports
>> Scanning dependencies of target LLVMDemangle
>> [  0%] Building CXX object 
>> lib/Demangle/CMakeFiles/LLVMDemangle.dir/Demangle.cpp.o
>> [  0%] Building CXX object 
>> lib/Demangle/CMakeFiles/LLVMDemangle.dir/ItaniumDemangle.cpp.o
>> [  0%] Building CXX object 
>> lib/Demangle/CMakeFiles/LLVMDemangle.dir/MicrosoftDemangle.cpp.o
>> [  0%] Building CXX object 
>> lib/Demangle/CMakeFiles/LLVMDemangle.dir/MicrosoftDemangleNodes.cpp.o
>> [  0%] Linking CXX static library ../libLLVMDemangle.a
>> [  0%] Built target LLVMDemangle
>> Scanning dependencies of target LLVMSupport
>> [  0%] Building CXX object 
>> lib/Support/CMakeFiles/LLVMSupport.dir/AArch64TargetParser.cpp.o
>> [  0%] Building CXX object 
>> lib/Support/CMakeFiles/LLVMSupport.dir/ARMTargetParser.cpp.o
>> [  0%] Building CXX object 
>> lib/Support/CMakeFiles/LLVMSupport.dir/AMDGPUMetadata.cpp.o
>> [  0%] Building CXX object 
>> lib/Support/CMakeFiles/LLVMSupport.dir/APFloat.cpp.o
>> [  0%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/APInt.cpp.o
>> 
>> Do I need any additional config options?
>> 
>> Thanks,
>> Tanya
>> 
>>> On May 3, 2019, at 8:58 AM, Jonas Devlieghere >> > wrote:
>>> 
>>> Hey Tanya,
>>> 
>>> It appears the website is still stuck. It hasn't picked up my changes from 
>>> earlier this week. Please let me know if there's anything I can do to help.
>>> 
>>> Thanks,
>>> Jonas
>>> 
>>> On Wed, May 1, 2019 at 10:40 PM Tanya Lattner >> > wrote:
>>> I will give this a shot. I did remove the changes before to prevent any 
>>> issue.
>>> 
>>> -Tanya
>>> 
 On Apr 29, 2019, at 10:26 AM, Jonas Devlieghere >>> > wrote:
 
 I've merged the aforementioned patch. 
 
 Tanya, can you give generating the python docs another shot?
 
 Thanks,
 Jonas
 
 On Fri, Apr 26, 2019 at 4:29 PM Jonas Devlieghere >>> > wrote:
 I've put up a patch to make it possible to generate the python reference 
 without building lldb at all: https://reviews.llvm.org/D61216 
 
 
 PS: The website isn't updating anymore, is that because of the python 
 reference generation?
 
 On Wed, Apr 24, 2019 at 11:46 AM Ted Woodward >>> > wrote:
 That's the issue - lldb-python-doc depends on liblldb. From 
 docs/CMakeLists.txt:
 
 if(EPYDOC_EXECUTABLE)
   find_program(DOT_EXECUTABLE dot)
 if(DOT_EXECUTABLE)
   set(EPYDOC_OPTIONS ${EPYDOC_OPTIONS} --graph all --dotpath 
 ${DOT_EXECUTABLE})
 endif()
 set(DOC_DIR "${CMAKE_CURRENT_SOURCE_DIR}/doc")
 file(MAKE_DIRECTORY "${DOC_DIR}")
 #set(ENV{PYTHONPATH} 
 ${CMAKE_CURRENT_BINARY_DIR}/../../../lib/python2.7/site-packages)
 add_custom_target(lldb-python-doc
   ${EPYDOC_EXECUTABLE}
   --html
   lldb
   -o ${CMAKE_CURRENT_BINARY_DIR}/python_reference
   --name "LLDB python API"
   --url "http://lldb.llvm.org "
   ${EPYDOC_OPTIONS}
   DEPENDS swig_wrapper liblldb
   WORKING_DIRECTORY 
 ${CMAKE_CURRENT_BINARY_DIR}/../../../lib${LLVM_LIBDIR_SUFFIX}/python2.7/site-packages
   COMMENT "Generating LLDB Python API 

Re: [lldb-dev] LLDB Website

[Tanya Lattner via lldb-dev]

Ignore this. svn wasn’t actually updating the src tree. It works! I just need 
doxygen script to finish and it will be confirmed tonight.


-Tanya

> On May 6, 2019, at 11:55 PM, Tanya Lattner  wrote:
> 
> I’m not sure it is working. To clarify, nothing in LLVM should be compiled to 
> build the python docs correct? 
> 
> So I shouldn’t see this?
> Scanning dependencies of target liblldb_exports
> [  0%] Creating export file for liblldb
> [  0%] Built target liblldb_exports
> Scanning dependencies of target LLVMDemangle
> [  0%] Building CXX object 
> lib/Demangle/CMakeFiles/LLVMDemangle.dir/Demangle.cpp.o
> [  0%] Building CXX object 
> lib/Demangle/CMakeFiles/LLVMDemangle.dir/ItaniumDemangle.cpp.o
> [  0%] Building CXX object 
> lib/Demangle/CMakeFiles/LLVMDemangle.dir/MicrosoftDemangle.cpp.o
> [  0%] Building CXX object 
> lib/Demangle/CMakeFiles/LLVMDemangle.dir/MicrosoftDemangleNodes.cpp.o
> [  0%] Linking CXX static library ../libLLVMDemangle.a
> [  0%] Built target LLVMDemangle
> Scanning dependencies of target LLVMSupport
> [  0%] Building CXX object 
> lib/Support/CMakeFiles/LLVMSupport.dir/AArch64TargetParser.cpp.o
> [  0%] Building CXX object 
> lib/Support/CMakeFiles/LLVMSupport.dir/ARMTargetParser.cpp.o
> [  0%] Building CXX object 
> lib/Support/CMakeFiles/LLVMSupport.dir/AMDGPUMetadata.cpp.o
> [  0%] Building CXX object 
> lib/Support/CMakeFiles/LLVMSupport.dir/APFloat.cpp.o
> [  0%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/APInt.cpp.o
> 
> Do I need any additional config options?
> 
> Thanks,
> Tanya
> 
>> On May 3, 2019, at 8:58 AM, Jonas Devlieghere > > wrote:
>> 
>> Hey Tanya,
>> 
>> It appears the website is still stuck. It hasn't picked up my changes from 
>> earlier this week. Please let me know if there's anything I can do to help.
>> 
>> Thanks,
>> Jonas
>> 
>> On Wed, May 1, 2019 at 10:40 PM Tanya Lattner > > wrote:
>> I will give this a shot. I did remove the changes before to prevent any 
>> issue.
>> 
>> -Tanya
>> 
>>> On Apr 29, 2019, at 10:26 AM, Jonas Devlieghere >> > wrote:
>>> 
>>> I've merged the aforementioned patch. 
>>> 
>>> Tanya, can you give generating the python docs another shot?
>>> 
>>> Thanks,
>>> Jonas
>>> 
>>> On Fri, Apr 26, 2019 at 4:29 PM Jonas Devlieghere >> > wrote:
>>> I've put up a patch to make it possible to generate the python reference 
>>> without building lldb at all: https://reviews.llvm.org/D61216 
>>> 
>>> 
>>> PS: The website isn't updating anymore, is that because of the python 
>>> reference generation?
>>> 
>>> On Wed, Apr 24, 2019 at 11:46 AM Ted Woodward >> > wrote:
>>> That's the issue - lldb-python-doc depends on liblldb. From 
>>> docs/CMakeLists.txt:
>>> 
>>> if(EPYDOC_EXECUTABLE)
>>>   find_program(DOT_EXECUTABLE dot)
>>> if(DOT_EXECUTABLE)
>>>   set(EPYDOC_OPTIONS ${EPYDOC_OPTIONS} --graph all --dotpath 
>>> ${DOT_EXECUTABLE})
>>> endif()
>>> set(DOC_DIR "${CMAKE_CURRENT_SOURCE_DIR}/doc")
>>> file(MAKE_DIRECTORY "${DOC_DIR}")
>>> #set(ENV{PYTHONPATH} 
>>> ${CMAKE_CURRENT_BINARY_DIR}/../../../lib/python2.7/site-packages)
>>> add_custom_target(lldb-python-doc
>>>   ${EPYDOC_EXECUTABLE}
>>>   --html
>>>   lldb
>>>   -o ${CMAKE_CURRENT_BINARY_DIR}/python_reference
>>>   --name "LLDB python API"
>>>   --url "http://lldb.llvm.org "
>>>   ${EPYDOC_OPTIONS}
>>>   DEPENDS swig_wrapper liblldb
>>>   WORKING_DIRECTORY 
>>> ${CMAKE_CURRENT_BINARY_DIR}/../../../lib${LLVM_LIBDIR_SUFFIX}/python2.7/site-packages
>>>   COMMENT "Generating LLDB Python API reference with epydoc" VERBATIM
>>> )
>>> endif(EPYDOC_EXECUTABLE)
>>> 
>>> 
>>> > -Original Message-
>>> > From: lldb-dev >> > > On Behalf Of Pavel Labath
>>> > via lldb-dev
>>> > Sent: Wednesday, April 24, 2019 1:16 AM
>>> > To: Jonas Devlieghere >> > >; Tanya Lattner
>>> > mailto:tanyalatt...@llvm.org>>
>>> > Cc: LLDB mailto:lldb-dev@lists.llvm.org>>
>>> > Subject: [EXT] Re: [lldb-dev] LLDB Website
>>> > 
>>> > On 24/04/2019 03:19, Jonas Devlieghere via lldb-dev wrote:
>>> > >
>>> > >
>>> > > On Tue, Apr 23, 2019 at 6:04 PM Jonas Devlieghere
>>> > > mailto:jo...@devlieghere.com> 
>>> > > >> wrote:
>>> > >
>>> > >
>>> > >
>>> > > On Tue, Apr 23, 2019 at 5:43 PM Tanya Lattner 
>>> > > mailto:tanyalatt...@llvm.org>
>>> > > >> 
>>> > > wrote:
>>> > >
>>> > >
>>> > >
>>> > >> On Apr 23, 2019, at 5:06 PM, Jonas Devlieghere
>>> > >> mailto:jo...@devlieghere.com> 
>>> > >> >> wrote:
>>> > >>
>>> > >>
>>> > >>
>>> > >> On Tue, Apr 

Re: [lldb-dev] LLDB Website

[Tanya Lattner via lldb-dev]

I’m not sure it is working. To clarify, nothing in LLVM should be compiled to 
build the python docs correct? 

So I shouldn’t see this?
Scanning dependencies of target liblldb_exports
[  0%] Creating export file for liblldb
[  0%] Built target liblldb_exports
Scanning dependencies of target LLVMDemangle
[  0%] Building CXX object 
lib/Demangle/CMakeFiles/LLVMDemangle.dir/Demangle.cpp.o
[  0%] Building CXX object 
lib/Demangle/CMakeFiles/LLVMDemangle.dir/ItaniumDemangle.cpp.o
[  0%] Building CXX object 
lib/Demangle/CMakeFiles/LLVMDemangle.dir/MicrosoftDemangle.cpp.o
[  0%] Building CXX object 
lib/Demangle/CMakeFiles/LLVMDemangle.dir/MicrosoftDemangleNodes.cpp.o
[  0%] Linking CXX static library ../libLLVMDemangle.a
[  0%] Built target LLVMDemangle
Scanning dependencies of target LLVMSupport
[  0%] Building CXX object 
lib/Support/CMakeFiles/LLVMSupport.dir/AArch64TargetParser.cpp.o
[  0%] Building CXX object 
lib/Support/CMakeFiles/LLVMSupport.dir/ARMTargetParser.cpp.o
[  0%] Building CXX object 
lib/Support/CMakeFiles/LLVMSupport.dir/AMDGPUMetadata.cpp.o
[  0%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/APFloat.cpp.o
[  0%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/APInt.cpp.o

Do I need any additional config options?

Thanks,
Tanya

> On May 3, 2019, at 8:58 AM, Jonas Devlieghere  wrote:
> 
> Hey Tanya,
> 
> It appears the website is still stuck. It hasn't picked up my changes from 
> earlier this week. Please let me know if there's anything I can do to help.
> 
> Thanks,
> Jonas
> 
> On Wed, May 1, 2019 at 10:40 PM Tanya Lattner  > wrote:
> I will give this a shot. I did remove the changes before to prevent any issue.
> 
> -Tanya
> 
>> On Apr 29, 2019, at 10:26 AM, Jonas Devlieghere > > wrote:
>> 
>> I've merged the aforementioned patch. 
>> 
>> Tanya, can you give generating the python docs another shot?
>> 
>> Thanks,
>> Jonas
>> 
>> On Fri, Apr 26, 2019 at 4:29 PM Jonas Devlieghere > > wrote:
>> I've put up a patch to make it possible to generate the python reference 
>> without building lldb at all: https://reviews.llvm.org/D61216 
>> 
>> 
>> PS: The website isn't updating anymore, is that because of the python 
>> reference generation?
>> 
>> On Wed, Apr 24, 2019 at 11:46 AM Ted Woodward > > wrote:
>> That's the issue - lldb-python-doc depends on liblldb. From 
>> docs/CMakeLists.txt:
>> 
>> if(EPYDOC_EXECUTABLE)
>>   find_program(DOT_EXECUTABLE dot)
>> if(DOT_EXECUTABLE)
>>   set(EPYDOC_OPTIONS ${EPYDOC_OPTIONS} --graph all --dotpath 
>> ${DOT_EXECUTABLE})
>> endif()
>> set(DOC_DIR "${CMAKE_CURRENT_SOURCE_DIR}/doc")
>> file(MAKE_DIRECTORY "${DOC_DIR}")
>> #set(ENV{PYTHONPATH} 
>> ${CMAKE_CURRENT_BINARY_DIR}/../../../lib/python2.7/site-packages)
>> add_custom_target(lldb-python-doc
>>   ${EPYDOC_EXECUTABLE}
>>   --html
>>   lldb
>>   -o ${CMAKE_CURRENT_BINARY_DIR}/python_reference
>>   --name "LLDB python API"
>>   --url "http://lldb.llvm.org "
>>   ${EPYDOC_OPTIONS}
>>   DEPENDS swig_wrapper liblldb
>>   WORKING_DIRECTORY 
>> ${CMAKE_CURRENT_BINARY_DIR}/../../../lib${LLVM_LIBDIR_SUFFIX}/python2.7/site-packages
>>   COMMENT "Generating LLDB Python API reference with epydoc" VERBATIM
>> )
>> endif(EPYDOC_EXECUTABLE)
>> 
>> 
>> > -Original Message-
>> > From: lldb-dev > > > On Behalf Of Pavel Labath
>> > via lldb-dev
>> > Sent: Wednesday, April 24, 2019 1:16 AM
>> > To: Jonas Devlieghere > > >; Tanya Lattner
>> > mailto:tanyalatt...@llvm.org>>
>> > Cc: LLDB mailto:lldb-dev@lists.llvm.org>>
>> > Subject: [EXT] Re: [lldb-dev] LLDB Website
>> > 
>> > On 24/04/2019 03:19, Jonas Devlieghere via lldb-dev wrote:
>> > >
>> > >
>> > > On Tue, Apr 23, 2019 at 6:04 PM Jonas Devlieghere
>> > > mailto:jo...@devlieghere.com> 
>> > > >> wrote:
>> > >
>> > >
>> > >
>> > > On Tue, Apr 23, 2019 at 5:43 PM Tanya Lattner > > > 
>> > > >> wrote:
>> > >
>> > >
>> > >
>> > >> On Apr 23, 2019, at 5:06 PM, Jonas Devlieghere
>> > >> mailto:jo...@devlieghere.com> 
>> > >> >> wrote:
>> > >>
>> > >>
>> > >>
>> > >> On Tue, Apr 23, 2019 at 5:00 PM Tanya Lattner
>> > >> mailto:tanyalatt...@llvm.org> 
>> > >> >> wrote:
>> > >>
>> > >>
>> > >>
>> > >>> On Apr 23, 2019, at 11:54 AM, Jonas Devlieghere
>> > >>> mailto:jo...@devlieghere.com> 
>> > >>> >>
>> > wrote:
>> > >>>
>> > >>> 

Re: [lldb-dev] LLDB Website

[Tanya Lattner via lldb-dev]

I will give this a shot. I did remove the changes before to prevent any issue.

-Tanya

> On Apr 29, 2019, at 10:26 AM, Jonas Devlieghere  wrote:
> 
> I've merged the aforementioned patch. 
> 
> Tanya, can you give generating the python docs another shot?
> 
> Thanks,
> Jonas
> 
> On Fri, Apr 26, 2019 at 4:29 PM Jonas Devlieghere  > wrote:
> I've put up a patch to make it possible to generate the python reference 
> without building lldb at all: https://reviews.llvm.org/D61216 
> 
> 
> PS: The website isn't updating anymore, is that because of the python 
> reference generation?
> 
> On Wed, Apr 24, 2019 at 11:46 AM Ted Woodward  > wrote:
> That's the issue - lldb-python-doc depends on liblldb. From 
> docs/CMakeLists.txt:
> 
> if(EPYDOC_EXECUTABLE)
>   find_program(DOT_EXECUTABLE dot)
> if(DOT_EXECUTABLE)
>   set(EPYDOC_OPTIONS ${EPYDOC_OPTIONS} --graph all --dotpath 
> ${DOT_EXECUTABLE})
> endif()
> set(DOC_DIR "${CMAKE_CURRENT_SOURCE_DIR}/doc")
> file(MAKE_DIRECTORY "${DOC_DIR}")
> #set(ENV{PYTHONPATH} 
> ${CMAKE_CURRENT_BINARY_DIR}/../../../lib/python2.7/site-packages)
> add_custom_target(lldb-python-doc
>   ${EPYDOC_EXECUTABLE}
>   --html
>   lldb
>   -o ${CMAKE_CURRENT_BINARY_DIR}/python_reference
>   --name "LLDB python API"
>   --url "http://lldb.llvm.org "
>   ${EPYDOC_OPTIONS}
>   DEPENDS swig_wrapper liblldb
>   WORKING_DIRECTORY 
> ${CMAKE_CURRENT_BINARY_DIR}/../../../lib${LLVM_LIBDIR_SUFFIX}/python2.7/site-packages
>   COMMENT "Generating LLDB Python API reference with epydoc" VERBATIM
> )
> endif(EPYDOC_EXECUTABLE)
> 
> 
> > -Original Message-
> > From: lldb-dev  > > On Behalf Of Pavel Labath
> > via lldb-dev
> > Sent: Wednesday, April 24, 2019 1:16 AM
> > To: Jonas Devlieghere  > >; Tanya Lattner
> > mailto:tanyalatt...@llvm.org>>
> > Cc: LLDB mailto:lldb-dev@lists.llvm.org>>
> > Subject: [EXT] Re: [lldb-dev] LLDB Website
> > 
> > On 24/04/2019 03:19, Jonas Devlieghere via lldb-dev wrote:
> > >
> > >
> > > On Tue, Apr 23, 2019 at 6:04 PM Jonas Devlieghere
> > > mailto:jo...@devlieghere.com> 
> > > >> wrote:
> > >
> > >
> > >
> > > On Tue, Apr 23, 2019 at 5:43 PM Tanya Lattner  > > 
> > > >> wrote:
> > >
> > >
> > >
> > >> On Apr 23, 2019, at 5:06 PM, Jonas Devlieghere
> > >> mailto:jo...@devlieghere.com> 
> > >> >> wrote:
> > >>
> > >>
> > >>
> > >> On Tue, Apr 23, 2019 at 5:00 PM Tanya Lattner
> > >> mailto:tanyalatt...@llvm.org> 
> > >> >> wrote:
> > >>
> > >>
> > >>
> > >>> On Apr 23, 2019, at 11:54 AM, Jonas Devlieghere
> > >>> mailto:jo...@devlieghere.com> 
> > >>> >>
> > wrote:
> > >>>
> > >>> Hey Tanya,
> > >>>
> > >>> On Tue, Apr 23, 2019 at 11:51 Tanya Lattner
> > >>> mailto:tanyalatt...@llvm.org> 
> > >>> >> wrote:
> > >>>
> > >>> Jonas,
> > >>>
> > >>> Ignore what I said before as these do need to be
> > >>> separate targets. It appears the new targets are
> > >>> running doxygen. This isn’t something we typically do
> > >>> as a post commit hook since it takes awhile. I’ll
> > >>> need to do this via the doxygen nightly script. Any
> > >>> concerns?
> > >>>
> > >>> That sounds perfect. Can we still do the regular website
> > >>> post commit?
> > >>
> > >> Yes, so it will do docs-lldb-html on every commit.
> > >>
> > >>
> > >> Perfect!
> > >>
> > >>
> > >> So I am able to generate the cpp reference docs:
> > >> https://lldb.llvm.org/cpp_reference/index.html 
> > >> 
> > >>
> > >> However, the main website links to
> > >> https://lldb.llvm.org/cpp_reference/html/index.html 
> > >> . Do
> > >> you want the html in that url? I can change the alias. We
> > >> strip for other doxygen.
> > >>
> > >>
> > >> Let's keep it without the html. I'll update a link on the
> > >> website and add a redirect.
> > >>
> > >>
> > >> As for python docs, what is required to build those? It's
> > >> not showing up as a target for me.
> > >>
> > >>
> > >> This is probably because you don't have 

Re: [lldb-dev] LLDB Website

[Tanya Lattner via lldb-dev]

> On Apr 23, 2019, at 5:06 PM, Jonas Devlieghere  wrote:
> 
> 
> 
> On Tue, Apr 23, 2019 at 5:00 PM Tanya Lattner  > wrote:
> 
> 
>> On Apr 23, 2019, at 11:54 AM, Jonas Devlieghere > > wrote:
>> 
>> Hey Tanya,
>> 
>> On Tue, Apr 23, 2019 at 11:51 Tanya Lattner > > wrote:
>> Jonas,
>> 
>> Ignore what I said before as these do need to be separate targets. It 
>> appears the new targets are running doxygen. This isn’t something we 
>> typically do as a post commit hook since it takes awhile. I’ll need to do 
>> this via the doxygen nightly script. Any concerns?
>>   
>> That sounds perfect. Can we still do the regular website post commit? 
> 
> Yes, so it will do docs-lldb-html on every commit.
> 
> Perfect! 
>  
> 
> So I am able to generate the cpp reference docs: 
> https://lldb.llvm.org/cpp_reference/index.html 
> 
> 
> However, the main website links to 
> https://lldb.llvm.org/cpp_reference/html/index.html 
> . Do you want the html 
> in that url? I can change the alias. We strip for other doxygen.
> 
> Let's keep it without the html. I'll update a link on the website and add a 
> redirect. 
>  
> 
> As for python docs, what is required to build those? It's not showing up as a 
> target for me.
> 
> This is probably because you don't have `epydoc` installed (sudo pip install 
> epydoc). 
> I think you'll have to re-run cmake after for it to pick it up. The 
> corresponding target should then be `lldb-python-doc`. 
> 
> https://lldb.llvm.org/cpp_reference/index.html 
> 
Well installing epydoc did the trick, but I don’t think the doxygen script is 
the right place for this target. I have not dug into it yet but it appears to 
require some LLVM libraries and is building those. I’m letting it finish to 
verify it builds but I’ll have to sort out the best way of doing this on the 
server. We have other scripts that generate other documentation that build 
parts of LLVM. Ideally, I would want to leverage that and reduce build times.

-Tanya
>  
> 
> Thanks,
> Tanya
> 
> Thanks again for doing this.
> 
> Cheers,
> Jonas
>  
> 
> 
>> 
>> 
>> -Tanya
>> 
>> Thank you! 
>> 
>> 
>>> On Apr 23, 2019, at 11:45 AM, Tanya Lattner >> > wrote:
>>> 
>>> Anytime new targets are added, the script has to be modified. Is there a 
>>> way you can put them all under a top level html target? Or is there a 
>>> reason not to?
>>> 
>>> -Tanya
>>> 
 On Apr 19, 2019, at 12:17 PM, Jonas Devlieghere >>> > wrote:
 
 Hey Tanya,
 
 Thanks again for migrating the LLDB website so it is generated with Sphinx!
 
 I made a change yesterday that hasn't been propagated yet. It looks like 
 it might have something to do with 
 http://lists.llvm.org/pipermail/www-scripts/2019-April/007524.html 
 . 
 
 Also, as the result of this change the following two links are broken:
 
 https://lldb.llvm.org/cpp_reference/ 
 https://lldb.llvm.org/python_reference/ 
 
 
 Could we make the script generate those two folders as well? The 
 corresponding CMake target are lldb-cpp-doc and lldb-python-doc.
 
 Thank you,Or
 Jonas
 
 PS: I've included lldb-dev in CC so everyone knows we're working on the 
 missing documentation. 
>>> 
>> 
>> -- 
>> Sent from my iPhone
> 

___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] LLDB Website

[Tanya Lattner via lldb-dev]

> On Apr 23, 2019, at 11:54 AM, Jonas Devlieghere  wrote:
> 
> Hey Tanya,
> 
> On Tue, Apr 23, 2019 at 11:51 Tanya Lattner  > wrote:
> Jonas,
> 
> Ignore what I said before as these do need to be separate targets. It appears 
> the new targets are running doxygen. This isn’t something we typically do as 
> a post commit hook since it takes awhile. I’ll need to do this via the 
> doxygen nightly script. Any concerns?
>   
> That sounds perfect. Can we still do the regular website post commit? 

Yes, so it will do docs-lldb-html on every commit.

So I am able to generate the cpp reference docs: 
https://lldb.llvm.org/cpp_reference/index.html

However, the main website links to 
https://lldb.llvm.org/cpp_reference/html/index.html. Do you want the html in 
that url? I can change the alias. We strip for other doxygen.

As for python docs, what is required to build those? It's not showing up as a 
target for me.

Thanks,
Tanya





> 
> 
> -Tanya
> 
> Thank you! 
> 
> 
>> On Apr 23, 2019, at 11:45 AM, Tanya Lattner > > wrote:
>> 
>> Anytime new targets are added, the script has to be modified. Is there a way 
>> you can put them all under a top level html target? Or is there a reason not 
>> to?
>> 
>> -Tanya
>> 
>>> On Apr 19, 2019, at 12:17 PM, Jonas Devlieghere >> > wrote:
>>> 
>>> Hey Tanya,
>>> 
>>> Thanks again for migrating the LLDB website so it is generated with Sphinx!
>>> 
>>> I made a change yesterday that hasn't been propagated yet. It looks like it 
>>> might have something to do with 
>>> http://lists.llvm.org/pipermail/www-scripts/2019-April/007524.html 
>>> . 
>>> 
>>> Also, as the result of this change the following two links are broken:
>>> 
>>> https://lldb.llvm.org/cpp_reference/ 
>>> https://lldb.llvm.org/python_reference/ 
>>> 
>>> 
>>> Could we make the script generate those two folders as well? The 
>>> corresponding CMake target are lldb-cpp-doc and lldb-python-doc.
>>> 
>>> Thank you,Or
>>> Jonas
>>> 
>>> PS: I've included lldb-dev in CC so everyone knows we're working on the 
>>> missing documentation. 
>> 
> 
> -- 
> Sent from my iPhone

___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] LLDB Website

[Tanya Lattner via lldb-dev]

Jonas,

Ignore what I said before as these do need to be separate targets. It appears 
the new targets are running doxygen. This isn’t something we typically do as a 
post commit hook since it takes awhile. I’ll need to do this via the doxygen 
nightly script. Any concerns?

-Tanya

> On Apr 23, 2019, at 11:45 AM, Tanya Lattner  wrote:
> 
> Anytime new targets are added, the script has to be modified. Is there a way 
> you can put them all under a top level html target? Or is there a reason not 
> to?
> 
> -Tanya
> 
>> On Apr 19, 2019, at 12:17 PM, Jonas Devlieghere > > wrote:
>> 
>> Hey Tanya,
>> 
>> Thanks again for migrating the LLDB website so it is generated with Sphinx!
>> 
>> I made a change yesterday that hasn't been propagated yet. It looks like it 
>> might have something to do with 
>> http://lists.llvm.org/pipermail/www-scripts/2019-April/007524.html 
>> . 
>> 
>> Also, as the result of this change the following two links are broken:
>> 
>> https://lldb.llvm.org/cpp_reference/ 
>> https://lldb.llvm.org/python_reference/ 
>> 
>> 
>> Could we make the script generate those two folders as well? The 
>> corresponding CMake target are lldb-cpp-doc and lldb-python-doc.
>> 
>> Thank you,Or
>> Jonas
>> 
>> PS: I've included lldb-dev in CC so everyone knows we're working on the 
>> missing documentation. 
> 

___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] LLDB Website

[Tanya Lattner via lldb-dev]

Anytime new targets are added, the script has to be modified. Is there a way 
you can put them all under a top level html target? Or is there a reason not to?

-Tanya

> On Apr 19, 2019, at 12:17 PM, Jonas Devlieghere  wrote:
> 
> Hey Tanya,
> 
> Thanks again for migrating the LLDB website so it is generated with Sphinx!
> 
> I made a change yesterday that hasn't been propagated yet. It looks like it 
> might have something to do with 
> http://lists.llvm.org/pipermail/www-scripts/2019-April/007524.html 
> . 
> 
> Also, as the result of this change the following two links are broken:
> 
> https://lldb.llvm.org/cpp_reference/ 
> https://lldb.llvm.org/python_reference/ 
> 
> 
> Could we make the script generate those two folders as well? The 
> corresponding CMake target are lldb-cpp-doc and lldb-python-doc.
> 
> Thank you,Or
> Jonas
> 
> PS: I've included lldb-dev in CC so everyone knows we're working on the 
> missing documentation. 

___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

[lldb-dev] Mentors and projects needed for Season of Docs

[Tanya Lattner via lldb-dev]

LLVM Developers,

Google has a new program called Season of Docs 
. To summarize, this program 
brings together open source communities and technical writers to the benefit of 
both. Open source communities are paired with technical writers on technical 
writing projects proposed by the open source community. 

As good documentation is key to getting new developers involved with the LLVM 
Project and also helping existing developers, I feel it would be beneficial if 
LLVM participated in this program.

Here is where we need your help! For our application, we need a list of open 
projects that are a good fit for technical writers. Here is the description of 
what the open projects proposals consist of:
https://developers.google.com/season-of-docs/docs/project-ideas 

Second, we need mentors to work with the technical writers as they work on the 
projects. Even if you don’t want to be involved in drafting the ideas, the 
technical writers will need mentors to help guide them and answer LLVM related 
questions.

If you have an idea for a project, please send me your outline. We are 
currently creating a web page for our application. Or if you just are 
interested in being a mentor (no commitment until you see the list of 
projects), then send me a quick email. The deadline for the application is 
April 23, 2019 at 20:00 UTC  (so not much time).

If you have questions, please let me know. As this program is new, we are all 
trying to figure it out :)

Thank you,
Tanya Lattner___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

[lldb-dev] Moderator needed for lldb-commits

[Tanya Lattner via lldb-dev]

LLDB Developers,

Moderators are needed for the lldb-commits mailing list. Is anyone interested 
in helping out?

Thanks,
Tanya
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

[lldb-dev] 2018 LLVM Developers' Meeting - Bay Area, October 17-18

[Tanya Lattner via lldb-dev]

The LLVM Foundation is pleased to announce the 12th annual LLVM Developers’ 
Meeting in the Bay Area  on October 17-18, 
2018 in San Jose, CA. 

Registration 

 will be opening Friday, June 15th at 9:00AM PDT. Please note that early 
registration will end on September 17th at 12:00AM PDT and a late registration 
will go into effect after this date. We highly encourage you to register early 
to avoid the increased prices.

The LLVM Developers' Meeting is a bi-annual 2 day gathering of the entire LLVM 
Project community. The conference is organized by the LLVM Foundation and many 
volunteers within the LLVM community. Developers and users of LLVM, Clang, and 
related subprojects will enjoy attending interesting talks, impromptu 
discussions, and networking with the many members of our community. Whether you 
are a 
new to the LLVM project or a long time member, there is something for each 
attendee.

New this year: There will also be a Women in Compilers and Tools Workshop the 
day before on October 16th (~1-6:30pm, details coming soon).

What can you can expect at an LLVM Developers' Meeting?

Technical Talks: These 20-30 minute talks cover all topics from core 
infrastructure talks, to project's using LLVM's infrastructure. Attendees will 
take away technical information that could be pertinent to their project or 
general interes. 
Tutorials: Tutorials are 50 minute sessions that dive down deep into a 
technical topic. Expect in depth examples and explanations.
Lightning Talks: These are fast 5 minute talks that give you a taste of a 
project or topic. Attendees will hear a wide range of topics and probably leave 
wanting to learn more.
Birds of a Feather (BoF): BoF sessions are more formal guided discussions about 
a specific topic. The presenter typically has slides to guide the discussion. 
The audience is given the opportunity to participate in the discussion.
Student Research Competition: Students present their research using LLVM or 
related subproject. These are usually 20 minute technical presentations with 
Q The audence will vote at the end for the winning presentation and paper.
Poster Session: An hour long poster session where selected posted are on 
display.
Round Table Discussions: Informal and impromptu discussions on a specific 
topic. During the conference there are set time slots where groups can organize 
to discuss a problem or topic.
Evening Reception (October 17): After a full day if technical talks and 
discussions, join your fellow attendees for an evening reception to continue 
the conversation and meet even more attendees.
What types of people attend?
Active developers of projects in the LLVM Umbrella (LLVM core, Clang, LLDB, 
libc++, compiler_rt, klee, lld, etc).
Anyone interested in using these as part of another project.
Students and Researchers
Compiler, programming language, and runtime enthusiasts.
Those interested in using compiler and toolchain technology in novel and 
interesting ways.

For future announcements or questions: Please sign up for the LLVM Developers’ 
Meeting mailing list 
.___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

[lldb-dev] Need one more moderator volunteer!

[Tanya Lattner via lldb-dev]

Can anyone help with this session?

Session 10 (2:10-3:40PM, General Session)
Adding Index‐While‐Building and Refactoring to Clang
Advancing Clangd: Bringing persisted indexing to Clang tooling

Thanks,
Tanya


> On Oct 10, 2017, at 5:27 PM, Tanya Lattner  wrote:
> 
> Just 2 more slots to fill! Any volunteers?
> 
> Session 7 (10:00-10:45AM, Technical Track)
> eval() in C++
> 
> Session 10 (2:10-3:40PM, General Session)
> Adding Index‐While‐Building and Refactoring to Clang
> Advancing Clangd: Bringing persisted indexing to Clang tooling
> 
> -Tanya
> 
>> On Oct 4, 2017, at 9:03 PM, Tanya Lattner > > wrote:
>> 
>> Thank you for those who have volunteered. I am still in need of people for 
>> the following sessions:
>> 
>> Session 7 (10:00-10:45AM, Technical Track)
>> eval() in C++
>> 
>> Session 8 (11:10AM-12:40PM, General Session)
>> Implementing Swift Generics
>> The Further Benefits of Explicit Modularization: Modular Codegen
>> 
>> Session 10 (2:10-3:40PM, General Session)
>> Adding Index‐While‐Building and Refactoring to Clang
>> Advancing Clangd: Bringing persisted indexing to Clang tooling
>> 
>> Session 11 (2:10-3:40PM, Technical Track)
>> Enabling Parallel Computing in Chapel with Clang and LLVM
>>  Challenges when building an LLVM bitcode Obfuscator
>> 
>> -Tanya
>> 
>> 
>>> On Sep 26, 2017, at 1:49 AM, Tanya Lattner >> > wrote:
>>> 
>>> The 2017 LLVM Developers’ Meeting relies on volunteers to keep things 
>>> running smoothly. Moderators are critical to this as they keep speakers on 
>>> track and facilitate Q after the talk. I’m looking for community members 
>>> who would be attending specific talks anyway, to volunteer to moderate the 
>>> session.
>>> 
>>> If you are interested in volunteering, please respond to this email with 
>>> your first and second choice session times. You will moderate all talks 
>>> during that time slot and they will occur back to back in the same room. 
>>> Moderators introduce the speaker, give the speaker warnings about time, and 
>>> facilitate Q by running microphones.
>>> 
>>> Full schedule here: https://2017llvmdevmtg.sched.com 
>>> 
>>> 
>>> Session 1 (10:30-12:45, Technical Track)
>>> Dominator Trees and incremental updates that transcend time
>>> GlobalISel: Past, Present, and Future
>>> XRay in LLVM: Function Call Tracing and Analysis
>>> 
>>> Session 2 (2:15-4:00PM, General Session)
>>> LIGHTNING TALKS
>>> LLVM Compile-Time: Challenges. Improvements. Outlook.
>>> 
>>> Session 3 (2:15-4:00PM, Technical Track)
>>> Tutorial: Welcome to the back-end: The LLVM machine representation.
>>> Scale, Robust and Regression-Free Loop Optimizations for Scientific Fortran 
>>> and Modern C++
>>> 
>>> Session 4 (4:20-5:50PM, General Session)
>>> The Type Sanitizer: Free Yourself from -fno-strict-aliasing
>>> Structure-aware fuzzing for Clang and LLVM with libprotobuf-mutator
>>> 
>>> Session 5 (4:20-6:05PM, General Session)
>>> Vectorizing Loops with VPlan – Current State and Next Steps
>>> Tutorial: Writing Great Machine Schedulers
>>> 
>>> Session 6 (9:00-10:45AM, General Session)
>>> Falcon: An optimizing Java JIT
>>> Apple LLVM GPU Compiler: Embedded Dragons
>>> 
>>> Session 7 (10:00-10:45AM, Technical Track)
>>> eval() in C++
>>> 
>>> Session 8 (11:10AM-12:40PM, General Session)
>>> Implementing Swift Generics
>>> The Further Benefits of Explicit Modularization: Modular Codegen
>>> 
>>> Session 9 (11:10AM-12:40PM, Technical Track)
>>> Bringing link-time optimization to the embedded world: (Thin)LTO with 
>>> Linker Scripts
>>> lld: A Fast, Simple, and Portable Linker
>>> 
>>> Session 10 (2:10-3:40PM, General Session)
>>> Adding Index‐While‐Building and Refactoring to Clang
>>> Advancing Clangd: Bringing persisted indexing to Clang tooling
>>> 
>>> Session 11 (2:10-3:40PM, Technical Track)
>>> Enabling Parallel Computing in Chapel with Clang and LLVM
>>>  Challenges when building an LLVM bitcode Obfuscator
>>> 
>>> Session 12 (4:40-6:25PM, General Session)
>>> Building Your Product Around LLVM Releases
>>> Tutorial: Head First into GlobalISel
>>> 
>>> 
>>> Thanks,
>>> Tanya
>>> 
>> 
> 

___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] Moderators for the 2017 LLVM Developers' Mtg Needed! (2 slots left!)

[Tanya Lattner via lldb-dev]

Just 2 more slots to fill! Any volunteers?

Session 7 (10:00-10:45AM, Technical Track)
eval() in C++

Session 10 (2:10-3:40PM, General Session)
Adding Index‐While‐Building and Refactoring to Clang
Advancing Clangd: Bringing persisted indexing to Clang tooling

-Tanya

> On Oct 4, 2017, at 9:03 PM, Tanya Lattner  wrote:
> 
> Thank you for those who have volunteered. I am still in need of people for 
> the following sessions:
> 
> Session 7 (10:00-10:45AM, Technical Track)
> eval() in C++
> 
> Session 8 (11:10AM-12:40PM, General Session)
> Implementing Swift Generics
> The Further Benefits of Explicit Modularization: Modular Codegen
> 
> Session 10 (2:10-3:40PM, General Session)
> Adding Index‐While‐Building and Refactoring to Clang
> Advancing Clangd: Bringing persisted indexing to Clang tooling
> 
> Session 11 (2:10-3:40PM, Technical Track)
> Enabling Parallel Computing in Chapel with Clang and LLVM
>  Challenges when building an LLVM bitcode Obfuscator
> 
> -Tanya
> 
> 
>> On Sep 26, 2017, at 1:49 AM, Tanya Lattner > > wrote:
>> 
>> The 2017 LLVM Developers’ Meeting relies on volunteers to keep things 
>> running smoothly. Moderators are critical to this as they keep speakers on 
>> track and facilitate Q after the talk. I’m looking for community members 
>> who would be attending specific talks anyway, to volunteer to moderate the 
>> session.
>> 
>> If you are interested in volunteering, please respond to this email with 
>> your first and second choice session times. You will moderate all talks 
>> during that time slot and they will occur back to back in the same room. 
>> Moderators introduce the speaker, give the speaker warnings about time, and 
>> facilitate Q by running microphones.
>> 
>> Full schedule here: https://2017llvmdevmtg.sched.com 
>> 
>> 
>> Session 1 (10:30-12:45, Technical Track)
>> Dominator Trees and incremental updates that transcend time
>> GlobalISel: Past, Present, and Future
>> XRay in LLVM: Function Call Tracing and Analysis
>> 
>> Session 2 (2:15-4:00PM, General Session)
>> LIGHTNING TALKS
>> LLVM Compile-Time: Challenges. Improvements. Outlook.
>> 
>> Session 3 (2:15-4:00PM, Technical Track)
>> Tutorial: Welcome to the back-end: The LLVM machine representation.
>> Scale, Robust and Regression-Free Loop Optimizations for Scientific Fortran 
>> and Modern C++
>> 
>> Session 4 (4:20-5:50PM, General Session)
>> The Type Sanitizer: Free Yourself from -fno-strict-aliasing
>> Structure-aware fuzzing for Clang and LLVM with libprotobuf-mutator
>> 
>> Session 5 (4:20-6:05PM, General Session)
>> Vectorizing Loops with VPlan – Current State and Next Steps
>> Tutorial: Writing Great Machine Schedulers
>> 
>> Session 6 (9:00-10:45AM, General Session)
>> Falcon: An optimizing Java JIT
>> Apple LLVM GPU Compiler: Embedded Dragons
>> 
>> Session 7 (10:00-10:45AM, Technical Track)
>> eval() in C++
>> 
>> Session 8 (11:10AM-12:40PM, General Session)
>> Implementing Swift Generics
>> The Further Benefits of Explicit Modularization: Modular Codegen
>> 
>> Session 9 (11:10AM-12:40PM, Technical Track)
>> Bringing link-time optimization to the embedded world: (Thin)LTO with Linker 
>> Scripts
>> lld: A Fast, Simple, and Portable Linker
>> 
>> Session 10 (2:10-3:40PM, General Session)
>> Adding Index‐While‐Building and Refactoring to Clang
>> Advancing Clangd: Bringing persisted indexing to Clang tooling
>> 
>> Session 11 (2:10-3:40PM, Technical Track)
>> Enabling Parallel Computing in Chapel with Clang and LLVM
>>  Challenges when building an LLVM bitcode Obfuscator
>> 
>> Session 12 (4:40-6:25PM, General Session)
>> Building Your Product Around LLVM Releases
>> Tutorial: Head First into GlobalISel
>> 
>> 
>> Thanks,
>> Tanya
>> 
> 

___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] Moderators for the 2017 LLVM Developers' Mtg Needed!

[Tanya Lattner via lldb-dev]

Thank you for those who have volunteered. I am still in need of people for the 
following sessions:

Session 7 (10:00-10:45AM, Technical Track)
eval() in C++

Session 8 (11:10AM-12:40PM, General Session)
Implementing Swift Generics
The Further Benefits of Explicit Modularization: Modular Codegen

Session 10 (2:10-3:40PM, General Session)
Adding Index‐While‐Building and Refactoring to Clang
Advancing Clangd: Bringing persisted indexing to Clang tooling

Session 11 (2:10-3:40PM, Technical Track)
Enabling Parallel Computing in Chapel with Clang and LLVM
 Challenges when building an LLVM bitcode Obfuscator

-Tanya


> On Sep 26, 2017, at 1:49 AM, Tanya Lattner  wrote:
> 
> The 2017 LLVM Developers’ Meeting relies on volunteers to keep things running 
> smoothly. Moderators are critical to this as they keep speakers on track and 
> facilitate Q after the talk. I’m looking for community members who would be 
> attending specific talks anyway, to volunteer to moderate the session.
> 
> If you are interested in volunteering, please respond to this email with your 
> first and second choice session times. You will moderate all talks during 
> that time slot and they will occur back to back in the same room. Moderators 
> introduce the speaker, give the speaker warnings about time, and facilitate 
> Q by running microphones.
> 
> Full schedule here: https://2017llvmdevmtg.sched.com 
> 
> 
> Session 1 (10:30-12:45, Technical Track)
> Dominator Trees and incremental updates that transcend time
> GlobalISel: Past, Present, and Future
> XRay in LLVM: Function Call Tracing and Analysis
> 
> Session 2 (2:15-4:00PM, General Session)
> LIGHTNING TALKS
> LLVM Compile-Time: Challenges. Improvements. Outlook.
> 
> Session 3 (2:15-4:00PM, Technical Track)
> Tutorial: Welcome to the back-end: The LLVM machine representation.
> Scale, Robust and Regression-Free Loop Optimizations for Scientific Fortran 
> and Modern C++
> 
> Session 4 (4:20-5:50PM, General Session)
> The Type Sanitizer: Free Yourself from -fno-strict-aliasing
> Structure-aware fuzzing for Clang and LLVM with libprotobuf-mutator
> 
> Session 5 (4:20-6:05PM, General Session)
> Vectorizing Loops with VPlan – Current State and Next Steps
> Tutorial: Writing Great Machine Schedulers
> 
> Session 6 (9:00-10:45AM, General Session)
> Falcon: An optimizing Java JIT
> Apple LLVM GPU Compiler: Embedded Dragons
> 
> Session 7 (10:00-10:45AM, Technical Track)
> eval() in C++
> 
> Session 8 (11:10AM-12:40PM, General Session)
> Implementing Swift Generics
> The Further Benefits of Explicit Modularization: Modular Codegen
> 
> Session 9 (11:10AM-12:40PM, Technical Track)
> Bringing link-time optimization to the embedded world: (Thin)LTO with Linker 
> Scripts
> lld: A Fast, Simple, and Portable Linker
> 
> Session 10 (2:10-3:40PM, General Session)
> Adding Index‐While‐Building and Refactoring to Clang
> Advancing Clangd: Bringing persisted indexing to Clang tooling
> 
> Session 11 (2:10-3:40PM, Technical Track)
> Enabling Parallel Computing in Chapel with Clang and LLVM
>  Challenges when building an LLVM bitcode Obfuscator
> 
> Session 12 (4:40-6:25PM, General Session)
> Building Your Product Around LLVM Releases
> Tutorial: Head First into GlobalISel
> 
> 
> Thanks,
> Tanya
> 

___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

[lldb-dev] Moderators for the 2017 LLVM Developers' Mtg Needed!

[Tanya Lattner via lldb-dev]

The 2017 LLVM Developers’ Meeting relies on volunteers to keep things running 
smoothly. Moderators are critical to this as they keep speakers on track and 
facilitate Q after the talk. I’m looking for community members who would be 
attending specific talks anyway, to volunteer to moderate the session.

If you are interested in volunteering, please respond to this email with your 
first and second choice session times. You will moderate all talks during that 
time slot and they will occur back to back in the same room. Moderators 
introduce the speaker, give the speaker warnings about time, and facilitate Q 
by running microphones.

Full schedule here: https://2017llvmdevmtg.sched.com

Session 1 (10:30-12:45, Technical Track)
Dominator Trees and incremental updates that transcend time
GlobalISel: Past, Present, and Future
XRay in LLVM: Function Call Tracing and Analysis

Session 2 (2:15-4:00PM, General Session)
LIGHTNING TALKS
LLVM Compile-Time: Challenges. Improvements. Outlook.

Session 3 (2:15-4:00PM, Technical Track)
Tutorial: Welcome to the back-end: The LLVM machine representation.
Scale, Robust and Regression-Free Loop Optimizations for Scientific Fortran and 
Modern C++

Session 4 (4:20-5:50PM, General Session)
The Type Sanitizer: Free Yourself from -fno-strict-aliasing
Structure-aware fuzzing for Clang and LLVM with libprotobuf-mutator

Session 5 (4:20-6:05PM, General Session)
Vectorizing Loops with VPlan – Current State and Next Steps
Tutorial: Writing Great Machine Schedulers

Session 6 (9:00-10:45AM, General Session)
Falcon: An optimizing Java JIT
Apple LLVM GPU Compiler: Embedded Dragons

Session 7 (10:00-10:45AM, Technical Track)
eval() in C++

Session 8 (11:10AM-12:40PM, General Session)
Implementing Swift Generics
The Further Benefits of Explicit Modularization: Modular Codegen

Session 9 (11:10AM-12:40PM, Technical Track)
Bringing link-time optimization to the embedded world: (Thin)LTO with Linker 
Scripts
lld: A Fast, Simple, and Portable Linker

Session 10 (2:10-3:40PM, General Session)
Adding Index‐While‐Building and Refactoring to Clang
Advancing Clangd: Bringing persisted indexing to Clang tooling

Session 11 (2:10-3:40PM, Technical Track)
Enabling Parallel Computing in Chapel with Clang and LLVM
 Challenges when building an LLVM bitcode Obfuscator

Session 12 (4:40-6:25PM, General Session)
Building Your Product Around LLVM Releases
Tutorial: Head First into GlobalISel


Thanks,
Tanya

___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

[lldb-dev] 2017 LLVM Dev Meeting - Schedule Online, Registration Closing & Room Block Expiring

[Tanya Lattner via lldb-dev]

All,

The 2017 LLVM Developers’ Meeting registration will be closing soon! Please 
make sure you are registered and tell your friends that they don’t want to miss 
the opportunity to attend the largest gathering of LLVM Developers.
https://llvm.org/devmtg/2017-10/ 
https://www.eventbrite.com/e/2017-llvm-developers-meeting-bay-area-tickets-35155516095

In addition, the room block for the event ends tomorrow September 26th! Details 
here:
https://llvm.org/devmtg/2017-10/#logistics

We have an AMAZING program this year. The schedule is now online:
https://2017llvmdevmtg.sched.com

Meeting other LLVM developers face to face is invaluable! We hope to see you 
there.

Thanks,
Tanya

___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

[lldb-dev] Session Volunteers for Hackers Lab Needed!

[Tanya Lattner via lldb-dev]

All,

We need volunteers for the Hacker’s Lab at the upcoming 2017 LLVM Developers’ 
Meeting! The Hacker’s Lab is for small groups to form to discuss topics or work 
on problems. Please let me know ASAP if you will able to volunteer so I can add 
your topic to the online listing and make appropriate signs.

The Hackers Lab is split into 1.5 hour sessions. During each session, the 
Hackers Lab will focus on specific topics. Each table (~15) in the room will 
have a sign on it to represent a sub-project or area of LLVM. This will help 
newcomers and even active developers congregate together on specific topics. 
Many of the tables will have an easel for informal discussions. 

In addition to labeling tables, we are asking for volunteers to represent a 
sub-project or topic related to the meeting. These volunteers should be 
knowledgeable about the sub-project/topic and able to answer some basic 
questions or point people to the right developer to talk to. If volunteers want 
to go a step further, they could prepare a list of bugs that groups could work 
on during the Hackers Lab. This is very open ended in what the leader of the 
table can do, but the main goal is to provide a space for developers’ to meet 
and find each other who are interested in a specific topic or sub-project.

I’ve gone through many of the Code Owners files to try to find topics, and here 
is a list I have started.. but really it depends on who volunteers :)

LLVM
Backends, Code Generation, Register Allocation, Machine Code Layer, ISel
LLDB, Debug Info, DWARF
LTO
Polly
MCJIT
Mid-level optimizations, pass manager, loop optimizations, etc
TableGen
Sanitizers
Windows support
Exception handling
lld

Clang, Libs, & Frontend tools
Clang - parsing, llvm ir generation, etc
Static Analyzer
OpenCL
Clang Tools - clang tidy, clang rename
parallel-libs
Open MP
libC++
llgo

I know this may be a bit confusing.. but it really doesn’t require much work if 
you don’t want it to. Ideally, I would love some Code Owners to fill the roles, 
but I realize not all will be attending.

Please let me know ASAP if you are interested! In the rare event I have too 
many volunteers, we may combine topics at tables.

Thanks,
Tanya___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

[lldb-dev] IMPORTANT: LLVM.org server move complete (SVN impact please read)

[Tanya Lattner via lldb-dev]

LLVMers,

We have completed the move to the new server for LLVM.org. One casualty of this 
move was that svn.llvm.org was NOT enabled at this time. 

There is a new certificate for LLVM.org and HTTPS is enabled for the website. 
We know of a few issues with some of the webpages but will be working them out 
over the next few days.

Please do not hesitate to contact llvm-ad...@lists.llvm.org with any issues you 
find. With a large change like this, we expect to have a few bumps and 
appreciate your patience.

A huge thank you to Anton and Mike for all their hard work!

Thanks,
Tanya___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

[lldb-dev] IMPORTANT: LLVM.org server move on June 24th! (SVN impact)

[Tanya Lattner via lldb-dev]

LLVMers,
 
The LLVM.org  server which hosts SVN, GIT mirror, 
documentation, and the main LLVM.org  website is moving to a 
new server on June 24th.  As a result of the move commit access will be locked 
out beginning 09:00PDT on the 24th.  We hope to have the move complete and 
commit access restored to everyone in a timely manner, however, a move of this 
magnitude will take several hours to complete.
 
In addition, this is the first step in moving SVN to a new URL: svn.llvm.org 
 
You can continue to access SVN via the old URL llvm.org/svn but we would like 
people to start moving over to the new URL. This will allow us more flexibility 
in moving SVN and SSL certificates going forward.
 
After the server move, you will may need to do the following:
Switch to the new URL via this command (you may need to adjust for your 
specific repo):
svn switch —relocate https://llvm.org/svn/llvm-project/ 
https://svn.llvm.org/llvm-project/
Accept the new certificate when using svn
 
A huge thank you to Mike Edwards for leading and helping this move. Mike has 
generously donated his time to help with system administration going forward 
and is still looking for volunteers to help with our ongoing operations needs.  
If you are interested in helping out please contact Mike at m...@sqlby.me 
.
 
 
Thanks,
Tanya___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

[lldb-dev] LLVM.org (SVN, web) DOWNTIME May 20th (7AM CDT -> 1PM CDT)

[Tanya Lattner via lldb-dev]

FYI, The llvm.org server will be down May 20th from 7AM CDT to 1PM CDT. SVN and 
llvm.org webpages will be unavailable. Please note that some websites and 
services (Mailing lists, Clang and other sub-projects, APT, releases, Bugzilla) 
are hosted by other servers and are not impacted. 

I apologize for the short notice as we had hoped to have the SVN move completed 
before this but even the best plans have speed bumps.

-Tanya
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

[lldb-dev] LLVM Bugzilla MOVED to bugs.llvm.org

[Tanya Lattner via lldb-dev]

All,

http://llvm.org/bugs  has moved to bugs.llvm.org 
. You will be redirected if you attempted to access via 
the old URL, but please update your bookmarks as well.

HTTPS access to bugzilla is now updated to a new SSL certificate. 

If you experience any problems, please let me know or email 
llvm-ad...@lists.llvm.org

Thank you,
Tanya___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

[lldb-dev] [SERVER UPDATE] Moving openmp, clang, clang-analyzer, libcxxabi, libcxx ... websites to new server

[Tanya Lattner via lldb-dev]

All,

The following websites will be moving to a new web server in the next few days:
clang.llvm.org 
clang-analyzer.llvm.org 
compiler-rt.llvm.org 
dragonegg.llvm.org 
klee.llvm.org 
libclc.llvm.org 
libcxx.llvm.org 
libcxxabi.llvm.org 
lldb.llvm.org 
lld.llvm.org 
openmp.llvm.org 
polly.llvm.org 
vmkit.llvm.org 

Please note that llvm.org  proper is NOT moving at this time. 
Therefore SVN, Bugzilla, ViewVC, and all the llvm.org/*  
webpages will remain on that server. I will be updating on this in a separate 
email.

How does this impact you?
You may see a very short downtime (< 1 hour) when the switch is made. This is 
most likely due to the DNS switch. I will notify the list when all websites 
listed have been moved. Since this does not involve SVN, the downtime is 
hopefully tolerable.

Are you fixing the SSL problem?
Yes. The new server will have SSL support for all websites and have an updated 
certificate. 

What about the website auto-update?
Currently, the web sites all automatically update via post-commit hook for SVN. 
We have temporarily set up an alternative method and websites will update every 
30 minutes.

What about website documentation generation?
There are 3 scripts that generate documentation on the web server. For doxygen, 
it will continue to update daily. For sphinx documentation, it will update 
every hour instead of immediately after a commit. 

In order to increase visibility into the server, these scripts have been 
enhanced to now email a list to indicate success or failure. You can either 
subscribe to the list or check the archives if you have concerns about 
documentation not being updated:
http://lists.llvm.org/cgi-bin/mailman/listinfo/www-scripts 


Why are you doing this?
We want to increase the reliability, stability, and speed of the LLVN services. 
The current machine is outdated and is not set up for our current needs. 

If you have any questions, please do not hesitate to ask.

Thank you,
Tanya___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

[lldb-dev] [IMPORTANT] Disabling bugzilla email notification temporarily

[Tanya Lattner via lldb-dev]

Bugzilla email notification will be turned off until spam cleanup can be 
handled.

Thanks,
Tanya
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] [llvm-dev] Closing spam bugs has a consequence, be aware

[Tanya Lattner via lldb-dev]

Paul,

Please don’t mass close the bugs. I’m going to turn off bugzilla mail and then 
do the cleanup.

-Tanya

> On Aug 29, 2016, at 11:53 AM, Robinson, Paul via llvm-dev 
>  wrote:
> 
> I just went in and bulk-closed a dozen or so of today's spam bugs.
> This made me realize that doing so sends an email to the submitter's
> address, which allows the submitter to collect valid addresses of
> the people who are trying to clean up the mess.
> 
> Anyone who wants to help with the cleanup, that's great, but just
> be aware of this consequence--you are likely to be (more) targeted
> by spammers in the future.
> --paulr
> 
> ___
> LLVM Developers mailing list
> llvm-...@lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev

___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] [llvm-dev] GitHub anyone?

[Tanya Lattner via lldb-dev]

> On Jun 2, 2016, at 12:18 PM, Mehdi Amini  wrote:
> 
> 
>> On Jun 2, 2016, at 9:21 AM, Tanya Lattner via llvm-dev 
>>  wrote:
>> 
>> I personally find this email thread very hard to follow and read (this isn’t 
>> anyones fault.. its just a lot of replies). I am sure others do as well. I 
>> think it would be good to have a form/survey of some sort that can get 
>> feedback from users such as: who they are, how they use 
>> LLVM/contributions/etc,  if they are pro-github move, how it impacts them, 
>> etc. People could then submit their feedback in an organized way and we 
>> could get a better idea of how the community feels on the topic. 
>> 
>> I am happy to try to set something like this up.
> 
> I don't think it is a good idea to set this up like that without having a 
> well defined plan first.
> My idea is rather that we should first try to see what is doable in term of 
> server-side hook and integration so that the "poll" is not about naked "svn 
> vs git", but about "svn vs 
> git-with-this-server-side-setup-that-preserve-our-workflow".
> 

Sure, I am fine with flushing out those details out. Just an idea to get a 
better idea of the consensus when the time comes.

-Tanya 


> -- 
> Mehdi
> 
> 
> 
>> 
>> -Tanya
>> 
>>> On Jun 2, 2016, at 8:48 AM, Renato Golin via llvm-dev 
>>>  wrote:
>>> 
>>> A little summary...
>>> 
>>> After a lot of discussion, I think we converged to a few issues that
>>> we need to solved before we finally decide to move.
>>> 
>>> Firstly, the responses were overwhelmingly positive (I counted 20 of
>>> the ~25 people strongly supporting and another 2~3 weakly supporting).
>>> This is a good indication that the move could be very beneficial to
>>> the community as a whole, including downstream infrastructure, not
>>> just the reduction in upstream infrastructure admin costs.
>>> 
>>> But that doesn't mean we have cleared up all the issues...
>>> 
>>> 
>>>  The benefits I gathered from the thread:
>>> 
>>> * Infrastructure admin (not just server costs) is too expensive.
>>> We're not sysadmins and maintaining all the tools is a full time job.
>>> Volunteering works for odd problems, not for production services.
>>> Furthermore, most of the infrastructure we need is covered by
>>> GitHub/Lab/BB for free, on a scale that we would not have, even with a
>>> full time sysadmin. Gratis.
>>> 
>>> * Having one official repository instead of two is beneficial to most
>>> developers. A lot of people (most people replying on this thread), use
>>> Git in addition to SVN. Git also seems to be used more on validation
>>> infrastructure than SVN (no example was put forward on this thread, at
>>> least), due to the simplicity of controlling the repository and the
>>> tools available. Reports of how teams decided to script Git to have
>>> linear behaviour instead of falling back to SVN are enlightening.
>>> 
>>> * Git developer tooling is a growing trend, while SVN tooling is
>>> dying. This is not just about GUIs, but repository management (GitHub,
>>> GitLab, BitBucket, etc versus SourceForge), bisects, branches,
>>> remotes, hooks, workdir, submodules and all the new development seem
>>> to be done on Git nowadays, not SVN. Windows may be an odd one related
>>> to GUIs, but Visual Studio has Git integration and I hear it's similar
>>> to the other MSVC VCSs. GitHub's desktop interface seems pretty cool,
>>> too.
>>> 
>>> * Web repositories make it *a lot* easier to create add-hoc pull
>>> requests by non-developers, which could boost the number of
>>> contributions and future contributors, as well as external projects
>>> using LLVM components.
>>> 
>>> * GitHub's SVN RW interface has been reported to work well for
>>> simpler projects, but we need a more thorough examination before
>>> declare it good enough for our purposes.
>>> 
>>> * All reports on the thread pointed that downstream infrastructure is
>>> already using Git, so that's one less problem to worry about if we do
>>> move.
>>> 
>>> 
>>>  The issues that were raised:
>>> 
>>> * Co-dependent patches already break buildbots, but the sequential ID
>>> helps us identify and ignore. They will continue to break, even if we
>>> use git sub-modules, so that doesn't change much, but it will be
>>> harder to spot the issue. Server side hooks may help, as well as
>>> sub-modules.
>>> 
>>> * Windows tooling may be an issue. There's a separate thread handling
>>> that part, so I won't cover it here. But I have to say it wasn't by a
>>> long shot a resonant problem. It may also have some problem with
>>> symlinks and in-tree checkouts (when interacting with llvm-projects
>>> and sub-modules).
>>> 
>>> * Sub-modules may help with a lot of the current relationship we have
>>> inside the SVN repo, but it also has some problems. Namely they:
>>> - require a modern version of git (1.7/1.9), but that's 2013 onward.
>>> - may need additional server side scripting, but we 

Re: [lldb-dev] [cfe-dev] [llvm-dev] GitHub anyone?

[Tanya Lattner via lldb-dev]

> On Jun 2, 2016, at 3:59 PM, Brian Cain  wrote:
> 
>> On Thu, Jun 2, 2016 at 11:21 AM, Tanya Lattner via cfe-dev 
>>  wrote:
>> I personally find this email thread very hard to follow and read (this isn’t 
>> anyones fault.. its just a lot of replies). I am sure others do as well. I 
>> think it would be good to have a form/survey of some sort that can get 
>> feedback from users such as: who they are, how they use 
>> LLVM/contributions/etc,  if they are pro-github move, how it impacts them, 
>> etc. People could then submit their feedback in an organized way and we 
>> could get a better idea of how the community feels on the topic.
> 
> 
> While I sympathize, I wonder if a survey is appropriate.  It gives equal 
> weight to all voices but not all voices are equally impacted by the 
> pros/cons.  I am in favor of a github/lab/etc transition but I've only lurked 
> on the list and built/tested a couple of releases for older platforms.  I 
> would think opinions of those who have lots of work with 
> commits/reviews/content should probably be weighed heavier than mine.  
> Perhaps the survey could ask for a voluntary high/medium/low activity level 
> for normalizing the votes?
> 

Yes that's what I meant about asking for information about how they use LLVM 
and contributions. It would not be an anonymous survey. I just was thinking it 
would be better to have an organized way of getting votes/opinions without all 
the emails and discussion. I think discussion is important of course but it can 
be hard to follow everything and for some to chime in.

Anyways, just an idea.

-Tanya 

> -- 
> -Brian
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] [llvm-dev] GitHub anyone?

[Tanya Lattner via lldb-dev]

I personally find this email thread very hard to follow and read (this isn’t 
anyones fault.. its just a lot of replies). I am sure others do as well. I 
think it would be good to have a form/survey of some sort that can get feedback 
from users such as: who they are, how they use LLVM/contributions/etc,  if they 
are pro-github move, how it impacts them, etc. People could then submit their 
feedback in an organized way and we could get a better idea of how the 
community feels on the topic. 

I am happy to try to set something like this up.

-Tanya

> On Jun 2, 2016, at 8:48 AM, Renato Golin via llvm-dev 
>  wrote:
> 
> A little summary...
> 
> After a lot of discussion, I think we converged to a few issues that
> we need to solved before we finally decide to move.
> 
> Firstly, the responses were overwhelmingly positive (I counted 20 of
> the ~25 people strongly supporting and another 2~3 weakly supporting).
> This is a good indication that the move could be very beneficial to
> the community as a whole, including downstream infrastructure, not
> just the reduction in upstream infrastructure admin costs.
> 
> But that doesn't mean we have cleared up all the issues...
> 
> 
>The benefits I gathered from the thread:
> 
> * Infrastructure admin (not just server costs) is too expensive.
> We're not sysadmins and maintaining all the tools is a full time job.
> Volunteering works for odd problems, not for production services.
> Furthermore, most of the infrastructure we need is covered by
> GitHub/Lab/BB for free, on a scale that we would not have, even with a
> full time sysadmin. Gratis.
> 
> * Having one official repository instead of two is beneficial to most
> developers. A lot of people (most people replying on this thread), use
> Git in addition to SVN. Git also seems to be used more on validation
> infrastructure than SVN (no example was put forward on this thread, at
> least), due to the simplicity of controlling the repository and the
> tools available. Reports of how teams decided to script Git to have
> linear behaviour instead of falling back to SVN are enlightening.
> 
> * Git developer tooling is a growing trend, while SVN tooling is
> dying. This is not just about GUIs, but repository management (GitHub,
> GitLab, BitBucket, etc versus SourceForge), bisects, branches,
> remotes, hooks, workdir, submodules and all the new development seem
> to be done on Git nowadays, not SVN. Windows may be an odd one related
> to GUIs, but Visual Studio has Git integration and I hear it's similar
> to the other MSVC VCSs. GitHub's desktop interface seems pretty cool,
> too.
> 
> * Web repositories make it *a lot* easier to create add-hoc pull
> requests by non-developers, which could boost the number of
> contributions and future contributors, as well as external projects
> using LLVM components.
> 
> * GitHub's SVN RW interface has been reported to work well for
> simpler projects, but we need a more thorough examination before
> declare it good enough for our purposes.
> 
> * All reports on the thread pointed that downstream infrastructure is
> already using Git, so that's one less problem to worry about if we do
> move.
> 
> 
>The issues that were raised:
> 
> * Co-dependent patches already break buildbots, but the sequential ID
> helps us identify and ignore. They will continue to break, even if we
> use git sub-modules, so that doesn't change much, but it will be
> harder to spot the issue. Server side hooks may help, as well as
> sub-modules.
> 
> * Windows tooling may be an issue. There's a separate thread handling
> that part, so I won't cover it here. But I have to say it wasn't by a
> long shot a resonant problem. It may also have some problem with
> symlinks and in-tree checkouts (when interacting with llvm-projects
> and sub-modules).
> 
> * Sub-modules may help with a lot of the current relationship we have
> inside the SVN repo, but it also has some problems. Namely they:
>   - require a modern version of git (1.7/1.9), but that's 2013 onward.
>   - may need additional server side scripting, but we can keep that
> in another repo to control it.
>   - won't replace SVN's monotonic IDs, but do we *really* need them?
> Sub-modules have a bad fame, I gather, but people in the thread
> reported success on using it to build validation and release
> infrastructure as well as doing bisects, checking out code, etc. We
> probably need some documentation on how to do these things, as well as
> some scripts to help people work out the dependencies (or use them).
> 
> * GitHub/Lab/BB are not perfect. They have some interface issues, but
> nothing more serious than we already have on our current
> infrastructure. We'll probably have to keep Bugzilla (as GitHub's own
> is really poor), but we can replace all our repos (SVN, Git),
> visualisation tools (ViewVC, Klaus) and Phabricator.
> 
> Of all those issues, Windows tooling is a minor problem that shouldn't
> impact decision