Hello --
I am on this list, you know :)
There may well be opportunities in tcc for a peephole optimizer
approach, but I'll caution that each compiler is different and that blog
post was examining QBE, so it wouldn't necessarily be a direct 1:1
mapping. QBE does a lot of optimization itself before writing out its
final assembly.
~Brian
On 4/4/2022 10:26 AM, Domingo Alvarez Duarte wrote:
After reading this https://briancallahan.net/blog/20220330.html and
using a citation on this list about dumping the ASM generated by TCC
using objdump maybe we can find patterns on the generated code and
identify where it's produced and update then.
On 31/3/22 20:16, rempas via Tinycc-devel wrote:
31 Μαρ 2022, 19:35 Από david.koch@libertysurf.fr:
Have a look : https://github.com/adorad/tcc and
https://github.com/adorad/adorad
----- Mail d'origine -----
De: rempas via Tinycc-devel <tinycc-devel@nongnu.org>
À: Tinycc Devel <tinycc-devel@nongnu.org>
Cc: rempas@tutanota.com, Tinycc Devel <tinycc-devel@nongnu.org>
Envoyé: Tue, 29 Mar 2022 21:12:37 +0200 (CEST)
Objet: Re: [Tinycc-devel] Re : Some questions regarding of TCC's
optimizations.
Thanks a lot! I will look at it!
_______________________________________________
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tinycc-devel
_______________________________________________
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tinycc-devel