public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug dynamic-link/15402] Run AVX audit tests for 32-bit x86 Date: Sat, 25 Jan 2014 18:29:00 -0000 [thread overview] Message-ID: <bug-15402-131-gLCGcMLtGP@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-15402-131@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=15402 --- Comment #2 from joseph at codesourcery dot com <joseph at codesourcery dot com> --- But what does "doesn't support SSE" mean? If it means that the interface to audit functions doesn't provide information about SSE register contents, then indeed any parts of the tests that rely on the interface providing such information can't be run for i386. But it should still be the case that audit functions for i386 can be ordinary C functions making use of SSE and AVX, and so clobbering any registers that are call-clobbered, without this interfering with function arguments or return values that are passed in such registers (where the i386 ABI involves use of SSE registers for argument passing or return, this should still work when the function being called is in a shared library). And so to the extent that the tests verify that such audit functions with incidental use of SSE or AVX work, they should be run for i386 - for example, I see nothing in tst-audit3 that should be inapplicable to i386. (If in fact such functions don't work, that's a separate bug.) -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2014-01-25 18:29 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-15402-131@http.sourceware.org/bugzilla/> 2014-01-25 3:45 ` hjl.tools at gmail dot com 2014-01-25 18:29 ` joseph at codesourcery dot com [this message] 2014-01-25 18:43 ` hjl.tools at gmail dot com 2014-02-06 18:22 ` [Bug dynamic-link/15402] [i386] " jsm28 at gcc dot gnu.org 2014-06-13 18:16 ` 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-15402-131-gLCGcMLtGP@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).