From: Cleber Rosa <crosa@redhat.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org, sergiodj@redhat.com, lmr@redhat.com,
brobecker@adacore.com
Subject: Re: [v2,2/2] Function attributes: use shorter versions of the format macros
Date: Sat, 13 Dec 2014 16:21:00 -0000 [thread overview]
Message-ID: <1150220882.18385946.1418487658609.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <548AD6C7.1000205@redhat.com>
----- Original Message -----
> From: "Pedro Alves" <palves@redhat.com>
> To: "Cleber Rosa" <crosa@redhat.com>, gdb-patches@sourceware.org
> Cc: sergiodj@redhat.com, lmr@redhat.com, brobecker@adacore.com
> Sent: Friday, December 12, 2014 8:51:35 AM
> Subject: Re: [v2,2/2] Function attributes: use shorter versions of the format macros
>
> On 12/11/2014 06:50 PM, Cleber Rosa wrote:
> > glibc provides a wide range of function attributes that can help GCC during
> > code compilation.
> >
> > One step further, glibc also provides in /usr/include/ansidecl.h a generic
> > version of a macro called ATTRIBUTE_PRINTF, based on the format function
> > attribute, and others that are more specific and shorter to write, read and
> > grasp.
>
> We have an ansidecl.h in gdb/../include/
> that still says it's part of glibc, but the glibc copy AFAIK is long
> gone. Seems to have been removed in 1997:
>
> 1997-06-13 10:06 Richard Henderson <rth@tamu.edu>
> ...
> * ansidecl.h: Removed.
>
> I don't have a /usr/include/ansidecl.h in my F20 system, nor do I see
> any ansidecl.h in the glibc sources.
>
> I'd guess your /usr/include/ansidecl.h file is really our/gcc's file,
> not glibc's.
I do have /usr/include/ansidecl.h on my F20 box, but you're right, it's not a part of glibc but part of binutils(-devel).
>
> >
> > For consistency sake, let's use these shorter versions of those macros.
>
> Consistency with? You mean, consistency throughout?
Throughout the whole repo (git://sourceware.org/git/binutils-gdb.git). The ATTRIBUTE_PRINTF_* is found on binutils/*, gold/*, libiberty/*, etc.
>
> >
> > For more information:
> > * /usr/include/ansidecl.h
> > *
> > https://gcc.gnu.org/onlinedocs/gcc/Function-Attributes.html#index-Wformat-2963
> >
> > gdb/ChangeLog:
> >
> > * ada-lang.c (lim_warning): use shorter versions of function attributes
> > macros.
>
> Uppercase "use".
OK!
>
> > gdb/gdbserver/ChangeLog:
> >
> > * ax.c (ax_vdebug): use shorter versions of function attributes
> > macros.
>
> Likewise.
>
> The patch itself looks fine to me (too).
Will send a v3, thanks!
>
> Thanks,
> Pedro Alves
>
>
next prev parent reply other threads:[~2014-12-13 16:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-01 15:58 [PATCH 1/2] remote-utils.c: remove unused gdb_stdlog Cleber Rosa
2014-12-01 15:58 ` [PATCH 2/2] Function attributes: use shorter versions of the format macros Cleber Rosa
2014-12-01 20:39 ` Sergio Durigan Junior
2014-12-03 10:31 ` Joel Brobecker
2014-12-04 13:29 ` Cleber Rosa
2014-12-11 18:51 ` [v2,1/2] remote-utils.c: remove unused gdb_stdlog Cleber Rosa
2014-12-11 18:51 ` [v2,2/2] Function attributes: use shorter versions of the format macros Cleber Rosa
2014-12-12 11:51 ` Pedro Alves
2014-12-13 16:21 ` Cleber Rosa [this message]
2014-12-01 20:34 ` [PATCH 1/2] remote-utils.c: remove unused gdb_stdlog Sergio Durigan Junior
2014-12-03 10:12 ` Joel Brobecker
2014-12-04 16:49 ` Sergio Durigan Junior
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=1150220882.18385946.1418487658609.JavaMail.zimbra@redhat.com \
--to=crosa@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=lmr@redhat.com \
--cc=palves@redhat.com \
--cc=sergiodj@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