From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18958 invoked by alias); 13 Jun 2017 09:14:51 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 18936 invoked by uid 89); 13 Jun 2017 09:14:50 -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,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=H*r:sk:static., policy X-HELO: mail-it0-f67.google.com Received: from mail-it0-f67.google.com (HELO mail-it0-f67.google.com) (209.85.214.67) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 13 Jun 2017 09:14:49 +0000 Received: by mail-it0-f67.google.com with SMTP id l6so13565967iti.0 for ; Tue, 13 Jun 2017 02:14:53 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:references:date:in-reply-to :message-id:user-agent:mime-version:content-transfer-encoding; bh=Oa9ugTTc8ofxvRnvx+w68+dDH/hVG1J3msG1U7Cmkno=; b=qb3phkM641j8Ijw7qrxydpZ+KuudqgrBxIj3ANpa4dX6tlHnCGC6jMe+9+E2zz3YGk 859ylTt1cGypxiWGeft1JTm3BNF2IK1Ypk+e9PM8zZPqO/Bq/mxVQD+Pot/9/NP9TYAg E11jt8bVPElY8Vc7MDCw14EmpP+Nd9kNtVkH5QVMVOaxlwjy1Tut9rYnX3Hq8fpwU1VW WWa3CPvAacoS20ZKWDgUP1Xw1QfX8mmadqOkjqULels6PaO2vb3tAQzzaHyN8O5MvD+/ B2rbsyh5HjKdzqe3Zs+yTJzWweSv7G0cnOpBcoNrLyAXDRGSj7QAUkPO6Z5TiL2SNSmM tKhQ== X-Gm-Message-State: AODbwcBHH9itv7Xp2PSwnmbj6+L68t+F5kJF6N/hoe4LMbHlVxowk70P 9QLAyr2Wqr8nKFyh X-Received: by 10.36.69.225 with SMTP id c94mr16697441itd.15.1497345292218; Tue, 13 Jun 2017 02:14:52 -0700 (PDT) Received: from E107787-LIN (static.42.136.251.148.clients.your-server.de. [148.251.136.42]) by smtp.gmail.com with ESMTPSA id q83sm4180870ioi.52.2017.06.13.02.14.50 (version=TLS1_2 cipher=AES128-SHA bits=128/128); Tue, 13 Jun 2017 02:14:51 -0700 (PDT) From: Yao Qi To: Eli Zaretskii Cc: Simon Marchi , gdb-patches@sourceware.org Subject: Re: [PATCH 0/5] Remove a few hurdles of compiling with clang References: <1497124689-11842-1-git-send-email-simon.marchi@ericsson.com> <83tw3n5jyk.fsf@gnu.org> <86tw3labb0.fsf@gmail.com> <83a85d5l4n.fsf@gnu.org> <93eb64489ac9d53665a144ddf5a966d5@polymtl.ca> <83wp8h40lo.fsf@gnu.org> Date: Tue, 13 Jun 2017 09:14:00 -0000 In-Reply-To: <83wp8h40lo.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 12 Jun 2017 19:44:35 +0300") Message-ID: <8660g0dzau.fsf@gmail.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes X-SW-Source: 2017-06/txt/msg00359.txt.bz2 Eli Zaretskii writes: > That's precisely the reason why I raised this: it would be good to > have a clear policy on this, to avoid the need for unnecessary work > and unnecessary disputes. (I actually hoped we already did have such > a policy, but if not, I think we should try to come up with it.) In general, it is good to keep GDB built by different popular compilers, so people are easy to build GDB and different warnings from different compilers will catch more bugs in GDB. On the other hand, GCC is still the primary compiler to build GDB, and support of other compilers in building GDB should not undermine the case that GDB is built by GCC. For example, it is not acceptable to build GDB with compiler X but break the build with GCC. We still must fix the GDB build failure with GCC, as what we did in the past, and we welcome the contributions to fix the GDB build with other compilers. --=20 Yao (=E9=BD=90=E5=B0=A7)