public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug dynamic-link/16275] New: x86-64 dynamic linker should preserve bound registers Date: Fri, 29 Nov 2013 12:36:00 -0000 [thread overview] Message-ID: <bug-16275-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=16275 Bug ID: 16275 Summary: x86-64 dynamic linker should preserve bound registers Product: glibc Version: 2.19 Status: NEW Severity: normal Priority: P2 Component: dynamic-link Assignee: unassigned at sourceware dot org Reporter: hjl.tools at gmail dot com Intel MPX uses bound registers for bound parameter passing. Since legacy branches will destroy bound registers, ld.so should preserve bound registers. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2013-11-29 12:36 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-11-29 12:36 hjl.tools at gmail dot com [this message] 2014-02-06 18:20 ` [Bug dynamic-link/16275] [i386/x86_64] " jsm28 at gcc dot gnu.org 2014-06-13 11:51 ` fweimer at redhat dot com 2014-08-13 14:58 ` hjl.tools at gmail 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-16275-131@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: linkBe 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).