[lldb-dev] [Bug 46775] New: lldb needs to handle auto

[via lldb-dev]

https://bugs.llvm.org/show_bug.cgi?id=46775

Bug ID: 46775
   Summary: lldb needs to handle auto
   Product: lldb
   Version: 11.0
  Hardware: PC
OS: Linux
Status: NEW
  Severity: normal
  Priority: P
 Component: All Bugs
  Assignee: lldb-dev@lists.llvm.org
  Reporter: tras...@gmail.com
CC: jdevliegh...@apple.com, llvm-b...@lists.llvm.org

When compiling clangd with clang it generates the following debug info:

Abbrev Number: 166 (DW_TAG_unspecified_type)
DW_AT_name: (indexed string: 0xb0c6): auto

This is not handled in DWARFASTParserClang::ParseTypeModifier:

  case DW_TAG_unspecified_type:
if (attrs.name == "nullptr_t" || attrs.name == "decltype(nullptr)") {
  resolve_state = Type::ResolveState::Full;
  clang_type = m_ast.GetBasicType(eBasicTypeNullPtr);
  break;
}
// Fall through to base type below in case we can handle the type
// there...
LLVM_FALLTHROUGH;

  case DW_TAG_base_type:

And due to the fallthrough this results in the following (somewhat misleading)
error message:
error: need to add support for DW_TAG_base_type 'auto' encoded with DW_ATE =
0x0, bit_size = 0

-- 
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

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&A):
>> 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&A)
>> 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&A. 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&A 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&A early in the morning, l