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

[Brian Cain via lldb-dev]

Ubuntu 20 binary uploaded.  I also disabled flang (-no-flang) because of
memory exhaustion while trying to build.  Is this increased memory
consumption expected or could it be a bug?

$ cat clang+llvm-13.0.0-rc3-x86_64-linux-gnu-ubuntu-20.04.tar.xz.sha256

488ff13c9a54f6b7b2aeb26e930da7d72e32a15542929cd642fc0b7d37e79967
 clang+llvm-13.0.0-rc3-x86_64-linux-gnu-ubuntu-20.04.tar.xz

On Mon, Sep 13, 2021 at 11:40 PM Tom Stellard via Release-testers <
release-test...@lists.llvm.org> 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.
>
> -Tom
>
> ___
> Release-testers mailing list
> release-test...@lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
>


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

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

[Andrzej Warzynski via lldb-dev]

Hi Brian,

Thank you for helping with the release!

On 20/09/2021 18:40, Brian Cain via Openmp-dev wrote:
I also disabled flang (-no-flang) because of 
memory exhaustion while trying to build.  Is this increased memory 
consumption expected or could it be a bug?


The memory usage of LLVM Flang was discussed in the past:
* https://bugs.llvm.org/show_bug.cgi?id=50059
* https://lists.llvm.org/pipermail/flang-dev/2019-November/61.html

It's not great, but sadly it is rather unlikely to improve in the near 
future.


Thanks,
-Andrzej



$ cat clang+llvm-13.0.0-rc3-x86_64-linux-gnu-ubuntu-20.04.tar.xz.sha256
488ff13c9a54f6b7b2aeb26e930da7d72e32a15542929cd642fc0b7d37e79967 
  clang+llvm-13.0.0-rc3-x86_64-linux-gnu-ubuntu-20.04.tar.xz


On Mon, Sep 13, 2021 at 11:40 PM Tom Stellard via Release-testers 
mailto:release-test...@lists.llvm.org>> 
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.

-Tom

___
Release-testers mailing list
release-test...@lists.llvm.org 
https://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers




--
-Brian

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


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

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

[Brian Cain via lldb-dev]

On Mon, Sep 20, 2021 at 1:14 PM Andrzej Warzynski 
wrote:

> Hi Brian,
>
> Thank you for helping with the release!
>
> On 20/09/2021 18:40, Brian Cain via Openmp-dev wrote:
> > I also disabled flang (-no-flang) because of
> > memory exhaustion while trying to build.  Is this increased memory
> > consumption expected or could it be a bug?
>
> The memory usage of LLVM Flang was discussed in the past:
> * https://bugs.llvm.org/show_bug.cgi?id=50059
> * https://lists.llvm.org/pipermail/flang-dev/2019-November/61.html
>
> It's not great, but sadly it is rather unlikely to improve in the near
> future.
>
>
Ok, I understand.  I am not opposed to including flang in this build, if I
can get it to work.  Is there a way to set some kind of variable to limit
the concurrency for building (only) these targets?  Like
LLVM_PARALLEL_LINK_JOBS works today.  What if test-release.sh defined
LLVM_PARALLEL_FLANG_COMPILE_JOBS to "1" (or I defined it in
-configure-flags) and there were some cmake magic that handled that input
to control how the build were invoked?  I think that would be a good
workaround.



> Thanks,
> -Andrzej
>
> >
> > $ cat clang+llvm-13.0.0-rc3-x86_64-linux-gnu-ubuntu-20.04.tar.xz.sha256
> > 488ff13c9a54f6b7b2aeb26e930da7d72e32a15542929cd642fc0b7d37e79967
> >   clang+llvm-13.0.0-rc3-x86_64-linux-gnu-ubuntu-20.04.tar.xz
> >
> > On Mon, Sep 13, 2021 at 11:40 PM Tom Stellard via Release-testers
> > mailto:release-test...@lists.llvm.org>>
>
> > 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.
> >
> > -Tom
> >
> > ___
> > Release-testers mailing list
> > release-test...@lists.llvm.org  release-test...@lists.llvm.org>
> > https://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
> > 
> >
> >
> >
> > --
> > -Brian
> >
> > ___
> > Openmp-dev mailing list
> > openmp-...@lists.llvm.org
> > https://lists.llvm.org/cgi-bin/mailman/listinfo/openmp-dev
> >
>


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

[lldb-dev] [Bug 51917] New: Can't build LLDB 13 with older linux kernel

[via lldb-dev]

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

Bug ID: 51917
   Summary: Can't build LLDB 13 with older linux kernel
   Product: lldb
   Version: unspecified
  Hardware: PC
OS: Linux
Status: NEW
  Severity: enhancement
  Priority: P
 Component: All Bugs
  Assignee: lldb-dev@lists.llvm.org
  Reporter: caleb.zulaw...@gmail.com
CC: jdevliegh...@apple.com, llvm-b...@lists.llvm.org

I am trying to build with a kernel older than 4.1, and get the following error:

llvm-project-13.0.0rc3.src/lldb/source/Plugins/Process/Linux/IntelPTManager.cpp:148:23:
error: 'struct perf_event_mmap_page' has no member named 'aux_size'
  148 |   return m_mmap_meta->aux_size;
  | 

aux_size was added in Linux 4.1.  It appears the Intel PT plugin was added in
LLVM 13, I can currently build LLVM 12 and hope to be able to upgrade to 13
when it's released.

-- 
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] [Openmp-dev] [Release-testers] 13.0.0-rc3 has been tagged

[Andrzej Warzynski via lldb-dev]

On 20/09/2021 19:53, Brian Cain wrote:


Is there a way to set some kind of variable to 
limit the concurrency for building (only) these targets?  Like 
LLVM_PARALLEL_LINK_JOBS works today.  


AFAIK, that's not possible ATM. I agree that it would be a good 
workaround and we should look into this. But it will be tricky to get 
this in on time for Release 13.


I suspect that you are already using either ld.gold or lld? Perhaps you 
could build all of LLVM with LLVM_PARALLEL_COMPILE_JOBS=1 (or some other 
small value)?



-Andrzej

What if test-release.sh defined
LLVM_PARALLEL_FLANG_COMPILE_JOBS to "1" (or I defined it in 
-configure-flags) and there were some cmake magic that handled that 
input to control how the build were invoked?  I think that would be a 
good workaround.


Thanks,
-Andrzej

 >
 > $ cat
clang+llvm-13.0.0-rc3-x86_64-linux-gnu-ubuntu-20.04.tar.xz.sha256
 > 488ff13c9a54f6b7b2aeb26e930da7d72e32a15542929cd642fc0b7d37e79967
 >   clang+llvm-13.0.0-rc3-x86_64-linux-gnu-ubuntu-20.04.tar.xz
 >
 > On Mon, Sep 13, 2021 at 11:40 PM Tom Stellard via Release-testers
 > mailto:release-test...@lists.llvm.org>
>>
 > 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.
 >
 >     -Tom
 >
 >     ___
 >     Release-testers mailing list
 > release-test...@lists.llvm.org

>
 > https://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers

 >   
  >
 >
 >
 >
 > --
 > -Brian
 >
 > ___
 > Openmp-dev mailing list
 > openmp-...@lists.llvm.org 
 > https://lists.llvm.org/cgi-bin/mailman/listinfo/openmp-dev

 >



--
-Brian

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