From: "Wilco Dijkstra" <wdijkstr@arm.com>
To: "'Joseph Myers'" <joseph@codesourcery.com>
Cc: "'GNU C Library'" <libc-alpha@sourceware.org>
Subject: RE: [PATCH 2/2] Remove ancient GCC string inlines
Date: Tue, 13 Oct 2015 15:08:00 -0000 [thread overview]
Message-ID: <000f01d105c9$02839c00$078ad400$@com> (raw)
In-Reply-To: <alpine.DEB.2.10.1510121809310.6267@digraph.polyomino.org.uk>
> Joseph Myers wrote:
> On Mon, 12 Oct 2015, Wilco Dijkstra wrote:
>
> > * string/string-inlines.c (__STRING2_COPY_TYPE): Add, moved from string2.h.
>
> > * string/bits/string2.h (__STRING2_COPY_TYPE): Remove.
>
> Does this move of __STRING2_COPY_TYPE mean the patch fixes [BZ #18712]?
It does indeed. It also ensures that future changes of _STRING_ARCH_unaligned no
longer cause backwards compatibility issues due to the inline functions using
different ABIs depending on the _STRING_ARCH_unaligned setting (I didn't find a
BZ entry for this one).
Wilco
next prev parent reply other threads:[~2015-10-13 15:08 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-09 15:53 Wilco Dijkstra
2015-10-09 16:01 ` Joseph Myers
2015-10-09 16:40 ` Wilco Dijkstra
2015-10-09 17:01 ` Joseph Myers
2015-10-12 11:20 ` Wilco Dijkstra
2015-10-12 11:33 ` Joseph Myers
2015-10-12 12:54 ` Wilco Dijkstra
2015-10-12 13:00 ` Joseph Myers
2015-10-12 18:06 ` Wilco Dijkstra
2015-10-12 18:10 ` Joseph Myers
2015-10-13 15:08 ` Wilco Dijkstra [this message]
2015-10-13 15:21 ` Joseph Myers
2015-10-13 16:33 ` Wilco Dijkstra
2015-10-13 17:34 ` Andreas Schwab
2015-10-13 17:29 ` Joseph Myers
2015-10-09 17:07 ` Joseph Myers
[not found] <FF1B652685AE434E94C2981B001E196529AF7B0DBC@GEORGE.Emea.Arm.com>
2015-12-16 13:08 ` Wilco Dijkstra
2015-12-16 18:38 ` Joseph Myers
2015-12-17 13:48 ` Wilco Dijkstra
2015-12-17 20:33 ` Joseph Myers
2015-12-17 22:59 ` Wilco Dijkstra
2016-02-19 17:20 Wilco Dijkstra
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='000f01d105c9$02839c00$078ad400$@com' \
--to=wdijkstr@arm.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@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).