Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
To: "'Jan Kratochvil'" <jan.kratochvil@redhat.com>, <tromey@redhat.com>
Cc: "'Pedro Alves'" <pedro@codesourcery.com>,
	<gdb-patches@sourceware.org>,
	       "'Mark Kettenis'" <mark.kettenis@xs4all.nl>
Subject: RE: [patch] ATTR_NORETURN -> ATTRIBUTE_NORETURN unification  [Re: [patch] ATTR_* -> ATTRIBUTE_* unification]
Date: Tue, 04 May 2010 06:34:00 -0000	[thread overview]
Message-ID: <001501caeb53$d8c3bd40$8a4b37c0$@muller@ics-cnrs.unistra.fr> (raw)
In-Reply-To: <20100503074356.GA14569@host0.dyn.jankratochvil.net>



> -----Message d'origine-----
> De : gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] De la part de Jan Kratochvil
> Envoyé : Monday, May 03, 2010 9:44 AM
> À : Pierre Muller
> Cc : 'Pedro Alves'; gdb-patches@sourceware.org; 'Mark Kettenis'
> Objet : Re: [patch] ATTR_NORETURN -> ATTRIBUTE_NORETURN unification
> [Re: [patch] ATTR_* -> ATTRIBUTE_* unification]
> 
> On Mon, 03 May 2010 09:17:42 +0200, Pierre Muller wrote:
> >   Should I add a rule to gdb_ari.sh
> > suggesting to use ATTRIBUTE_NORETURN
> > instead of NORETURN or ATTR_NORETURN?
> >
> >   Should I do the same for ATTRIBUTE_PRINTF?
> 
> Any of an inadvertent use of NORETURN, ATTR_NORETURN or ATTR_FORMAT now
> causes
> a compilation error as definitions of these symbols have been removed
> now.
> Therefore I believe ARI is not needed in this case.
  
  But they could still be defined in some 
headers of a particular system.
  If someone uses such a macro for a native file,
we will get no feedback...


  Tom, what did you mean by poison these identifiers?
Something like
#undef NORETURN
#define NORETURN "Anything that will for sure create a compilation error"

I see nothing like this in gdb/defs.h 
Is this something we should start?

  
Pierre



  reply	other threads:[~2010-05-04  6:34 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-30 18:16 [patch 1/3] Make obconcat use stdarg Jan Kratochvil
2010-04-30 18:38 ` Tom Tromey
2010-04-30 19:07   ` Jan Kratochvil
2010-04-30 19:09 ` Mark Kettenis
2010-04-30 22:18   ` `sentinel' gcc-3.x/OpenBSD compat. [Re: [patch 1/3] Make obconcat use stdarg] Jan Kratochvil
2010-05-01  0:10     ` Pedro Alves
2010-05-02 12:04       ` [patch] ATTR_* -> ATTRIBUTE_* unification [Re: `sentinel' gcc-3.x/OpenBSD compat.] Jan Kratochvil
2010-05-02 15:33         ` Pedro Alves
2010-05-02 21:37           ` Jan Kratochvil
2010-05-02 23:20             ` [patch] ATTR_NORETURN -> ATTRIBUTE_NORETURN unification [Re: [patch] ATTR_* -> ATTRIBUTE_* unification] Jan Kratochvil
2010-05-02 23:42               ` Pedro Alves
2010-05-02 23:53                 ` Jan Kratochvil
2010-05-03  7:18                   ` Pierre Muller
2010-05-03  7:44                     ` Jan Kratochvil
2010-05-04  6:34                       ` Pierre Muller [this message]
2010-05-04 15:28                         ` Joel Brobecker
     [not found]                   ` <6652.26431233368$1272871093@news.gmane.org>
2010-05-03 18:15                     ` Tom Tromey
2010-05-01  6:07     ` `sentinel' gcc-3.x/OpenBSD compat. [Re: [patch 1/3] Make obconcat use stdarg] Eli Zaretskii
2010-05-02  6:49       ` Jan Kratochvil
2010-05-01  8:53     ` Mark Kettenis
2010-05-07 16:58       ` Jan Kratochvil
2010-05-07 22:34         ` Tom Tromey
2010-05-08  4:59           ` Jan Kratochvil
2010-05-02  7:52   ` [patch 1/3] Make obconcat use stdarg Jan Kratochvil
2010-05-03 18:25     ` Tom Tromey
2010-05-03 20:19     ` Mark Kettenis
2010-05-03 21:00       ` Pedro Alves
2010-05-04 21:03         ` Mark Kettenis
2010-05-07 14:31           ` Jan Kratochvil
2010-05-07 14:36             ` Pedro Alves
2010-05-07 14:44               ` Jan Kratochvil
2010-05-07 14:44             ` Mark Kettenis

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='001501caeb53$d8c3bd40$8a4b37c0$@muller@ics-cnrs.unistra.fr' \
    --to=pierre.muller@ics-cnrs.unistra.fr \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    --cc=mark.kettenis@xs4all.nl \
    --cc=pedro@codesourcery.com \
    --cc=tromey@redhat.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