From: "Mike Frysinger (vapier)" <vapier@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo commit in src/patchsets/glibc/2.10.1: 0070_all_glibc-i386-x86_64-revert-clone-cfi.patch
Date: Sun, 25 Apr 2010 07:46:58 +0000 (UTC) [thread overview]
Message-ID: <20100425074658.E99382C04C@corvid.gentoo.org> (raw)
vapier 10/04/25 07:46:58
Modified: 0070_all_glibc-i386-x86_64-revert-clone-cfi.patch
Log:
add gentoo bug url
Revision Changes Path
1.2 src/patchsets/glibc/2.10.1/0070_all_glibc-i386-x86_64-revert-clone-cfi.patch
file : http://sources.gentoo.org/viewcvs.py/gentoo/src/patchsets/glibc/2.10.1/0070_all_glibc-i386-x86_64-revert-clone-cfi.patch?rev=1.2&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/src/patchsets/glibc/2.10.1/0070_all_glibc-i386-x86_64-revert-clone-cfi.patch?rev=1.2&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/src/patchsets/glibc/2.10.1/0070_all_glibc-i386-x86_64-revert-clone-cfi.patch?r1=1.1&r2=1.2
Index: 0070_all_glibc-i386-x86_64-revert-clone-cfi.patch
===================================================================
RCS file: /var/cvsroot/gentoo/src/patchsets/glibc/2.10.1/0070_all_glibc-i386-x86_64-revert-clone-cfi.patch,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- 0070_all_glibc-i386-x86_64-revert-clone-cfi.patch 18 May 2009 04:41:06 -0000 1.1
+++ 0070_all_glibc-i386-x86_64-revert-clone-cfi.patch 25 Apr 2010 07:46:58 -0000 1.2
@@ -2,6 +2,7 @@
gcc's unwinder code. this is not a bug in glibc, it triggers problems
elsewhere. this cfi code does not gain us a whole lot anyways.
+http://bugs.gentoo.org/202055
http://gcc.gnu.org/ml/gcc/2006-12/msg00293.html
Index: sysdeps/unix/sysv/linux/i386/clone.S
reply other threads:[~2010-04-25 7:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20100425074658.E99382C04C@corvid.gentoo.org \
--to=vapier@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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