From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7771 invoked by alias); 19 May 2016 16:44:20 -0000 Mailing-List: contact crossgcc-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: crossgcc-owner@sourceware.org Received: (qmail 7736 invoked by uid 89); 19 May 2016 16:44:19 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.3 required=5.0 tests=AWL,BAYES_50,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy=rwlocks, !HAS_RTM, cpuinfo.c, elisionconfc X-HELO: mail-io0-f182.google.com Received: from mail-io0-f182.google.com (HELO mail-io0-f182.google.com) (209.85.223.182) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-GCM-SHA256 encrypted) ESMTPS; Thu, 19 May 2016 16:44:09 +0000 Received: by mail-io0-f182.google.com with SMTP id p64so23135745ioi.2 for ; Thu, 19 May 2016 09:44:08 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=e0DqK2LK1Ap+ZuTDdDnzPCfLC8mfSFQY7Qxb4PGuuSE=; b=edUrl8ZJnCdv4lTn9OaAK6YGeLM82b3rmgxJZFyDa2l+hYdCbbBwlYo6jb+m6euT2o 2cXjRHjyqCyXvpOZ5ejj3Nf14DwndWFU11/nPzjF4q5cZoUnx0KpW99ZM0/DsHZgIVGi aYHrQItw9b7OiAoCoX+ixUO0Ywl5Cj4etH+EiSqSGoa9gL+zgxkZeKky8blzrUKAXlS6 BHoU2ISm/y+1SRJJzJcYkYzX9qojIt6seLr/UJafvYAeBbzX1A4MGFZRzU5UQu62DXXD kCuGFj9pvJy2erX3yvWnctFIRBM2Z/XsW9RxviiMQfmx5HSeNwnB7jn8rvumBSBfVUvm A5kw== X-Gm-Message-State: AOPr4FU7TMUWTeea5sVgOmeJBzugcam2rXa+mUwHF7V6e33WIV5qyvUd1fXm6xki8qznSWEytUdVl96g7o8HEQ== MIME-Version: 1.0 X-Received: by 10.107.140.133 with SMTP id o127mr11074581iod.32.1463676247048; Thu, 19 May 2016 09:44:07 -0700 (PDT) Received: by 10.79.118.80 with HTTP; Thu, 19 May 2016 09:44:06 -0700 (PDT) In-Reply-To: References: <64f1a37c-8aa5-be67-eec1-88893ec0d1cf@gmail.com> <03f98607-1993-5dc3-5774-99fe01544886@gmail.com> <8d1c4d18-0915-ac7a-25cb-f531a323b39c@gmail.com> <71a932f2-5e59-ed1e-910c-18b9c1e9089b@gmail.com> Date: Thu, 19 May 2016 16:44:00 -0000 Message-ID: Subject: Re: problem with __init_cpu_features() From: "Carlos O'Donell" To: The Source Cc: "libc-help@sourceware.org" , crossgcc@sourceware.org Content-Type: text/plain; charset=UTF-8 X-SW-Source: 2016-05/txt/msg00016.txt.bz2 On Thu, May 19, 2016 at 10:40 AM, The Source wrote: > 1. I changed libc code slightly to avoid using cpuid inside pthread: > > sysdeps/unix/sysv/linux/x86/elision-conf.c > > Replaced all usage of HAS_RTM to 0: > > __elision_available = 0;//HAS_RTM; > #ifdef ENABLE_LOCK_ELISION > __pthread_force_elision = __libc_enable_secure ? 0 : __elision_available; > #endif > //if (!HAS_RTM) > __elision_aconf.retry_try_xbegin = 0; /* Disable elision on rwlocks */ There should be no use of cpuid inside libpthread. What is failing here? > 2. And crash has gone from libpthread. But poped up in different place: > > libgcc_s: libgcc/config/i386/cpuinfo.c > > __cpu_indicator_init function uses cpuid That would be a gcc bug. File a bug in their tracker. > So cpuid pops up here and there even if everything is built for i486. Isn't > there a way to completely get rid of it? Nobody builds for i486 anymore, so what you're seeing is just bitrot from an untested configuration. Please file bugs and we'll fix everything you can find. Cheers, Carlos. -- For unsubscribe information see http://sourceware.org/lists.html#faq