From: "hunt at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug translator/2339] New: optimize out unnecessary copies and assignments
Date: Tue, 14 Feb 2006 17:38:00 -0000 [thread overview]
Message-ID: <20060214173840.2339.hunt@redhat.com> (raw)
Simple concatenations like
str = str."foo"
generate 3 strcpys and a strcat.
x = 5
first copies 5 to a temporary variable then sets x to the temporary variable.
x++
copies 1 to a temporary variable then copies x to a temporary variable, then
adds the two temp and sets x to that,
Is there anything that can be done to make this more efficient?
--
Summary: optimize out unnecessary copies and assignments
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: translator
AssignedTo: systemtap at sources dot redhat dot com
ReportedBy: hunt at redhat dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=2339
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next reply other threads:[~2006-02-14 17:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-14 17:38 hunt at redhat dot com [this message]
2007-04-04 20:15 ` [Bug translator/2339] " dsmith at redhat dot com
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=20060214173840.2339.hunt@redhat.com \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sources.redhat.com \
/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).