From: Mike Stump <mrs@apple.com>
To: HANGUOLING <leohgl@ucla.edu>
Cc: gcc@gcc.gnu.org
Subject: Re: gcc front end help
Date: Wed, 27 Oct 2004 23:58:00 -0000 [thread overview]
Message-ID: <F295656A-284F-11D9-BBBB-000D9330C092@apple.com> (raw)
In-Reply-To: <1098860665.417f4879cf1bc@mail.ucla.edu>
On Oct 27, 2004, at 12:04 AM, HAN,GUOLING wrote:
> Could anyone tell me how to forbid function inline in GCC?
-fno-inline would be the first that comes to mind.
> I tried the compiler options and changed some code in cp directory. It
> dose not work.
Would be nice if you said what options, and an example of the code.
> Could you also help us evaluate the feasibilty of using GCC as our
> frontend?
Sounds interesting.
I suspect this question is best answered in a hardware list, not this
list. Also depends upon just what you want gcc to do for you. The
more you want it to do (optimizations for example), the less well it
will do it. Would be interesting to enhance the edge cases in the
optimizer and add custom optimization passes to deal well in that
domain...
prev parent reply other threads:[~2004-10-27 19:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-27 13:05 HAN,GUOLING
2004-10-27 23:58 ` Mike Stump [this message]
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=F295656A-284F-11D9-BBBB-000D9330C092@apple.com \
--to=mrs@apple.com \
--cc=gcc@gcc.gnu.org \
--cc=leohgl@ucla.edu \
/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).