This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug nptl/16125] New: Issue with glibc lock elision implementation for Haswell CPU
- From: "alphazo at gmail dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Tue, 05 Nov 2013 22:01:32 +0000
- Subject: [Bug nptl/16125] New: Issue with glibc lock elision implementation for Haswell CPU
- Auto-submitted: auto-generated
https://sourceware.org/bugzilla/show_bug.cgi?id=16125
Bug ID: 16125
Summary: Issue with glibc lock elision implementation for
Haswell CPU
Product: glibc
Version: 2.18
Status: NEW
Severity: normal
Priority: P2
Component: nptl
Assignee: unassigned at sourceware dot org
Reporter: alphazo at gmail dot com
CC: drepper.fsp at gmail dot com
Created attachment 7268
--> https://sourceware.org/bugzilla/attachment.cgi?id=7268&action=edit
Kdenlive BT
I just installed ArchLinux on a brand new Intel i7 4770S (Haswell) because my
old laptop was unable to handle HD content properly under Kdenlive. I have the
exact package versions on both machines but when disabling a simple effect in
Kdenlive I get a seg fault on the new machine.
You can see my bug report on Kdenlive bug tracker here:
http://www.kdenlive.org/mantis/view.php?id=3186
and ArchLinux bug tracker there:
https://bugs.archlinux.org/task/37617
I looked at the trace and found this stuff about lock elision that seems very
(hardware) specific to Haswell CPU.
I looked at the PKGBUILD for the pre-compiled glibc 2.18-9 that ships with
ArchLinux and it has the "--enable-lock-elision" switch so I used ABS to
recompile it without this switch. And yes problem is gone.
Is this a problem with Kdenlive code or lock elision implementation in current
glibc when ran on Haswell processors ? Don't know if this is related but I also
had some repetive issues with Digikam when using the default glibc.
--
You are receiving this mail because:
You are on the CC list for the bug.