public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Jeff Law <jeffreyalaw@gmail.com>
To: Tiezhu Yang <yangtiezhu@loongson.cn>, gcc-patches@gcc.gnu.org
Cc: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] gcc: rename floatformat_ia64_quad_{big, little} to floatformat_ieee_quad_{big, little}
Date: Sat, 19 Mar 2022 11:38:20 -0600	[thread overview]
Message-ID: <c89d9816-448a-6ad7-ac54-2c067f3fb521@gmail.com> (raw)
In-Reply-To: <1647227412-4315-1-git-send-email-yangtiezhu@loongson.cn>



On 3/13/2022 9:10 PM, Tiezhu Yang wrote:
> I submitted a GDB patch [1] to rename floatformats_ia64_quad to
> floatformats_ieee_quad to reflect the reality, and then we can
> clean up the related code.
>
> As GDB Global Maintainer Tom Tromey said [2]:
>
>    These files are maintained in gcc and then imported into the
>    binutils-gdb repository, so any changes to them will have to
>    be proposed there first.
>
> this GCC patch is preparation for the GDB patch, no functionality
> change.
>
> [1] https://sourceware.org/pipermail/gdb-patches/2022-March/186452.html
> [2] https://sourceware.org/pipermail/gdb-patches/2022-March/186569.html
>
> Signed-off-by: Tiezhu Yang <yangtiezhu@loongson.cn>
> ---
>
> Hi GCC Maintainers,
>
> I have no write access of gcc.git, if you are OK with this change,
> could you please help me to merge this patch to the gcc master?

While this isn't a behavior change, it is, an ABI change.  We don't have 
a strict backwards compatible ABI mandate for libiberty, but it is 
useful to keep ABI issues in mind when making changes to libraries.  I'm 
not terribly worried about this one.

Also, please make sure to include ChangeLog entries in future submissions.

Thanks.  Installed on the trunk.

Jeff



      reply	other threads:[~2022-03-19 17:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-14  3:10 Tiezhu Yang
2022-03-19 17:38 ` Jeff Law [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=c89d9816-448a-6ad7-ac54-2c067f3fb521@gmail.com \
    --to=jeffreyalaw@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=tom@tromey.com \
    --cc=yangtiezhu@loongson.cn \
    /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).