Re: [lldb-dev] RFC: Moving toward Discord and Discourse for LLVM's discussions

2019-11-18 Thread Chandler Carruth via lldb-dev
Hello folks,

I sent the message quoted below to llvm-dev@ just now, but it applies to
the whole community so sending an FYI here. Probably best to follow up w/
discussion on llvm-dev.

The archive link for reference is here:
http://lists.llvm.org/pipermail/llvm-dev/2019-November/136880.html

On Sun, Nov 17, 2019 at 11:48 PM Chandler Carruth 
wrote:

> Hello everyone,
>
>
> *Short version:*I've set up an LLVM Discord server for real time chat
> (similar to IRC) and an LLVM Discourse server for forums (similar to email
> lists):
> https://discord.gg/xS7Z362
> https://llvm.discourse.group/
>
> Please join and use these new services. They are only partially set up and
> still very new, so don't hesitate to improve them and/or reach out to this
> thread with any issues you see or things you want to fix. Also, both
> services have dedicated feedback channels.
>
> Do feel free to use Discourse for technical discussions, although try not
> to create duplicate discussions (any more than you would between the lists
> and Bugzilla) and make sure the people you're having the discussion with
> are fine using Discourse instead of the email list. In case Discourse
> doesn't work out, we'll collect and archive everything so it isn't lost.
>
>
> *Longer version & more details:*During this year's Women in Compilers and
> Tools meeting, folks expressed very clearly that our communication systems
> cause a non-trivial amount of friction for new people trying to find out
> about, learn, or contribute to LLVM. Both IRC for chatting and mailing
> lists for longer-form discussions are unfamiliar, difficult, and often
> intimidating for newcomers. While I have long been a fan and resistant to
> change in these areas, the feedback from folks at WiCT was compelling and
> important for us as a community to address. Even if it means I have to let
> go of my precious IRC. ;]
>
> We talked to a bunch of people and looked at the options out there and the
> most promising ones were Discord for chatting and Discourse for longer-form
> discussions. Meike and I have set up both an initial Discord and Discourse
> server. You can find them here:
> https://discord.gg/xS7Z362
> https://llvm.discourse.group/
>
> There is still a lot of work to be done. Notably, it'd be great for folks
> to clean up and improve the summaries for each of the groups in Discourse,
> and I'll be asking various people to help moderate on both Discourse and
> Discord. If you'd like to help out with a specific set of improvements to
> these, don't hesitate to reach out to me or Meike and we can get you set
> up. Some specific things we're already working on:
>
>- Getting Discord verified with a nice URL.
>- Archives of mailing lists on Discourse so you can search in one
>place, etc.
>   - See the plan here:
>   
> https://llvm.discourse.group/t/mirroring-and-archiving-llvm-mailing-lists-on-discourse/61
>- Moving Discourse to forums.llvm.org.
>- Documenting the best way to move to Discourse while preserving a
>similarly email-focused workflow.
>
>
> We're just adding these for now, but I'd like people to seriously try
> using them. While IRC has served us fairly well, I think it is one of the
> bigger barriers to entry. Our email lists are more effective, but also have
> had serious infrastructure challenges over the years: a constant flow of
> spam, bouncing for several major email providers, etc. Discourse has very
> powerful email-based workflows available and I think we should seriously
> consider moving to Discourse long-term instead of the email lists.
>
> I also want to say thanks to all the folks at the WiCT workshop for giving
> me and others feedback. I was pretty set in my ways around these kind of
> things, but hearing the kinds of challenges this has posed to people less
> established in the community was a real eye opener. It takes a lot to speak
> up like this, and I really appreciate it. I hope this also helps start to
> address these long-standing issues. Also a huge thanks to Tanya for
> organizing the WICT workshop and Meike for helping drive this message home
> to me and doing a bunch of the work getting these things set up. I wouldn't
> have been able to do it without her help, especially around Discord bots.
>
> -Chandler
>
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev


Re: [lldb-dev] [CFP] LLVM devroom at FOSDEM 2020

2019-11-18 Thread Kristof Beyls via lldb-dev
This is just a gentle reminder that the deadline for submission is coming
Sunday, 24th of November.

Thanks,

Kristof

Op di 8 okt. 2019 om 17:26 schreef Kristof Beyls :

> CALL FOR PAPERS / PARTICIPATION
>
> At FOSDEM 2020, LLVM will again participate with a dedicated devroom, on
> Saturday February 1st, in Brussels.
>
> As possibly the largest European Open Source Conference, FOSDEM attracts
> more than 600 lectures and over 8000 hackers - many core contributors of
> the world’s leading open source projects.
>
> Complementing the LLVM developer meetings, the devroom at FOSDEM provides
> a great opportunity for LLVM developers and the wider open source community
> to get together, connect and discuss.
>
> We invite academic, industrial and hobbyist speakers to present their work
> on developing or using LLVM, Clang, LLDB, Compiler-rt, MLIR, flang, or any
> of the other technologies in the LLVM project.
>
> We are looking for:
>
>-
>
>Keynote speakers.
>-
>
>Technical presentations (default length of 40 minutes including
>questions) related to the development of LLVM technologies or use of those
>technologies in other projects.
>-
>
>Tutorials.
>-
>
>Lightning talks (default length of 5 minutes).
>-
>
>Demos.
>
> The deadline for receiving proposals is Sunday November 24th, 2019.
>
> Speakers will be notified of acceptance or rejection by December 13th.
> Please find some advice on what constitutes a good proposal at the end of
> this CFP.
>
> To submit a proposal, please create an account on the FOSDEM interface (
> https://penta.fosdem.org/user/new_account). If you already have an
> account from previous years, please reuse that.
>
> Submit your proposal following
> https://penta.fosdem.org/submission/FOSDEM20, “Create Event”.
>
> Please make sure you select "LLVM devroom" as the "Track”.
>
> Presentations will be recorded and streamed. Sending your proposal implies
> giving permission to be recorded.
>
> Registration
>
> FOSDEM does not require any registration and is free of charge.
>
> Organization
>
> The mailing list llvm-devroom at lists.fosdem.org can be used to discuss
> issues of general interest related to the conference organization. Please,
> do not reply to this email, as it is cross posted to many lists.
>
> Financial support
>
> There may be a possibility of limited funding to help presenters who could
> not otherwise attend the conference.
>
> If you need funding to be able to present at the meeting, or can help
> provide sponsorship, please tell us on llvm-devroom at lists.fosdem.org.
>
> Guidance on writing a proposal for the LLVM Dev Room
>
> This is a guide to help you submit a good proposal and increase your
> chances of your proposal being accepted.
>
> If you have never presented at an LLVM 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
>target audience is, and what are the takeaways for attendees. The program
>committee does not have time to read 10 page papers for each submission.
>-
>
>Talks about the use of an LLVM technology 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.
>-
>
>Typically a few paragraphs are sufficient.
>
>
> Best regards,
>
> LLVM @ FOSDEM organisers
>
>
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev


[lldb-dev] [Bug 44037] New: Adding range which has a base that is less than the function's low PC

2019-11-18 Thread via lldb-dev
https://bugs.llvm.org/show_bug.cgi?id=44037

Bug ID: 44037
   Summary: Adding range which has a base that is less than the
function's low PC
   Product: lldb
   Version: unspecified
  Hardware: PC
OS: Linux
Status: NEW
  Severity: enhancement
  Priority: P
 Component: All Bugs
  Assignee: lldb-dev@lists.llvm.org
  Reporter: diana.pi...@linaro.org
CC: jdevliegh...@apple.com, llvm-b...@lists.llvm.org

TestBreakpointLocations.py
TestRedefinitionsInInlines.py
TestMembersAndLocalsWithSameName.py
TestInlinedFrame.py

are failing on AArch64 Linux with errors similar to:
error: a.out 0x002d: adding range [0x14-0x24) which has a base that is less
than the function's low PC 0x40060c. Please file a bug and attach the file at
the start of this error message.

This seems to be happening only for the dwo info (gmodules is unsupported and
dwarf is passing).

Maybe related to https://bugs.swift.org/browse/SR-8690 ?

-- 
You are receiving this mail because:
You are the assignee for the bug.___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev