public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bob.eric.nelson at gmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/15845] glibc-2.18 (32-bit) segfault with i7-3770K CPU Date: Sun, 18 Aug 2013 17:26:00 -0000 [thread overview] Message-ID: <bug-15845-131-ElbT2CA2bB@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-15845-131@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=15845 --- Comment #4 from re_nelson <bob.eric.nelson at gmail dot com> --- Created attachment 7150 --> http://sourceware.org/bugzilla/attachment.cgi?id=7150&action=edit inline keyword restored to __m128i_strloadu Allan: I can now confirm with 100% certainty that the __strstr_sse42 issue involving the inline keyword having been removed upstream is the problem. Your comments in this thread are spot on: https://bugs.archlinux.org/task/36556?project=1 Before I even saw that thread, trial and error led me to using an "-O3" optimization which had the result of inlining the __m128i_strloadu. After applying the "glibc-2.18-strstr-hackfix.patch" (attached), which restores the "inline" keyword to the function definition, I can again use the "-O2" flag and get a working 32-bit library. 12:26:15 on Sun Aug 18 -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2013-08-18 17:26 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-08-16 19:15 [Bug libc/15845] New: " bob.eric.nelson at gmail dot com 2013-08-16 19:17 ` [Bug libc/15845] " bob.eric.nelson at gmail dot com 2013-08-16 19:18 ` bob.eric.nelson at gmail dot com 2013-08-16 19:30 ` bob.eric.nelson at gmail dot com 2013-08-16 19:32 ` bob.eric.nelson at gmail dot com 2013-08-18 3:45 ` bob.eric.nelson at gmail dot com 2013-08-18 3:46 ` bob.eric.nelson at gmail dot com 2013-08-18 4:06 ` allan at archlinux dot org 2013-08-18 17:26 ` bob.eric.nelson at gmail dot com [this message] 2014-02-07 2:46 ` jsm28 at gcc dot gnu.org 2014-06-13 13:11 ` 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-15845-131-ElbT2CA2bB@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).