public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mingodad at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/51622] GCC generates bad code that generate big executable sizes when using _Decimal*
Date: Mon, 19 Dec 2011 12:24:00 -0000	[thread overview]
Message-ID: <bug-51622-4-x0iEv718mH@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51622-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51622

--- Comment #1 from Domingo Alvarez <mingodad at gmail dot com> 2011-12-19 12:17:28 UTC ---
If code generation is solved probably we can have better results with the
following:

lua 5.1.4 with double -> 150KB
lua 5.1.4 with _Decimal64 -> 2.4MB *with ***bad code generation
lua 5.1.4 with _Decimal64 -> 160KB *with hopefully ***good code generation

sqlite3 with double -> 500KB
sqlite3 with _Decimal64 -> 3MB *with ***bad code generation
sqlite3 with _Decimal64 -> 530KB *with hopefully ***good code generation

The same proportion probably will apply to any other program using _Decimal*
wich will make using _Decimal* a very interesting option.


  reply	other threads:[~2011-12-19 12:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-19 12:11 [Bug c/51622] New: " mingodad at gmail dot com
2011-12-19 12:24 ` mingodad at gmail dot com [this message]
2011-12-19 12:27 ` [Bug c/51622] " rguenth at gcc dot gnu.org
2011-12-19 12:41 ` redi at gcc dot gnu.org
2011-12-19 14:33 ` mingodad at gmail dot com
2011-12-19 14:41 ` mingodad at gmail dot com
2011-12-19 14:43 ` mingodad at gmail dot com
2011-12-19 15:31 ` jakub at gcc dot gnu.org
2011-12-19 21:39 ` mingodad at gmail dot com
2011-12-20 17:31 ` mingodad at gmail dot com
2011-12-21 10:40 ` mingodad at gmail dot com
2013-11-10 19:43 ` pinskia at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-51622-4-x0iEv718mH@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).