leaningtech-dev team mailing list archive

[Jan Hruby <jhruby.web@xxxxxxxxx>]

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.

** Attachment added: "string-construction.png"
   https://bugs.launchpad.net/duetto/+bug/1284811/+attachment/3996755/+files/string-construction.png

-- 
You received this bug notification because you are a member of
Leaningtech Team, which is subscribed to Duetto.
https://bugs.launchpad.net/bugs/1284811

Title:
  Huge output files

Status in Duetto: C++ for the Web:
  New

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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/duetto/+bug/1284811/+subscriptions