From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 67048 invoked by alias); 4 Jan 2020 02:23:12 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 67025 invoked by uid 89); 4 Jan 2020 02:23:12 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-3.2 required=5.0 tests=AWL,BAYES_00,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,GIT_PATCH_2,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.1 spammy=yield, Best, our, H*r:2002 X-HELO: mail-il1-f194.google.com Received: from mail-il1-f194.google.com (HELO mail-il1-f194.google.com) (209.85.166.194) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sat, 04 Jan 2020 02:23:11 +0000 Received: by mail-il1-f194.google.com with SMTP id b15so38159316iln.3 for ; Fri, 03 Jan 2020 18:23:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=2qNCKujq6nDDNfWA3TXbvydYhWatwDvLFFyQldIa7hQ=; b=Ix75JZ7iOweb2pZ2HDtny5hY6zdUoGCg6YT8hZJjeWNCM7ir9P7p6Pqummb6A/UqMe dUYMNij5hhnuUhbz8Gn9Oke0dXTuB48Z45/rYm74AsZjVSIdajoMNkyBz9+wBgR2AgH5 SVHiYbhoLIAIY+CB35Ff4HHlONkAeWRn/nVam5dkc0m1TBaiy71NGsVYxDXHBJuvgq34 WBqAB69wmmx6ZY2kxrwSZIflj5VL/jHUFsxbiyPPBuTpyJnl2KgRnjM0YK47Mx1pGLZz J5OEeYr+fc/15QEktyojQnAeL2W+Ae9D0HCtmWC7Ua3jHAWDSP3i6gMp+m6sO+xiXWxZ Hofg== MIME-Version: 1.0 Received: by 2002:a6b:da16:0:0:0:0:0 with HTTP; Fri, 3 Jan 2020 18:23:09 -0800 (PST) In-Reply-To: References: From: Eric Curtin Date: Sat, 04 Jan 2020 02:23:00 -0000 Message-ID: Subject: Re: Could I obtain the forms needed to make a contribution? To: Dmitry Grinberg Cc: gcc@gcc.gnu.org Content-Type: text/plain; charset="UTF-8" X-SW-Source: 2020-01/txt/msg00019.txt.bz2 Hi Guys, Sorry I switched off the email for the holidays. I guess the problem with the linker error is, we have a distributed build system with the linking occurring at the very end of the build (we have a slow build, that's a different problem though). So it's compile time that this would be preferable like -Wdate-time does. Would introducing a new warning be the only way to achieve this? Other than the clever linker way below? On 19/12/2019, Dmitry Grinberg wrote: > Why not just add "-D__LINE__=LinkerError_LineMacroUsed_DoNotDoThat()" to > CFLAGS? > > ---- > Best Regards, > Dmitry Grinberg > > > On Mon, Dec 16, 2019 at 3:51 AM Eric Curtin wrote: > >> I want to add a compiler warning, if it will get accepted. It's a >> -Wlines warning. My employer bans the __LINE__ macro as well as the >> ones warned by the -Wdate-time warning, because there is a consensus >> that the addition of whitespace or comments should not yield different >> binary output for our project. Would this patch get accepted? >> >