public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug build/16873] GDB 7.7 does not build with GCC 4.9
Date: Thu, 24 Apr 2014 23:16:00 -0000	[thread overview]
Message-ID: <bug-16873-4717-sTP6YOqCyM@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16873-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=16873

--- Comment #1 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "gdb and binutils".

The branch, gdb-7.7-branch has been updated
       via  8a90a4ef6a9c5acb6fd363c7c556682578aa9254 (commit)
      from  87a1630ead223311c409d19e98553c4fa363cb59 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=8a90a4ef6a9c5acb6fd363c7c556682578aa9254

commit 8a90a4ef6a9c5acb6fd363c7c556682578aa9254
Author: Nick Clifton <nickc@redhat.com>
Date:   Wed Jan 29 13:46:39 2014 +0000

    Following up on Tom's suggestion I am checking in a patch to replace the
various
    bfd_xxx_set macros with static inline functions, so that we can avoid
compile time
    warnings about comma expressions with unused values.

        PR build/16873
        * bfd-in.h (bfd_set_section_vma): Delete.
        (bfd_set_section_alignment): Delete.
        (bfd_set_section_userdata): Delete.
        (bfd_set_cacheable): Delete.
        * bfd.c (bfd_set_cacheable): New static inline function.
        * section.c (bfd_set_section_userdata): Likewise.
        (bfd_set_section_vma): Likewise.
        (bfd_set_section_alignment): Likewise.
        * bfd-in2.h: Regenerate.

-----------------------------------------------------------------------

Summary of changes:
 bfd/ChangeLog |   14 ++++++++++++++
 bfd/bfd-in.h  |    5 -----
 bfd/bfd-in2.h |   41 +++++++++++++++++++++++++++++++++++------
 bfd/bfd.c     |    8 ++++++++
 bfd/section.c |   26 ++++++++++++++++++++++++++
 5 files changed, 83 insertions(+), 11 deletions(-)

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  parent reply	other threads:[~2014-04-24 23:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-24 22:43 [Bug build/16873] New: " sergiodj at redhat dot com
2014-04-24 22:43 ` [Bug build/16873] " sergiodj at redhat dot com
2014-04-24 23:16 ` cvs-commit at gcc dot gnu.org [this message]
2014-04-24 23:18 ` sergiodj at redhat dot com

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=bug-16873-4717-sTP6YOqCyM@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).