>always optimal. Still, we might benefit from some of the optimizations.
>Have you tried calling opt with vectorizations disabled?
I tried quickly this morning with vectorization disabled on opt and that solved
the problem. But I ran into another - sdcc ran out of memory. It gets up to
2GB me
On 22.11.2016 14:45, alvin albrecht wrote:
>
>>always optimal. Still, we might benefit from some of the optimizations.
>>Have you tried calling opt with vectorizations disabled?
>
> I tried quickly this morning with vectorization disabled on opt and that
> solved the problem. But I ran into anot
hello all,
even at the risk of embarrassing myself: can someone please explain me the
benefit of LLVM+SDCC toolchain vs. the "normal“ SDCC-only build? What is the
motivation behind? Sorry for my ignorance and thanks for a (simple)
explanation…!
Regards,
Georg Icking-Konert
--
On 22.11.2016 21:55, Georg Icking-Konert wrote:
> hello all,
>
> even at the risk of embarrassing myself: can someone please explain
> me the benefit of LLVM+SDCC toolchain vs. the "normal“ SDCC-only
> build? What is the motivation behind? Sorry for my ignorance and
> thanks for a (simple) explana
