From: Segher Boessenkool <segher@kernel.crashing.org>
To: Zopolis0 <creatorsmithmdt@gmail.com>
Cc: Xi Ruoyao <xry111@mengyan1223.wang>, gcc-help@gcc.gnu.org
Subject: Re: Multiple descriptions for fassert in gcc/d/lang.opt and gcc/java/lang.opt
Date: Wed, 30 Mar 2022 07:00:38 -0500 [thread overview]
Message-ID: <20220330120038.GT614@gate.crashing.org> (raw)
In-Reply-To: <CAEYL+X8p0xBHYQv=kRygo+vqY9aF+rZ=U+53Y0xZmma=+sqS8w@mail.gmail.com>
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
prev parent reply other threads:[~2022-03-30 12:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-29 8:11 Zopolis0
2022-03-29 15:41 ` Xi Ruoyao
2022-03-30 9:32 ` Zopolis0
2022-03-30 12:00 ` Segher Boessenkool [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220330120038.GT614@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=creatorsmithmdt@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=xry111@mengyan1223.wang \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).