From owner-freebsd-toolchain@freebsd.org Fri Aug 25 18:30:12 2017 Return-Path: Delivered-To: freebsd-toolchain@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A34FBDDE974 for ; Fri, 25 Aug 2017 18:30:12 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x233.google.com (mail-io0-x233.google.com [IPv6:2607:f8b0:4001:c06::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 68E906B9E6 for ; Fri, 25 Aug 2017 18:30:12 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x233.google.com with SMTP id c18so2090847ioj.1 for ; Fri, 25 Aug 2017 11:30:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=AlFcnb+2+qxCj6q2XpwRWtNEQqKP5/gDkzQqvA4MBeY=; b=qeA3s+egf0RBj1U4qqocdoHH+YSgZRdaBrtiswPLJhu/OVKVRcc4ioQ99oLBKIlAji QsETTs5Sdx6FGyEKZw1L+ehxxK1c46AqST78lp5ZNdmM0uN7hBmzHCZEO1myNriDkTim ARn4H7Gmnkn1xbbZEnGh+K+AS/G4OwlUyNOAbKbvl0snMSRzy4xVdxt1bwyCnOy3e+fF R24rkZwGLV2F0KXuTVA/gpH8JwGY5oLKhAeMnJHchoIeuyHVGI2XQvn7TNtv2X9V1afJ YGjGCKPOyV7XlIETkMCrrhkhj8yG7AKk2ksp5CvYga94o9xt84PYMFjFS5WJEPVXgaNH so+A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=AlFcnb+2+qxCj6q2XpwRWtNEQqKP5/gDkzQqvA4MBeY=; b=rJagX5amY7RLYJptd9Z255/vvFQaTAAe1YcHTe6Nypw32wXYWwVjUu0GAav7GV68ab eQj8uruNiP0odXAMKNltOVkpgo1kYNFmqiyg2vPVvfk2iDvGhYsg3ewUHp6wUHy81DI5 VvwFZCMllvgwEDqLlT1b6z1cmvwYQCYacIjbGrj/kFlNNaAs6qtHlAGvzix7OiHuFwUM y2FViPiVfIBlssyXC6fd/eyW7InQPYmSEZ3+1FzD6AbfXqLRP+5ZmfIpoZFJPgVfvpyO WAJL4NCUBFxQ5R8+Homd+EqsC7QJ0gCdPl3pc0KaMHwdW23W3HB+eSX1WgZ7s6f0aOhv oE8Q== X-Gm-Message-State: AHYfb5j7aDfUqmiHSBgwQgYYN4CmqoTKo6lhxjijxhDdBrJK+2qZZ9vj Jwqv5EYcHBh0kX+XUmf9kN3C5K9gEBbO X-Received: by 10.107.17.19 with SMTP id z19mr9989886ioi.182.1503685811756; Fri, 25 Aug 2017 11:30:11 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.10.71 with HTTP; Fri, 25 Aug 2017 11:30:11 -0700 (PDT) X-Originating-IP: [50.253.99.174] In-Reply-To: References: <201708232330.v7NNUPpV052276@repo.freebsd.org> From: Warner Losh Date: Fri, 25 Aug 2017 12:30:11 -0600 X-Google-Sender-Auth: o-iwCwuRe80unh0TWMMrZZDAXZo Message-ID: Subject: Re: svn commit: r322824 - in head: lib/clang share/mk usr.bin/clang To: Ed Maste Cc: Ryan Libby , "svn-src-head@freebsd.org" , "svn-src-all@freebsd.org" , src-committers , John Baldwin , "freebsd-toolchain@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Aug 2017 18:30:12 -0000 On Fri, Aug 25, 2017 at 12:27 PM, Ed Maste wrote: > On 25 August 2017 at 14:07, Ryan Libby wrote: > > On Wed, Aug 23, 2017 at 4:30 PM, John Baldwin wrote: > >> Author: jhb > >> Date: Wed Aug 23 23:30:25 2017 > >> New Revision: 322824 > >> URL: https://svnweb.freebsd.org/changeset/base/322824 > >> > >> Log: > >> Improve the coverage of debug symbols for MK_DEBUG_FILES. > >> > ... > > This causes llvm to emit hundreds of new warnings [1] for > > "DWARF2 only supports one section per compilation unit" > > > > Are these expected? Are they a concern? Should we silence them? > > Is this an upstream llvm bug [2]? > > I'm not sure they were "expected" but I guess are an unsurprising > consequence of building more things with debug. In any case they're > not a concern. > > It is an llvm bug (the warning really ought not be emitted for empty > sections), but upstream is probably not too concerned as (most? all) > other platforms are not using dwarf2. > > The right answer for us is likely to just stop defaulting to dwarf2 > (and specifying it via CFLAGS for kernel if necessary). > What's the status of kicking gdb out of the tree? If we kick it out, we can stop doing dwarf2 and move to something more modern. Last time this issue came up, that was the decision, pending a few issues with the gdb port which I think John Baldwin is getting close to reaching closure on. Warner