all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: <tomas@tuxteam.de>
To: emacs-devel@gnu.org
Subject: Re: Emacs' C: static inline considered useless nowadays?
Date: Tue, 18 Oct 2022 19:01:41 +0200	[thread overview]
Message-ID: <Y07b9Wnb1SxhJTck@tuxteam.de> (raw)
In-Reply-To: <83zgdtyxra.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 869 bytes --]

On Tue, Oct 18, 2022 at 06:09:13PM +0300, Eli Zaretskii wrote:
> > From: Stefan Monnier <monnier@iro.umontreal.ca>
> > Cc: Matt Armstrong <matt@rfc20.org>,  emacs-devel@gnu.org
> > Date: Tue, 18 Oct 2022 09:32:32 -0400
> > 
> > > Never mind that; it's a historic accident.  Just use 'static' and let
> > > the compiler decide when to inline.
> > 
> > Since both `gcc` and `clang` obey the `inline` attribute in that case
> > for options like `-Og`, it can still be a good idea to keep them in
> > those places where we think it makes a significant difference.
> 
> Experience shows that we have no idea where it makes a difference.

In the case of gcc, it's at least documented [1] (no idea about clang,
but I'd assume it's documented as well).

For proprietary compilers... we don't talk about proprietary compilers,
do we?

;-)

Cheers
-- 
t

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  reply	other threads:[~2022-10-18 17:01 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-16 22:08 Emacs' C: static inline considered useless nowadays? Matt Armstrong
2022-10-17  0:43 ` Stefan Monnier
2022-10-17  3:13   ` Matt Armstrong
2022-10-17  3:33     ` Óscar Fuentes
2022-10-17  6:10 ` Eli Zaretskii
2022-10-17 19:08   ` Matt Armstrong
2022-10-17 19:12     ` Eli Zaretskii
2022-10-17 20:33       ` Matt Armstrong
2022-10-18  2:30         ` Eli Zaretskii
2022-10-18 13:32           ` Stefan Monnier
2022-10-18 15:09             ` Eli Zaretskii
2022-10-18 17:01               ` tomas [this message]
2022-10-18 19:22               ` Stefan Monnier
2022-10-18 19:31                 ` Eli Zaretskii
2022-10-18 11:58 ` Richard Stallman

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=Y07b9Wnb1SxhJTck@tuxteam.de \
    --to=tomas@tuxteam.de \
    --cc=emacs-devel@gnu.org \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.