From: Daniel Jacobowitz <drow@false.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: binutils@sources.redhat.com
Subject: Re: [RFA] Fix compilation warnings in irix-core.c
Date: Tue, 29 Mar 2005 04:59:00 -0000 [thread overview]
Message-ID: <20050328225322.GA1345@nevyn.them.org> (raw)
In-Reply-To: <20050328224444.GS2295@adacore.com>
On Mon, Mar 28, 2005 at 02:44:44PM -0800, Joel Brobecker wrote:
> Hello,
>
> GDB currently fails to build on mips/irix due to warnings now being
> turned into errors. I am unfortunately lacking the time to look deeply
> into this at the moment (I have asked one of my coworkers to help me
> with that), but there was one file where the fixes were I think obvious.
> Here is a patch for it:
>
> 2005-03-28 Joel Brobecker <brobecker@adacore.com>
>
> * irix-core.c (do_sections): Add parenthesis in expression
> to avoid a compiler warning.
> (irix_core_core_file_matches_executable_p): Add ATTRIBUTE_UNUSED
> to unused parameters to avoid a compiler warning.
>
> The changes should be nops. The only question I had was regarding
> the conversion to ISO C (ie have "int foo (char *bar) {" instead of
> "int foo (bar) char * bar; {"). For now, I just left the file as is.
> I think the conversion should be done in a patch of its own anyway.
I agree.
> Tested by building GDB and running the GDB testsuite.
> OK to apply?
> - SEC_ALLOC | SEC_LOAD+SEC_HAS_CONTENTS,
How about just changing the + to an | ?
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-03-28 22:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-29 4:32 Joel Brobecker
2005-03-29 4:59 ` Daniel Jacobowitz [this message]
2005-03-29 5:11 ` Thiemo Seufer
2005-03-29 6:03 ` Eric Christopher
2005-03-29 6:19 ` Joel Brobecker
2005-03-29 6:29 ` Eric Christopher
2005-03-29 8:31 ` Joel Brobecker
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=20050328225322.GA1345@nevyn.them.org \
--to=drow@false.org \
--cc=binutils@sources.redhat.com \
--cc=brobecker@adacore.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).