Re: [lldb-dev] [llvm-dev] 13.0.0-rc3 has been tagged

[Tom Stellard via lldb-dev]

On 9/17/21 10:29 AM, Sedat Dilek wrote:

@Tom Stellard

Shall I open a bug-report to cherry-pick...?

commit 454f69bcc17e6451c926a2e7b708e900fc8fdcb8
"[PATCH] [LLD] Add required `ppc` target to the test cases. NFC")

If yes - Can you point me to the LLVM release/13.x meta bug number?



Yes,that would be great if you could open a bug.  And you don't need the meta 
bug
number, you can just put release-13.0.0 in the blocks field.

-Tom


Do you want to do it directly by yourself?

Thanks.

- Sedat -

On Wed, Sep 15, 2021 at 1:50 AM Sedat Dilek  wrote:


On Tue, Sep 14, 2021 at 6:40 AM Tom Stellard via llvm-dev
 wrote:


Hi,

I've tagged 13.0.0-rc3.  This will likely be the last rc unless there are
critical bugs that are found.  Please test the release and report results.



I use tc-build from the ClangBuiltLinux project to build a selfmade
x86-64 LLVM toolchain.

My invocation looks like this:

$ python3 ./build-llvm.py --no-update --build-type Release -p
clang;lld -t X86;BPF --clang-vendor dileks -B
/home/dileks/src/llvm-toolchain/build -I /opt/llvm-toolchain
--check-targets clang lld --build-stage1-only --install-stage1-only -D
LLVM_PARALLEL_LINK_JOBS=1 --show-build-commands

The LLD check-targets failed:

3887: TEST 'lld :: ELF/compressed-debug-input.s'
FAILED 
3918: TEST 'lld ::
ELF/compressed-debug-input-err.s' FAILED 
3947:FAILED: tools/lld/test/CMakeFiles/check-lld

$ grep error: log_tc-build.txt
3911:/home/dileks/src/llvm-toolchain/build/stage1/bin/llvm-mc: error:
: error: unable to get target for 'powerpc64-unknown-unknown', see
--version and --triple.
3930:/home/dileks/src/llvm-toolchain/build/stage1/bin/llvm-mc: error:
: error: unable to get target for 'powerpc64-unknown-unknown', see
--version and --triple.

This is due to I have no ppc target:

$ /home/dileks/src/llvm-toolchain/build/stage1/bin/llvm-mc --version
LLVM (http://llvm.org/):
  LLVM version 13.0.0
  Optimized build.
  Default target: x86_64-unknown-linux-gnu
  Host CPU: sandybridge

  Registered Targets:
bpf- BPF (host endian)
bpfeb  - BPF (big endian)
bpfel  - BPF (little endian)
x86- 32-bit X86: Pentium-Pro and above
x86-64 - 64-bit X86: EM64T and AMD64

I needed to apply [1] to fix the issue with LLD check-targets:

 From 454f69bcc17e6451c926a2e7b708e900fc8fdcb8 Mon Sep 17 00:00:00 2001
From: Simon Atanasyan 
Date: Sat, 7 Aug 2021 13:29:59 +0300
Subject: [PATCH] [LLD] Add required `ppc` target to the test cases. NFC

Please cherry-pick this to release/13.x Git tree.

Thanks.

Regards,
- Sedat -

[1] 
https://github.com/llvm/llvm-project/commit/454f69bcc17e6451c926a2e7b708e900fc8fdcb8.patch




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

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

[Dimitry Andric via lldb-dev]

On 14 Sep 2021, at 06:40, Tom Stellard via Release-testers 
 wrote:
> 
> I've tagged 13.0.0-rc3.  This will likely be the last rc unless there are
> critical bugs that are found.  Please test the release and report results.

For 13.0.0 rc3, I have built and tested on both FreeBSD 12 and 13. No
additional patches were needed, as they were merged.

For the 32-builds I used -no-flang, as flang is currently not 32-bit
clean, and I do not expect it will ever be. (Also, these builds consume
a huge amount of RAM, making native compilation likely impossible.)


Main results on amd64-freebsd12:

  Skipped: 3 (rc2: 3)
  Unsupported:  6353 (rc2:  6353)
  Passed With Retry  : 91823 (rc2: 0)
  Passed : 1 (rc2: 91855)
  Expectedly Failed  :   320 (rc2:   320)
  Timed Out  : 2 (rc2: 2)
  Failed :   300 (rc2:   295)
  Unexpectedly Passed: 2 (rc2: 2)

Test suite results on amd64-freebsd12:

  Passed: 2419 (rc2: 2419)
  Failed:3 (rc2:3)


Main results on amd64-freebsd13:

  Skipped: 3 (rc2: 3)
  Unsupported:  6352 (rc2:  6352)
  Passed : 91789 (rc2: 91792)
  Expectedly Failed  :   320 (rc2:   320)
  Failed :   338 (rc2:   324)
  Unexpectedly Passed: 2 (rc2: 2)

Test suite results on amd64-freebsd13:

  Passed: 2419 (rc2: 2419)
  Failed:3 (rc2:3)


Main results on i386-freebsd12:

  Skipped: 3 (rc2: 3)
  Unsupported:  4738 (rc2:  4736)
  Passed : 87552 (rc2: 87542)
  Expectedly Failed  :   295 (rc2:   295)
  Failed :   198 (rc2:   200)
  Unexpectedly Passed: 1 (rc2: 1)


Main results on i386-freebsd13:

  Skipped: 3 (rc2: 3)
  Unsupported:  4738 (rc2:  4736)
  Passed : 87550 (rc2: 87540)
  Expectedly Failed  :   295 (rc2:   295)
  Failed :   200 (rc2:   202)
  Unexpectedly Passed: 1 (rc2: 1)


Uploaded:
SHA256 (clang+llvm-13.0.0-rc3-amd64-unknown-freebsd12.tar.xz) = 
9f20ba1bbec09588c3fb630d29890f29885102408deb5e563b7e3f94a47c7ce1
SHA256 (clang+llvm-13.0.0-rc3-amd64-unknown-freebsd13.tar.xz) = 
946ad0e3b720fe0c2faaf19c62cee6692d2cc0f022d7ba8a0ffb60f2883a638b
SHA256 (clang+llvm-13.0.0-rc3-i386-unknown-freebsd12.tar.xz) = 
3f74f48c0a09d9f0c86efd8a3c1a7ee16d9cb4d0991c8abeb8163600f107df41
SHA256 (clang+llvm-13.0.0-rc3-i386-unknown-freebsd13.tar.xz) = 
5afd93f47f0d93159d0e67e2298a0a9b499e41090dd92372276fd93f01d088d9

-Dimitry



signature.asc
Description: Message signed with OpenPGP
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

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&A 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.
> T