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/17187] New: Call to java.lang.Object constructor is redundant Date: Wed, 25 Aug 2004 15:45:00 -0000 [thread overview] Message-ID: <20040825154545.17187.mckinlay@redhat.com> (raw) The constructor for java.lang.Object does nothing. Its probably a reasonable assumption that it will always do nothing, so, we should change the compiler to not generate calls to it when generating native code. This would save 1 call for every "new" operation, and also improve the number of inlining opportunities available to the compiler, as many constructor calls could now be fully inlined. One way to do this might be to extend the java "builtins" mechanism to allow us to turn other well known calls, not just Math.* calls, into inlined trees. If we see a java.lang.Object() call, check_for_builtin() would just return an empty statement tree. -- Summary: Call to java.lang.Object constructor is redundant Product: gcc Version: 3.5.0 Status: UNCONFIRMED Keywords: missed-optimization Severity: enhancement Priority: P2 Component: java AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: mckinlay at redhat dot com CC: gcc-bugs at gcc dot gnu dot org,java-prs at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17187
next reply other threads:[~2004-08-25 15:45 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-08-25 15:45 mckinlay at redhat dot com [this message] 2004-08-25 15:58 ` [Bug java/17187] " pinskia at gcc dot gnu dot org 2004-08-25 16:16 ` mckinlay at redhat dot com 2004-11-08 2:49 ` pinskia 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=20040825154545.17187.mckinlay@redhat.com \ --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).