From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate.crashing.org (gate.crashing.org [63.228.1.57]) by sourceware.org (Postfix) with ESMTP id F2F063858405 for ; Wed, 30 Mar 2022 12:01:39 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org F2F063858405 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=kernel.crashing.org Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=kernel.crashing.org Received: from gate.crashing.org (localhost.localdomain [127.0.0.1]) by gate.crashing.org (8.14.1/8.14.1) with ESMTP id 22UC0dJj018648; Wed, 30 Mar 2022 07:00:39 -0500 Received: (from segher@localhost) by gate.crashing.org (8.14.1/8.14.1/Submit) id 22UC0dN2018645; Wed, 30 Mar 2022 07:00:39 -0500 X-Authentication-Warning: gate.crashing.org: segher set sender to segher@kernel.crashing.org using -f Date: Wed, 30 Mar 2022 07:00:38 -0500 From: Segher Boessenkool To: Zopolis0 Cc: Xi Ruoyao , gcc-help@gcc.gnu.org Subject: Re: Multiple descriptions for fassert in gcc/d/lang.opt and gcc/java/lang.opt Message-ID: <20220330120038.GT614@gate.crashing.org> References: <12a5e21f1432b767709e423315fb8081e4e447bd.camel@mengyan1223.wang> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i X-Spam-Status: No, score=-3.2 required=5.0 tests=BAYES_00, JMQ_SPF_NEUTRAL, KAM_DMARC_STATUS, SPF_HELO_PASS, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: gcc-help@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-help mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Mar 2022 12:01:41 -0000 On Wed, Mar 30, 2022 at 08:32:04PM +1100, Zopolis0 via Gcc-help wrote: > I was asking in gcc-help because this isn't an error related to gcj > specifically, as it applies to any scenarios where there are multiple > definitions for the same thing in different lang.opt files. You can look at how d/lang.opt handles this for its conflicts with C. Warning: it is very underwhelming :-) It does require the documentation to be the same for both languages, which probably is a good idea anyway. Segher