From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <gentoo-dev+bounces-85926-garchives=archives.gentoo.org@lists.gentoo.org> Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 0AEE3138334 for <garchives@archives.gentoo.org>; Thu, 13 Sep 2018 15:56:33 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id C5AB9E0E14; Thu, 13 Sep 2018 15:56:29 +0000 (UTC) Received: from mail-oi0-f68.google.com (mail-oi0-f68.google.com [209.85.218.68]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 79611E0E03 for <gentoo-dev@lists.gentoo.org>; Thu, 13 Sep 2018 15:56:29 +0000 (UTC) Received: by mail-oi0-f68.google.com with SMTP id y207-v6so9856730oie.13 for <gentoo-dev@lists.gentoo.org>; Thu, 13 Sep 2018 08:56:29 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=yfocOnXMWnK+n86AANlisnTAwdUjcAeYkXYP7EG6GzU=; b=RHrZFiHzpE7x+xehrpK0EvUcUKNUrU+9LWRn9cXOj+uIYjsyz+Z8kVvbffwbs5wUd/ h9s0ksSSkbFMNGp0sedbDYazCJ4rkQASFKRJaCsCDfz3DYBowZjjo4GQ/kvgQYpCgs3h pOmcuBspQNeUz1AP+/8nGkCH7FWDsYqbEreKEX8FOxgAraMQhibtXWiuJ63itELvQ9s7 PFXJyGgToqGR6GEtlhaCA3qlQbSxJnWo/p8C/oN7d5Mqb9GW3wfODAUeq3xTglFDxZ7i N+4K+ZALz08T9nsx+D1TtXzxX+MZwMVWU6xc1yCTJsXi+lU+6IfgBF2PLoJCJFSg7u8I 5WdA== X-Gm-Message-State: APzg51BZDEi4XZqG0pgmtQKZqYJ4gfOWaGPTy5U/r2s3f8hGaDwcsssK O2/luUzCOYYnhOmxTt4dg9d8EKB+gQi1egnuA075Ew== X-Google-Smtp-Source: ANB0VdZxX0i2eoGnH6FrZdYeYo5HdN0ld2Btlek6rKMNa037l2gDgnnpT/x/YFCGDWjvcpVAynhFaRy97D6nPLF75/Y= X-Received: by 2002:aca:b985:: with SMTP id j127-v6mr6513876oif.257.1536854187548; Thu, 13 Sep 2018 08:56:27 -0700 (PDT) Precedence: bulk List-Post: <mailto:gentoo-dev@lists.gentoo.org> List-Help: <mailto:gentoo-dev+help@lists.gentoo.org> List-Unsubscribe: <mailto:gentoo-dev+unsubscribe@lists.gentoo.org> List-Subscribe: <mailto:gentoo-dev+subscribe@lists.gentoo.org> List-Id: Gentoo Linux mail <gentoo-dev.gentoo.org> X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 References: <20180910074539.GA6512@baraddur.perfinion.com> <0d8b7f02-9c38-969c-413b-69d4dee6ca89@gentoo.org> <CAEdQ38GfSjoKmn2jZgA-j8dxXESxe_hxu-bovSKgo6yonrR9bQ@mail.gmail.com> <20180912085649.GA16516@baraddur.perfinion.com> <CAGfcS_kXsZdQkWTVHCaZK-CzU0E5N64neUF04Hcc6O7v7=qP1A@mail.gmail.com> <6c18c6bd-4cf3-dff6-2f20-c021063e01fa@gentoo.org> <CAGfcS_mi=ScuSrMO52urz779jCBdTUp1qSxw3L+dtnk5-ou_Dw@mail.gmail.com> <CAEdQ38FBnSz-zdUw+iiysFX5qjRj6sxY7nMEQHh+qzJeqHdMug@mail.gmail.com> <CAGfcS_naAd3qShZf1mgjH_b-PBv1n=Q9asXrEaatvHx4fgk6ig@mail.gmail.com> <CAEdQ38Gdzqe6YMxW168w8rxtN6b5b02N5L+8bv78W=OTXtPB8Q@mail.gmail.com> <20180913155123.GB26329@gentoo.org> In-Reply-To: <20180913155123.GB26329@gentoo.org> From: Alon Bar-Lev <alonbl@gentoo.org> Date: Thu, 13 Sep 2018 18:56:13 +0300 Message-ID: <CAOazyz3Vc2asCupLiWLJbHT+Nz57qmNERAXX=fTSKRY9i3RgGg@mail.gmail.com> Subject: Re: [gentoo-dev] Changing policy about -Werror To: gentoo-dev@lists.gentoo.org Content-Type: text/plain; charset="UTF-8" X-Archives-Salt: 992aa8a3-6a75-441a-a700-64623f5bbf0a X-Archives-Hash: 221f636bbc2edfd3bcd151aac2edd831 On Thu, Sep 13, 2018 at 6:51 PM Fabian Groffen <grobian@gentoo.org> wrote: > > On 12-09-2018 17:46:03 -0700, Matt Turner wrote: > > On Wed, Sep 12, 2018 at 5:11 PM Rich Freeman <rich0@gentoo.org> wrote: > > With new GCC comes new warnings, and harmless as the vast majority are > > they cause the build to break with Werror. > > To illustrate harmless: > warning: this statement may fall through [-Wimplicit-fallthrough=] > The warning message already has it in it that it's just a pure guess. One that exposed a lot of unintentional fallthoughs which were fixed when reporting to upstream. Once again... we should discuss to leave -Werror when policy of upstream to have no warnings and is maintaining that policy properly while we at downstream may cooperate and avoid patching upstream but discuss issues when found.