public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug ports/16169] AArch64 clone.S is missing some CFI markup
Date: Wed, 27 Nov 2013 17:56:00 -0000 [thread overview]
Message-ID: <bug-16169-131-2Kf5DVrTEj@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16169-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=16169
--- Comment #6 from Tom Tromey <tromey at redhat dot com> ---
Just a friendly ping -- I wasn't sure what to do with this patch.
I can write up a ChangeLog and submit it if you want; but I don't
have any particularly good way to test it (even compile it) right now.
I suppose it would be best if you tested it, as I assume you're
probably already set up for that.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2013-11-27 17:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-13 20:35 [Bug ports/16169] New: " tromey at redhat dot com
2013-11-13 20:46 ` [Bug ports/16169] " tromey at redhat dot com
2013-11-13 22:32 ` carlos at redhat dot com
2013-11-13 22:33 ` carlos at redhat dot com
2013-11-14 0:59 ` ryan.arnold at linaro dot org
2013-11-14 9:30 ` marcus.shawcroft at linaro dot org
2013-11-14 15:32 ` tromey at redhat dot com
2013-11-14 20:27 ` ryan.arnold at linaro dot org
2013-11-27 17:56 ` tromey at redhat dot com [this message]
2013-11-27 17:58 ` ryan.arnold at linaro dot org
2014-01-16 17:40 ` jan.kratochvil at redhat dot com
2014-01-16 17:44 ` mjw at redhat dot com
2014-01-16 17:52 ` mjw at redhat dot com
2014-01-16 18:39 ` carlos at redhat dot com
2014-01-16 20:28 ` tromey at redhat dot com
2014-01-20 15:45 ` cvs-commit at gcc dot gnu.org
2014-01-21 12:44 ` cvs-commit at gcc dot gnu.org
2014-01-21 12:45 ` marcus.shawcroft at linaro dot org
2014-06-13 9:32 ` fweimer at redhat dot com
2020-11-09 10:24 ` fweimer at redhat dot com
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=bug-16169-131-2Kf5DVrTEj@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@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).