Hi Neal,
This seems reminiscent of another closed issue
(https://github.com/serge-sans-paille/pythran/issues/796), which
actually still persists in fluidimage - just in gcc compilers. The
kernel compiles with clang so we don't bother so much. Is it something
similar for you?
Ashwin
On 5/2/19 8:01 PM, Neal Becker wrote:
One thing I see so far, is that my pythran code which caused gcc to
blow up it's memory until I either kill it or it kills my server,
still causes the same with the new gcc-9.0.1.
Not really a fault of pythran though.
On Thu, May 2, 2019 at 1:43 PM Serge Guelton
<serge.guelton@xxxxxxxxxxxxxxxxxxx> wrote:
Hi Pythraners,
I plan to do a release in the forthcoming days, so It's the right time to
check if master branch is working fine on your codebase!
Thanks o/