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] New: glibc-2.18 (32-bit) segfault with i7-3770K CPU Date: Fri, 16 Aug 2013 19:15:00 -0000 [thread overview] Message-ID: <bug-15845-131@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=15845 Bug ID: 15845 Summary: glibc-2.18 (32-bit) segfault with i7-3770K CPU Product: glibc Version: 2.18 Status: NEW Severity: normal Priority: P2 Component: libc Assignee: unassigned at sourceware dot org Reporter: bob.eric.nelson at gmail dot com CC: drepper.fsp at gmail dot com Building a 32-bit glibc-2.18 with the triplet (or quartet) of i686-pc-linux-gnu produces a segfault on Adobe's acrobat (9.5.5) as well as other 32-bit applications including a numerically-intensive antenna modeling app (4nec) running under wine. The problem occurs with these Linux distros tested where I have built the 32-bit version of glibc-2.18: Linux from Scratch, Gentoo-2.2, Slackware-14.0 and CentOS-6.4. 1). The problem does NOT occur with a rollback to glibc-2.17. 2). The problem does NOT occur with the x86_64 (64-bit) build. 3). The problem does NOT occur with glibc-2.18 under VirtualBox which emulates a core2. 4). The problem does not occur on a modest Supermicro C2SBC-Q mainboard with an Intel(R) Pentium(R) Dual E2220 @2.40GHz CPU. 5). The problem DOES occur (and is easily reproduced at will) with on a corei7-avx. Here are the full details of that system: ASUSTeK COMPUTER INC. P8Z77-V LX (Quad-Core Hyper-Threaded Intel(R) Core(TM) i7-3770K @3.50GHz) Memory Error Correction: None Maximum Memory: 32768MB (32GB) ChannelA-DIMM0 BANK 0: 8192MB 1333MHz Synchronous DDR3 DIMM, AMI CMV8GX3M1A1333C9 ChannelA-DIMM1 BANK 1: 8192MB 1333MHz Synchronous DDR3 DIMM, AMI CMX8GX3M1A1333C9 ChannelB-DIMM0 BANK 2: 8192MB 1333MHz Synchronous DDR3 DIMM, AMI CMV8GX3M1A1333C9 ChannelB-DIMM1 BANK 3: 8192MB 1333MHz Synchronous DDR3 DIMM, AMI CMX8GX3M1A1333C9 empty memory sockets: None total memory = 32768MB (32GB) 6). Here's the rest of pertinent information: a). gcc-4.8.1 (also fails with gcc-4.7.2) b). binutils-2.23.2 (also fails with 2.22) c). Linux kernel 3.10.7 (also fails with 3.8.8) d). CFLAGS="-O2 -march=native -pipe" (also fails with CFLAGS undefined and with "-O1 -march=i386") 7). My workaround is to change the triplet from i686-pc-linux to i586-pc-linux or i486-pc-linux. My guess is one or more of the system-dependent assembly files in the "i386/i686" hierarchy doesn't play well with the i7-3770K instruction set. I have not yet toyed with trying to isolated which of the "i386/i686" sourcefiles triggers the error, opting for the expedient approach of using the i586-* triplet. Since I can readily replicate the error, I'll be glad to provide additional information or perform other tests. Also see the thread here when I initially thought the problem may have been isolated to Adobe's acroread: http://www.linuxquestions.org/questions/linux-from-scratch-13/glibc-2-18-and-acroread-4175473288/ -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2013-08-16 19:15 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-08-16 19:15 bob.eric.nelson at gmail dot com [this message] 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 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@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).