unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: tomas@tuxteam.de (Tomas Zerolo)
Cc: nickrob@snap.net.nz, Tomas Zerolo <tomas@tuxteam.de>,
	ich@frank-schmitt.net, emacs-devel@gnu.org
Subject: Re: gcc and inline [was: Re: New function for gdb-ui.el?]
Date: Thu, 27 Oct 2005 06:22:43 +0200	[thread overview]
Message-ID: <20051027042243.GA28280@www.trapp.net> (raw)
In-Reply-To: <uvezkdqg8.fsf@gnu.org>


[-- Attachment #1.1: Type: text/plain, Size: 915 bytes --]

On Wed, Oct 26, 2005 at 09:32:39PM +0200, Eli Zaretskii wrote:
> > Date: Wed, 26 Oct 2005 17:02:59 +0200
> > From: tomas@tuxteam.de (Tomas Zerolo)
> > Cc: ich@frank-schmitt.net, Eli Zaretskii <eliz@gnu.org>, rms@gnu.org,
> > 	emacs-devel@gnu.org
> > 
> > No, it's just a hint to the compiler.
> 
> Yes, but GCC is generally known for honoring that hint.

As Andreas said, GCC seems to be getting lazier lately. (Actually, my
knowledge bits were based on a recent experience. -Winline told me, to
my surprise, that some short function wasn't being inlined. But (after
digging and finding this __inline__ __attribute__ thing) forcing the
compiler to do it confirmed the compiler's guess: it wasn't worth the
while (the whole thing was faster by about 1 percent, which I consider
to be noise).

This behaviour was consistent across several gcc versions (2.95 through
3.some).

Regards
-- tomás

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 142 bytes --]

_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel

  parent reply	other threads:[~2005-10-27  4:22 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-23  9:14 New function for gdb-ui.el? Nick Roberts
2005-10-23 11:56 ` Eli Zaretskii
2005-10-23 20:25   ` Nick Roberts
2005-10-23 21:53     ` Kim F. Storm
2005-10-24  6:33       ` Nick Roberts
2005-10-24 11:46         ` Kim F. Storm
2005-10-24 22:07           ` Kim F. Storm
2005-10-24 22:29             ` Nick Roberts
2005-10-25  1:27             ` Nick Roberts
2005-10-25  9:12               ` Kim F. Storm
2005-10-23 20:43   ` Frank Schmitt
2005-10-24  6:57     ` Nick Roberts
2005-10-24  7:35       ` Frank Schmitt
2005-10-24 16:27         ` Richard M. Stallman
2005-10-24 20:26           ` Nick Roberts
2005-10-25 20:27             ` Richard M. Stallman
2005-10-25 23:00               ` Nick Roberts
2005-10-26  6:49                 ` Eli Zaretskii
2005-10-26  8:58                   ` Nick Roberts
2005-10-26 15:02                     ` gcc and inline [was: Re: New function for gdb-ui.el?] Tomas Zerolo
2005-10-26 19:32                       ` Eli Zaretskii
2005-10-26 20:20                         ` Andreas Schwab
2005-10-27  4:22                         ` Tomas Zerolo [this message]
2005-10-27  5:01                           ` Eli Zaretskii
2005-10-28  3:47                             ` Richard M. Stallman
2005-10-28  8:29                               ` Eli Zaretskii
2005-10-28  8:34                                 ` Tomas Zerolo
2005-10-28 11:19                                   ` Miles Bader
2005-10-26 19:31                     ` New function for gdb-ui.el? Eli Zaretskii
2005-10-27  1:30                     ` Richard M. Stallman
2005-10-28 10:54                     ` David Hansen
2005-10-28 12:22                       ` Miles Bader
2005-10-28 21:14                       ` Nick Roberts
2005-10-29 13:02                         ` David Hansen
2005-10-29 20:37                           ` Nick Roberts
2005-10-30  0:11                             ` Miles Bader
2005-10-30 22:33                               ` Nick Roberts
2005-10-26  6:43               ` Eli Zaretskii
2005-10-25  8:14           ` Eli Zaretskii
2005-10-23 21:26 ` Kim F. Storm

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20051027042243.GA28280@www.trapp.net \
    --to=tomas@tuxteam.de \
    --cc=emacs-devel@gnu.org \
    --cc=ich@frank-schmitt.net \
    --cc=nickrob@snap.net.nz \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).