Re: Ability to further support 32bit architectures

2024-01-12 Thread Hank Barta
On Fri, Jan 12, 2024 at 5:07 PM Alan Corey wrote: > > So, can you set an RPI4 to 32 bit for even more speed? > My Pi4 config.txt (Debian Bookworm) says > > # Switch the CPU from ARMv7 into ARMv8 (aarch64) mode > arm_64bit=1 > You would have to try it to see if it is faster for your workload. I su

Re: Ability to further support 32bit architectures

2024-01-12 Thread Alan Corey
So, can you set an RPI4 to 32 bit for even more speed? My Pi4 config.txt (Debian Bookworm) says # Switch the CPU from ARMv7 into ARMv8 (aarch64) mode arm_64bit=1 I haven't tried it because I don't know how the software will handle the timing. On Fri, Jan 12, 2024 at 1:37 PM gene heskett wrote:

Re: Ability to further support 32bit architectures

2024-01-12 Thread Bastian Blank
On Thu, Jan 11, 2024 at 09:48:34AM +, Dimitri John Ledkov wrote: > Disabling debug symbols, enabling debug symbol zstd compression, using > split debug symbols (disabled BTF usage) should help here. Disabling debug symbols does not help. Bastian > Sent from Ubuntu Pro > https://ubuntu.com/pr

Re: Ability to further support 32bit architectures

2024-01-12 Thread gene heskett
On 1/12/24 13:07, Alan Corey wrote: Are you forgetting that 64 bit is slower?  In the arm world where it's easily switchable 64 bit is pokey when you don't need it. Thank Alan, to put numbers behind that, linuxcnc has a thing called latency-test on an rpi4b the armhf kernel I built from 4.19 s

Re: Ability to further support 32bit architectures

2024-01-12 Thread Alan Corey
Are you forgetting that 64 bit is slower? In the arm world where it's easily switchable 64 bit is pokey when you don't need it. On Fri, Jan 12, 2024, 12:54 PM wrote: > > > Sent from my mobile device. > > -- > *From:* YunQiang Su > *Sent:* Friday, January 12, 2024 10

Re: Ability to further support 32bit architectures

2024-01-12 Thread rhys
Sent from my mobile device. From: YunQiang Su Sent: Friday, January 12, 2024 10:11 To: r...@neoquasar.org Cc: noloa...@gmail.com; debian-ker...@lists.debian.org; debian-arm@lists.debian.org; debian-de...@lists.debian.org; debian-rele...@lists.debian.org Subjec

Re: Enabling -fstack-clash-protection for trixie [armhf rebuild]

2024-01-12 Thread Lucas Nussbaum
Hi, I finally got time to perform those archive rebuilds. Results are available at http://qa-logs.debian.net/2024/01/11/ I did a first archive rebuild (all packages on arm64, armhf, armel), and then did a second one, restricted to packages that failed at on at least one architecture. Results in

Re: Ability to further support 32bit architectures

2024-01-12 Thread rhys
Keeping in mind that I am new to this arena... I have some Intel systems - both 64-bit and 32-bit - that I might be able to use as build platforms.  What does the Debian team need from me to be able to use these systems? I can't guarantee they'll be FAST, but I'll do what I can to make them EF

Re: Ability to further support 32bit architectures

2024-01-12 Thread YunQiang Su
于2024年1月12日周五 23:59写道: > > Keeping in mind that I am new to this arena... > > I have some Intel systems - both 64-bit and 32-bit - that I might be able to > use as build platforms. > I guess all of your hardwares are 64bit. You setup different OS on them. > What does the Debian team need from m

Re: Error: bad immediate value for offset (4100)

2024-01-12 Thread Emanuele Rocca
Hi Mathieu! On 2024-01-12 11:33, Mathieu Malaterre wrote: > Could someone please confirm what I see on the armel/buildd: > > * > https://buildd.debian.org/status/fetch.php?pkg=dcmtk&arch=armel&ver=3.6.8-2&stamp=1705054390&raw=0 > > Is this a 32bits/limited RAM issue ? Is there a way to fix the

Error: bad immediate value for offset (4100)

2024-01-12 Thread Mathieu Malaterre
[CC me please] Dear ARM porters, Could someone please confirm what I see on the armel/buildd: * https://buildd.debian.org/status/fetch.php?pkg=dcmtk&arch=armel&ver=3.6.8-2&stamp=1705054390&raw=0 Is this a 32bits/limited RAM issue ? Is there a way to fix the symptoms ? Thanks !