From: "Alex Rosenberg" <alexr@spies.com>
To: egcs@egcs.cygnus.com
Subject: Re: optimization hints?
Date: Fri, 11 Jun 1999 16:50:00 -0000 [thread overview]
Message-ID: <199906112349.QAA36122@scv3.apple.com> (raw)
> just the fact that I don't expect an error (poll() returning -1),
> I was hoping to be able to tell it that this code isn't likely to
> execute and perhaps even move it someplace else to maximize the
> instruction cache utilization of my code.
Apple's MrC compiler has two pragmas for this:
#pragma seldom
This moves the marked block to the end of the function (after the exit
node).
#pragma outofline
This puts the marked block in a seperate GL function in the XCOFF, which
results in placement at the end of the file by the linker.
Both would be straight-forward to implement in egcs, but pragmas have been
shunned in the past. No keyword alternative approach comes to mind.
A particularly useful variant would be to automatically move C++ catch
blocks.
+------------------------------------------------------------+
| Alexander M. Rosenberg < mailto:alexr@_spies.com > |
| Nobody cares what I say. Remove the underscore to mail me. |
WARNING: multiple messages have this Message-ID
From: "Alex Rosenberg" <alexr@spies.com>
To: egcs@egcs.cygnus.com
Subject: Re: optimization hints?
Date: Wed, 30 Jun 1999 15:43:00 -0000 [thread overview]
Message-ID: <199906112349.QAA36122@scv3.apple.com> (raw)
Message-ID: <19990630154300.ZgaGzWY0XBmlwJd_YceKsQxW76Y-lPeUXTn7NlgRZZw@z> (raw)
> just the fact that I don't expect an error (poll() returning -1),
> I was hoping to be able to tell it that this code isn't likely to
> execute and perhaps even move it someplace else to maximize the
> instruction cache utilization of my code.
Apple's MrC compiler has two pragmas for this:
#pragma seldom
This moves the marked block to the end of the function (after the exit
node).
#pragma outofline
This puts the marked block in a seperate GL function in the XCOFF, which
results in placement at the end of the file by the linker.
Both would be straight-forward to implement in egcs, but pragmas have been
shunned in the past. No keyword alternative approach comes to mind.
A particularly useful variant would be to automatically move C++ catch
blocks.
+------------------------------------------------------------+
| Alexander M. Rosenberg < mailto:alexr@_spies.com > |
| Nobody cares what I say. Remove the underscore to mail me. |
next reply other threads:[~1999-06-11 16:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-11 16:50 Alex Rosenberg [this message]
1999-06-30 15:43 ` Alex Rosenberg
-- strict thread matches above, loose matches on Subject: below --
1999-06-11 17:43 Mike Stump
1999-06-30 15:43 ` Mike Stump
1999-06-11 10:34 Mike Stump
1999-06-16 9:42 ` Alfred Perlstein
1999-06-30 15:43 ` Alfred Perlstein
1999-06-30 15:43 ` Mike Stump
1999-06-11 1:47 Alfred Perlstein
1999-06-11 1:58 ` Jeffrey A Law
1999-06-30 15:43 ` Jeffrey A Law
1999-06-11 6:08 ` Robert Lipe
1999-06-11 9:12 ` Joe Buck
1999-06-30 15:43 ` Joe Buck
1999-06-11 18:28 ` Benjamin Scherrey
1999-06-11 19:17 ` Robert Lipe
1999-06-30 15:43 ` Robert Lipe
1999-06-30 15:43 ` Benjamin Scherrey
1999-06-30 15:43 ` Robert Lipe
1999-06-30 15:43 ` Alfred Perlstein
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=199906112349.QAA36122@scv3.apple.com \
--to=alexr@spies.com \
--cc=egcs@egcs.cygnus.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).