public inbox for java-prs@sourceware.org help / color / mirror / Atom feed
From: "mckinlay at redhat dot com" <gcc-bugzilla@gcc.gnu.org> To: java-prs@gcc.gnu.org Subject: [Bug java/18190] [4.0 regression] primitive array optimization is gone Date: Thu, 04 Nov 2004 18:46:00 -0000 [thread overview] Message-ID: <20041104184608.22958.qmail@sourceware.org> (raw) In-Reply-To: <20041028011546.18190.tromey@gcc.gnu.org> ------- Additional Comments From mckinlay at redhat dot com 2004-11-04 18:46 ------- Here's my thoughts about this: - This optimization only ever worked for source compilation. Bytecode compilers always emit array initializers as code, so for byte compilation it makes no difference. - I don't see a strong reason not to reference the vtable symbols, but if we decide to remove my patch then we need to be careful that the original bug remains fixed - see: http://gcc.gnu.org/ml/java-patches/2004-q3/msg00343.html - Is this optimization really worth worrying about? I'm pretty sure that performance-wise, the difference is insignificant - binary size is what we should be concerned about here. Is a binary that initializes arrays in code significantly larger? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18190
next prev parent reply other threads:[~2004-11-04 18:46 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-10-28 1:15 [Bug java/18190] New: " tromey at gcc dot gnu dot org 2004-10-28 1:39 ` [Bug java/18190] " pinskia at gcc dot gnu dot org 2004-11-04 4:53 ` pinskia at gcc dot gnu dot org 2004-11-04 18:46 ` mckinlay at redhat dot com [this message] 2004-11-04 21:19 ` pinskia at gcc dot gnu dot org 2004-11-04 23:06 ` pinskia at gcc dot gnu dot org 2005-01-11 13:48 ` pinskia at gcc dot gnu dot org 2005-01-19 18:52 ` mmitchel at gcc dot gnu dot org 2005-03-05 19:58 ` [Bug java/18190] [4.0/4.1 " pinskia at gcc dot gnu dot org 2005-08-22 1:47 ` mmitchel at gcc dot gnu dot 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=20041104184608.22958.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=java-prs@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: linkBe 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).