From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26648 invoked by alias); 4 Nov 2016 12:12:47 -0000 Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-alpha-owner@sourceware.org Received: (qmail 26636 invoked by uid 89); 4 Nov 2016 12:12:46 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy= X-HELO: mail-vk0-f42.google.com X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=a8nWAwa5ZARfxlQv0BOhOmGk/0WZmzeNj+fhUnYoysg=; b=dAhGbDkvjpMScefsBvwdLSjYyKrkRsUBe30b/TPLbak33GrvFbrELNtvd4LcOebIDD tlOgry7PBBZsZ+soWmljHvM49JS/K74zcg1Xu9+5FCsumqrFKj1bkfMjaRjPToBtgr82 J+4YDX4w1I+txWUXwQAE7fxK56oZ6dANHhKWbM2N7zcMGH7cLdzHLtLSG2Cc/94u5m3Q PDPcS0s2gYyNpCqo29YZuO5v3YI2yqRLNKfBIxNy4i1VlRXgny/IsrsH0so9rVH6rDDF /OGqy1LE1m+hBoCfrWMPh/DeaqW39G+AYoW8SO328BI6isGShA7fRkIQUX/9fTDY8sjD VawQ== X-Gm-Message-State: ABUngvfgbUB04kfIIxS0XMtBbGvj+0r+gbLbhmcN0sH1CIhk7t/EhRpjdPbD6Jj+f1UvSxqh X-Received: by 10.31.242.74 with SMTP id q71mr897899vkh.46.1478261554354; Fri, 04 Nov 2016 05:12:34 -0700 (PDT) Subject: Re: Building cross-toolchain for microblaze To: libc-alpha@sourceware.org References: From: Adhemerval Zanella Message-ID: Date: Fri, 04 Nov 2016 12:12:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-SW-Source: 2016-11/txt/msg00147.txt.bz2 On 04/11/2016 00:48, Joseph Myers wrote: > Continuing the issues shown up by writing a script to build glibc for all > ABIs, I find that MicroBlaze glibc does not build using the final compiler > because MicroBlaze GCC always uses SJLJ exceptions (see > gcc/common/config/microblaze/microblaze-common.c defining > TARGET_EXCEPT_UNWIND_INFO to sjlj_except_unwind_info), which is not > supported in glibc, resulting in undefined references to _Unwind_SjLj_* > (glibc deliberately links with libgcc.a and *not* libgcc_eh.a and gets EH > functionality via loading libgcc_s as needed, which is not implemented for > the SJLJ case; in the static-only case there isn't a separate libgcc_eh so > a build with the initial static-only compiler works accidentally). > > How is building MicroBlaze glibc meant to work? Is there some GCC patch > missing upstream to use DWARF2 exceptions? > I could build a workable toolchain, at least for glibc building, by configuring GCC with both '--disable-sjlj-exceptions' and '--disable-shared'. I did not dig into the issue, but it was already reported on maillist this same issue.