Huge output files
Bug #1284811 reported by
Jan Hruby
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cheerp |
Fix Released
|
High
|
Unassigned |
Bug Description
For your example program dom1 that is compiled with :
clang++ -O3 -target duetto dom1.cpp -o test1.js
I got from 419 bytes of original code 2.03 MB of compiled javascript. That seems to me a bug.
It looks like that the standard library code is included in the output. It should be posible to get rid of it by using static analysis and dead code elemination.
Changed in duetto: | |
status: | New → Confirmed |
importance: | Undecided → High |
Changed in cheerp: | |
status: | Confirmed → Fix Committed |
Changed in cheerp: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
As I see it there is an optimization that should be done.
It should be eliminated partial string construction. It does not make much sense to me. At the compile time you already know what string is going to be constructed.
It will reduce code size also.