Date: Sat, 3 Jul 2021 01:45:26 -0700 From: Mark Millard via freebsd-ports <freebsd-ports@freebsd.org> To: bob prohaska <fbsd@www.zefox.net> Cc: FreeBSD ports <freebsd-ports@freebsd.org>, freebsd-arm <freebsd-arm@freebsd.org>, FreeBSD Toolchain <freebsd-toolchain@freebsd.org> Subject: Re: llvm10 build failure on Rpi3 Message-ID: <F727FF9A-CDFB-4C9C-8333-0FEA6C54976A@yahoo.com> In-Reply-To: <60EEFD09-97DE-4B4F-BAFD-61B96EF60E27@yahoo.com> References: <6F0CF2F3-A298-4CEA-AA07-B79810F3E8CF@yahoo.com> <20210623222838.GA85566@www.zefox.net> <8E78EE69-44A2-429E-AB65-941537DE25A0@yahoo.com> <20210624043000.GA87740@www.zefox.net> <22B941CA-3AFF-42FD-98D1-D40EC2F6EC43@yahoo.com> <20210624160109.GB87740@www.zefox.net> <3B41633E-AAFC-422A-8D73-3B1B001023F0@yahoo.com> <20210625001651.GA98214@www.zefox.net> <D0845F74-A9A9-4588-910B-B55F9216C9C9@yahoo.com> <5A26965D-2DFD-4A46-A171-A382A61E3CFB@yahoo.com> <20210626035234.GA18893@www.zefox.net> <C64D1A3F-A42E-42E3-8491-4DE9F6A96CFB@yahoo.com> <43513842-6FC0-4A89-8F0C-9EB2B328A5ED@yahoo.com> <9CFE71E2-23C3-4072-A8AD-74EDB339A146@yahoo.com> <A4669E1F-6DA9-492C-B06C-12AABE60FCEB@yahoo.com> <F2A8E1C3-EAAD-448A-9A97-979CC9ED9BE7@yahoo.com> <60EEFD09-97DE-4B4F-BAFD-61B96EF60E27@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2021-Jul-2, at 21:47, Mark Millard <marklmi at yahoo.com> wrote: > On 2021-Jul-2, at 19:23, Mark Millard <marklmi at yahoo.com> wrote: >>=20 >> I just noticed that in several prior messasges I quoted the = llvm-tblgen >> command that generates the *.inc files with the odd contents instead >> of the later compile that tried to use the output files in question. >>=20 >> This leaves open the possibility that I had incorrectly checked on if >> the build had failed, the build possibly not having reached the part >> that used the files as of when I declared it was past that point. >>=20 >> So I may need to rerun some tests. >=20 > I have restarted a RPi4B total_mem=3D1024 test build of devel/llvm10 > via poudriere (-devel). >=20 > It has: >=20 > [00:01:12] Deleting llvm10-10.0.1_5.txz: changed options > [00:01:12] Pkg: BE_AMDGPU BE_NATIVE CLANG DOCS EXTRAS LIT LLD LLDB = LLD_LINK OPENMP=20 > [00:01:12] New: BE_AMDGPU BE_STANDARD CLANG DOCS EXTRAS LIT LLD LLDB = LLD_LINK OPENMP PYCLANG=20 >=20 > as your builds vary which target it fails from from one build > attempt to the next and this better matches what your logs > report. I need to wait until after all the *GenGlobalISel.inc > files for all the targets have been put to use before > concluding that it did not fail. Your logs have gone up to > at least 17:34:09 before reaching a failure of bad content > in one of those files (when only devel/llvm10 was being built). > In other words: a lot more targets used their *GenGlobalISel.inc > file(s) before one failed. >=20 > The context for this test is based on: >=20 > # uname -apKU > FreeBSD Rock64_RPi_4_3_2v1p2 14.0-CURRENT FreeBSD 14.0-CURRENT #1 = main-n247651-a00d703f2f43-dirty: Wed Jun 30 02:02:01 PDT 2021 = root@CA72_16Gp_ZFS:/usr/obj/BUILDs/main-CA53-nodbg-clang/usr/main-src/arm6= 4.aarch64/sys/GENERIC-NODBG-CA53 arm64 aarch64 1400024 1400024 >=20 > (So it predates today's workaround for allowing lang/rust to build > via main.) >=20 > Usual rules for me for for USB3 SSD, swap/paging space > size, etc. Well, at this point grep usage shows that the files shown by: # find = /usr/local/poudriere/data/.m/main-CA53-default/01/wrkdirs/usr/ports/devel/= llvm10/work/ -name '*GlobalISel.inc' -print = /usr/local/poudriere/data/.m/main-CA53-default/01/wrkdirs/usr/ports/devel/= llvm10/work/.build/lib/Target/AArch64/AArch64GenGlobalISel.inc = /usr/local/poudriere/data/.m/main-CA53-default/01/wrkdirs/usr/ports/devel/= llvm10/work/.build/lib/Target/AMDGPU/AMDGPUGenGlobalISel.inc = /usr/local/poudriere/data/.m/main-CA53-default/01/wrkdirs/usr/ports/devel/= llvm10/work/.build/lib/Target/ARM/ARMGenGlobalISel.inc = /usr/local/poudriere/data/.m/main-CA53-default/01/wrkdirs/usr/ports/devel/= llvm10/work/.build/lib/Target/Mips/MipsGenGlobalISel.inc = /usr/local/poudriere/data/.m/main-CA53-default/01/wrkdirs/usr/ports/devel/= llvm10/work/.build/lib/Target/RISCV/RISCVGenGlobalISel.inc = /usr/local/poudriere/data/.m/main-CA53-default/01/wrkdirs/usr/ports/devel/= llvm10/work/.build/lib/Target/X86/X86GenGlobalISel.inc do not have any examples of: @2779096485 @0 */, so I doubt that the build will fail. But I've left it running. >> Side note: >>=20 >> It llooks like http://www.zefox.org/~bob/swaplogs/poudrierellvm10.log >> shows that you tried with: >>=20 >> Device 1K-blocks Used Avail Capacity >> /dev/da0s2b 1048576 25784 1022792 2% >> /dev/mmcsd0s2b 1048576 25124 1023452 2% >> Total 2097152 50908 2046244 2% >>=20 >> A gather that the problem still occurred? >=20 > "I" gather, not "A" gather. >=20 > (I can not tell which build attempt the log is for but > I expect that you would have reported a successful build > if one had occurred.) FYI: at the moment . . . # swapinfo Device 1K-blocks Used Avail Capacity /dev/gpt/Rock64swp2 3145728 1116384 2029344 35% My odd variant of top reports for swap/paging space use: 1271Mi MaxObsUsed (maximum observed used) and: 2180Mi MaxObs(Act+Wir+Lndry+SwapUsed) As for RAM (each MaxObj<?> can be from a different time): 961312Ki MaxObs(Act+Wir+Lndry) 712760Ki MaxObsActive 261724Ki MaxObsWired =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?F727FF9A-CDFB-4C9C-8333-0FEA6C54976A>