From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 106363 invoked by alias); 14 Jun 2017 09:07:02 -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 106351 invoked by uid 89); 14 Jun 2017 09:07:01 -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. X-HELO: mail-io0-f173.google.com Received: from mail-io0-f173.google.com (HELO mail-io0-f173.google.com) (209.85.223.173) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 14 Jun 2017 09:07:00 +0000 Received: by mail-io0-f173.google.com with SMTP id y77so88787026ioe.3 for ; Wed, 14 Jun 2017 02:07:04 -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=b/diq/fWKN0IcafO4jxQDtDOuf3HLHnCXHPIDX+fqOE=; b=l4WZiDKBDGCoIgzkauZzJe4KhtBysftyGWNGnkNiuBsO/x68prwtMcUI9yy13/0yqL r1TFE7oZXuLP/7PI967OGHBDybZGHSahXpz7sIQ6LU7NpWnx476iTXzP2WzBH93JhDV5 3RpqlufJB+Vuwj2u0nMhvOGiAFFGepJMjSP/82aevvV27fmEQ6+HcKoT4jEIRopTCpVn c/Vx0MXggwsPy6p0R6KBCLVIzd8BMqcXeY1em/HwIOiMj9bL4q3Mj9R1Sx5DxJT2wIwh ivYKRQq+prC/UTzQNpc3NSE4sjNFhZ3AI23eXqE7AvZoybxSKP20NfYVGgILASS46+XA g5hw== X-Gm-Message-State: AKS2vOx+13cwzlz3kycW6WDb4gJTasWscD9TKluTeIMykF2detisCQMj tfixBHmASJm/mA== X-Received: by 10.107.12.28 with SMTP id w28mr5151463ioi.170.1497431223451; Wed, 14 Jun 2017 02:07:03 -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 n3sm1900551itg.3.2017.06.14.02.07.01 (version=TLS1_2 cipher=AES128-SHA bits=128/128); Wed, 14 Jun 2017 02:07:02 -0700 (PDT) From: Yao Qi To: Eli Zaretskii Cc: simon.marchi@ericsson.com, gdb-patches@sourceware.org, palves@redhat.com 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> <8660g0dzau.fsf@gmail.com> <86o9trdib1.fsf@gmail.com> <83d1a751us.fsf@gnu.org> Date: Wed, 14 Jun 2017 09:07:00 -0000 In-Reply-To: <83d1a751us.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 13 Jun 2017 18:44:27 +0300") Message-ID: <86bmprvsy6.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/msg00417.txt.bz2 Eli Zaretskii writes: > Specifically, this text sounds too vague to me to be considered > "policy". Too much is left to judgment calls. But if everyone else > is happy, I won't insist on prolonging this discussion. > It is vague because the tasks this "policy" about are not clear. It is unlike other polices like "-Werror policy" or "GDB's #include file policy", their tasks are quite clear, so it is possible to give clear actionable rules. However, it is still unknown that what are we going to do to make GDB built with compilers other than GCC. It was just raised by Simon's patches several days ago. We need to write this vague policy down, and don't discourage people building GDB with different compilers. Patches are still reviewed, and some of them may be controversial. As we have some concrete bad/good patches, we can have some specific rules in this policy. >> I also looked for the place to add this policy. Looks the most relevant >> page is https://sourceware.org/gdb/wiki/Internals%20Compiler-Warnings > > I would suggest to consider a new page, or maybe make this part of > coding standards. OK, let me create a new page, "Build GDB with different compilers" in chapter "Miscellaneous guidelines" in=20 https://sourceware.org/gdb/wiki/Internals It has few to do with coding standards. People should still write the code in the same way, specified in our coding standards, although GDB can be built by different compilers. --=20 Yao (=E9=BD=90=E5=B0=A7)