From: "Martin v. Loewis" <martin@loewis.home.cs.tu-berlin.de>
To: jamie.lokier@cern.ch
Cc: n@pcep-jamie.cern.ch, osken393@student.liu.se, gcc@gcc.gnu.org
Subject: Re: Inlining Improvements
Date: Fri, 31 Dec 1999 23:54:00 -0000 [thread overview]
Message-ID: <199912211736.SAA08498@loewis.home.cs.tu-berlin.de> (raw)
Message-ID: <19991231235400.bZ7hZlnKfMmSkU1ZVIX4Ym7QhY33lE5yRxeVuKB9kHI@z> (raw)
In-Reply-To: <19991221170444.B10482@pcep-jamie.cern.ch>
> So we have a situation where the C++ compiler generates better code than
> the C compiler from the same source?
It might be possible to create examples. On the average, I doubt that.
If it is plain C code that also compiles as C++ code, inlining most
likely happens at the same places.
I believe that the main advantage is in terms of memory consumption in
the compiler itself.
> Are there plans to add the tree inlining to C any time soon?
I can't answer that question.
Regards,
Martin
next prev parent reply other threads:[~1999-12-31 23:54 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-21 2:49 Oskar Enoksson
1999-12-21 4:59 ` Martin v. Loewis
1999-12-21 8:04 ` Jamie Lokier
1999-12-21 8:55 ` Mark Mitchell
1999-12-21 9:06 ` Jamie Lokier
1999-12-31 23:54 ` Jamie Lokier
1999-12-31 23:54 ` Mark Mitchell
1999-12-21 9:43 ` Jeffrey A Law
1999-12-31 23:54 ` Jeffrey A Law
1999-12-21 9:46 ` Martin v. Loewis [this message]
1999-12-21 16:00 ` Jamie Lokier
1999-12-21 16:08 ` Joe Buck
1999-12-22 0:35 ` Martin v. Loewis
1999-12-31 1:56 ` Kevin Atkinson
1999-12-31 23:54 ` Kevin Atkinson
1999-12-31 23:54 ` Martin v. Loewis
1999-12-31 23:54 ` Joe Buck
1999-12-22 0:04 ` Martin v. Loewis
1999-12-22 0:15 ` Marcin Dalecki
1999-12-22 1:56 ` Martin v. Loewis
1999-12-31 23:54 ` Martin v. Loewis
1999-12-31 23:54 ` Marcin Dalecki
1999-12-22 6:57 ` Jamie Lokier
1999-12-22 7:58 ` Mark Mitchell
1999-12-31 23:54 ` Mark Mitchell
1999-12-31 23:54 ` Jamie Lokier
1999-12-31 23:54 ` Martin v. Loewis
1999-12-31 23:54 ` Jamie Lokier
1999-12-31 23:54 ` Martin v. Loewis
1999-12-31 23:54 ` Jamie Lokier
1999-12-31 23:54 ` Martin v. Loewis
1999-12-31 23:54 ` Oskar Enoksson
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=199912211736.SAA08498@loewis.home.cs.tu-berlin.de \
--to=martin@loewis.home.cs.tu-berlin.de \
--cc=gcc@gcc.gnu.org \
--cc=jamie.lokier@cern.ch \
--cc=n@pcep-jamie.cern.ch \
--cc=osken393@student.liu.se \
/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).