From: Joel Brobecker <brobecker@adacore.com>
To: Steve Ellcey <sellcey@mips.com>
Cc: gdb-patches@sourceware.org, binutils@sourcware.org,
yufeng.zhang@arm.com, rdsandiford@googlemail.com
Subject: Re: [Patch] Update include/longlong.h to match GCC
Date: Thu, 01 May 2014 15:56:00 -0000 [thread overview]
Message-ID: <20140501155647.GA28869@adacore.com> (raw)
In-Reply-To: <bc4d7f87-57da-4931-8f5f-5bf9df04c6af@BAMAIL02.ba.imgtec.org>
> I would like to update include/longlong.h to pick up the latest changes
> from GCC and keep this file in sync. I think changes to keep files
> in sync are considered pre-approved so if I don't hear any objections
> I will go ahead. The changes in GCC that are not yet in the binutils
> tree are:
>
> 2014-05-01 Steve Ellcey <sellcey@mips.com>
>
> * include/longlong.h: Use 'defined()' to check __mips16.
>
> 2014-04-30 Richard Sandiford <rdsandiford@googlemail.com>
>
> * longlong.h (__i386__): Remove W_TYPE_SIZE==64 handling.
>
> 2014-04-22 Yufeng Zhang <yufeng.zhang@arm.com>
>
> * longlong.h: Merge from glibc.
Yes, these resyncs should be considered pre-approved.
Thanks for doing this,
--
Joel
prev parent reply other threads:[~2014-05-01 15:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-01 15:18 Steve Ellcey
2014-05-01 15:56 ` Joel Brobecker [this message]
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=20140501155647.GA28869@adacore.com \
--to=brobecker@adacore.com \
--cc=binutils@sourcware.org \
--cc=gdb-patches@sourceware.org \
--cc=rdsandiford@googlemail.com \
--cc=sellcey@mips.com \
--cc=yufeng.zhang@arm.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