From: "Pierre Muller" <muller@ics.u-strasbg.fr>
To: "'Joel Brobecker'" <brobecker@adacore.com>
Cc: <gdb-patches@sourceware.org>, <gdb@sourceware.org>
Subject: RE: GDB ARIndex cleanup
Date: Fri, 27 Mar 2009 08:43:00 -0000 [thread overview]
Message-ID: <001201c9aeb5$44ece820$cec6b860$@u-strasbg.fr> (raw)
In-Reply-To: <20090326230959.GN9472@adacore.com>
> -----Message d'origine-----
> De : Joel Brobecker [mailto:brobecker@adacore.com]
> Envoyé : Friday, March 27, 2009 12:10 AM
> À : Pierre Muller
> Cc : gdb-patches@sourceware.org; gdb@sourceware.org; 'Eli Zaretskii'
> Objet : Re: GDB ARIndex cleanup
>
> > 1) "inline"
> > for inline, someone once said that the rule that we should not use
> > "inline" keyword is old, and maybe not correct anymore.
> >
> > If everyone agrees that this rule should stay, I will be happy to
> > commit an obvious fix removing all of them as this seems quite
> > mechanical, but I wanted to get some feedback first.
>
> I don't know much about the effectiveness of using "inline".
> I personally tend to avoid it, because I trust the compiler to
> determine
> whether an inline will help or not. So I'm OK either way.
As Daniel seems to think that is can be useful
(maybe for non GNU compilers?) should
we use some configure set macro like
INLINE
that would be set to nothing for GNU gcc
but could be inline for other compilers?
Configure already checks for the ability of inline,
but it could be modified to discard inline altogether
for gcc, no?
Pierre Muller
Pascal language support maintainer for GDB
next prev parent reply other threads:[~2009-03-27 8:23 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-26 15:29 Pierre Muller
2009-03-26 20:53 ` Eli Zaretskii
2009-03-27 8:23 ` Pierre Muller
2009-03-27 8:47 ` Eli Zaretskii
2009-03-27 14:12 ` Eli Zaretskii
2009-03-27 15:35 ` Eli Zaretskii
2009-04-02 15:12 ` Thiago Jung Bauermann
2009-04-02 19:40 ` Eli Zaretskii
2009-04-02 20:34 ` Joel Brobecker
2009-03-26 23:18 ` Joel Brobecker
2009-03-27 2:22 ` Daniel Jacobowitz
2009-03-27 8:43 ` Pierre Muller [this message]
2009-03-27 16:04 ` Joel Brobecker
2009-03-27 16:46 ` Daniel Jacobowitz
2009-04-14 23:06 ` [RFC] GDB ARIndex Linux rule cleanup Pierre Muller
2009-04-14 23:23 ` Mark Kettenis
2009-04-14 23:38 ` Pedro Alves
2009-04-14 23:41 ` Joel Brobecker
2009-04-15 7:06 ` Pierre Muller
2009-04-15 7:33 ` Eli Zaretskii
2009-04-15 14:00 ` Ulrich Weigand
2009-04-15 14:21 ` Pedro Alves
2009-04-15 15:32 ` Ulrich Weigand
2009-04-15 15:54 ` Pedro Alves
2009-04-15 14:25 ` Eli Zaretskii
2009-04-15 15:15 ` Daniel Jacobowitz
2009-04-15 15:23 ` Ulrich Weigand
2009-04-15 15:34 ` Mark Kettenis
2009-04-15 16:00 ` Eli Zaretskii
2009-04-15 16:04 ` Eli Zaretskii
2009-04-15 17:34 ` Ulrich Weigand
2009-04-15 18:07 ` Eli Zaretskii
2009-04-15 18:55 ` Ulrich Weigand
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='001201c9aeb5$44ece820$cec6b860$@u-strasbg.fr' \
--to=muller@ics.u-strasbg.fr \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=gdb@sourceware.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox