Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
To: Paul E Murphy <murphyp@linux.ibm.com>, gdb-patches@sourceware.org
Subject: Re: [PATCHv2] gnulib: update to 776af40e0
Date: Fri, 5 Feb 2021 13:06:00 -0500	[thread overview]
Message-ID: <94207709-cc81-4571-67d7-01f88e60f79c@polymtl.ca> (raw)
In-Reply-To: <664fefe5-b512-173c-9ea1-ea6b7a821b3c@linux.ibm.com>

On 2021-02-05 12:29 p.m., Paul E Murphy via Gdb-patches wrote:
> 
> 
> On 1/22/21 1:55 PM, Paul E. Murphy wrote:
>> Changes generated by rerunning are left out as the
>> resulting patch is too big for the mailing list.
>>
>> Likewise, tested compilation on x86 and ppc64le,
>> and I do not have commit access, but I do have
>> gnu copyright assignment.
>>
>> V2 updates:
>>
>> Apply suggested fixes from Simon Marchi and
>> Christian Biesinger for unoptimized gcc builds
>> and mingw.
>>
>> ---8<---
>>
>> This fixes PR27184, a failure to compile gdb due to
>> cdefs.h being out of sync with glibc on ppc64le targets
>> which are compiled with -mabi=ieeelongdouble and glibc
>> 2.32.
>>
>> Likewise, update usage of _GL_ATTRIBUTE_FORMAT_PRINTF to
>> _GL_ATTRIBUTE_FORMAT_PRINTF_STANDARD.
>>
>> Likewise, disable newly added rpl_free gnulib api in
>> gdbserver support libraries.
>>
>> Likewise, undefine read/write macros before redefining them
>> on mingw targets.
>>
>> Likewise, wrap C++ usage of free with GNULIB_NAMESPACE namespace
>> as needed.
> 
> Ping.

Since we didn't get any more feedback, I'll push the patch, if anybody
hits some problem they'll report it.

Simon

      reply	other threads:[~2021-02-05 18:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-22 19:55 Paul E. Murphy via Gdb-patches
2021-01-22 20:40 ` Simon Marchi via Gdb-patches
2021-01-25 13:15   ` Christian Biesinger via Gdb-patches
2021-02-05 17:29 ` Paul E Murphy via Gdb-patches
2021-02-05 18:06   ` Simon Marchi via Gdb-patches [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=94207709-cc81-4571-67d7-01f88e60f79c@polymtl.ca \
    --to=gdb-patches@sourceware.org \
    --cc=murphyp@linux.ibm.com \
    --cc=simon.marchi@polymtl.ca \
    /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