From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
To: "'Eli Zaretskii'" <eliz@gnu.org>,
"'Joel Brobecker'" <brobecker@adacore.com>
Cc: <yao@codesourcery.com>, <gdb-patches@sourceware.org>
Subject: RE: New ARI warning Fri Apr 20 01:58:17 UTC 2012
Date: Fri, 20 Apr 2012 11:14:00 -0000 [thread overview]
Message-ID: <00bc01cd1ee3$57938eb0$06baac10$@muller@ics-cnrs.unistra.fr> (raw)
In-Reply-To: <83d372ivjh.fsf@gnu.org>
> -----Message d'origine-----
> De : gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] De la part de Eli Zaretskii
> Envoyé : vendredi 20 avril 2012 11:48
> À : Joel Brobecker
> Cc : yao@codesourcery.com; gdb-patches@sourceware.org
> Objet : Re: New ARI warning Fri Apr 20 01:58:17 UTC 2012
>
> > Date: Thu, 19 Apr 2012 21:38:07 -0700
> > From: Joel Brobecker <brobecker@adacore.com>
> > Cc: gdb-patches@sourceware.org
> >
> > In this particular case, I kind of agree with the warning, but
> > at the same time, I don't really see why we should necessarily
> > ban the use of the "inline" keyword. I'm actually considering
> > the idea of getting rid of this ARI rule.
> >
> > Any opinion on this topic?
>
> Absolutely, the warning should be tossed. There's nothing wrong with
> using it.
I have no opinion on the removal of this rule,
I would just like to be sure that,
if we allow to use inline function,
the configure step will correctly define inline as nothing
on systems using compilers that do not support inline functions.
Does anyone know if this is done inside GDB configuration step?
Pierre Muller
As un-official GDB ARI maintainer ...
next prev parent reply other threads:[~2012-04-20 10:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-20 2:07 GDB Administrator
2012-04-20 2:45 ` Yao Qi
2012-04-20 9:48 ` Joel Brobecker
2012-04-20 10:04 ` Eli Zaretskii
2012-04-20 11:14 ` Pierre Muller [this message]
[not found] ` <43835.7730432928$1334919059@news.gmane.org>
2012-04-20 12:41 ` Andreas Schwab
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='00bc01cd1ee3$57938eb0$06baac10$@muller@ics-cnrs.unistra.fr' \
--to=pierre.muller@ics-cnrs.unistra.fr \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=yao@codesourcery.com \
/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