From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id C06DB3945C23; Wed, 8 Apr 2020 20:48:31 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C06DB3945C23 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1586378911; bh=xX/BPvCOZWTDdaKR6QAbkLummAPS0+ZGMEplQ0qJIoY=; h=From:To:Subject:Date:In-Reply-To:References:From; b=clLJ8LEEUhLvDiPMi3wqR/y/Amj6mYXGX29B2n+frwKa++M2UauwdNPIaMiRS8jsN x8HfjcfK6enGz4Jp1ADv6+UHfgUu0gcZYcS6mBDkV85VkDeZbokHQcMReos26ND3e4 2JOk/v3bkaZz8w1szl1uj6KwvkaWb2g944SdabCI= From: "pinskia at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug preprocessor/94535] __LINE__ value changed for function-like macro invocations spanning multiple lines Date: Wed, 08 Apr 2020 20:48:31 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: preprocessor X-Bugzilla-Version: 9.1.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: pinskia at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: gcc-bugs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-bugs mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Apr 2020 20:48:31 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D94535 --- Comment #3 from Andrew Pinski --- >There is no multiline "macro function" here, there is an invocation of a m= acro, and the invocation spans multiple lines.=20 I miss-remembered the issue, the issue was only with preprocessor directives inside macro functions (this changed in GCC 3.3 and above really). But I still think both line #s are correct. is the line at the opening of = the macro function or the closing?=