Bug#1096811: hipblas: ftbfs with GCC-15

[Santiago Vila <sanvila@debian.org>]

> > I believe this bug ("FTBFS with GCC 15") is fixed in the above
> > version, so I'm closing it by hand now.
> 
> I don't know how I screwed up twice, but 6.4.1-2 FTBFS as well.

Yes, but for an unrelated reason, that's why I filed that as a different bug.

> [...]
> > While we are at it, I noticed a very significant raise in the amount
> > of memory allocated while building the package, from 2GB in trixie to
> > 14GB in current unstable (using machines with 2 CPUs).
> > 
> > Is this normal/expected?
> 
> The hipblas tests have adopted a structure more similar to rocblas and
> they're also building two binaries now instead of one. I think the new
> upstream design is just more resource intensive to build and run.
> 
> I guess it's normal.

Well, the problem now is not just "requiring a lot of memory" in a generic sense
but more like requiring a lot of memory *per* CPU.

In fact, I can build the package on machines with 16 GB of RAM having
1 CPU but not on machines with 16 GB having 2 CPUs, where I get this:

c++: fatal error: Killed signal terminated program cc1plus
compilation terminated.

Could you please adjust the number of CPUs to be used according
to available memory?

I did something like that in graph-tool for the same reason:

https://salsa.debian.org/python-team/packages/graph-tool/-/commit/315bc676236d997573ccdda8d820376755744dab

but I believe now there are more advanced ways to achieve the same.

(Sorry for my flaky memory, Cc: Helmut who will probably remember it)

Thanks.