From: Segher Boessenkool <segher@kernel.crashing.org>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Gaius Mulley <gaius.mulley@southwales.ac.uk>,
Matthias Klose <doko@ubuntu.com>,
gcc-patches@gcc.gnu.org, Richard Biener <rguenther@suse.de>,
dje.gcc@gmail.com
Subject: Re: [PATCH] Modula-2 into the GCC tree on master
Date: Wed, 23 Jun 2021 11:34:02 -0500 [thread overview]
Message-ID: <20210623163402.GF5077@gate.crashing.org> (raw)
In-Reply-To: <20210621224127.GZ7746@tucnak>
On Tue, Jun 22, 2021 at 12:41:27AM +0200, Jakub Jelinek wrote:
> On Mon, Jun 21, 2021 at 11:36:48PM +0100, Gaius Mulley via Gcc-patches wrote:
> > > <built-in>: error: the file containing the definition module <E2><80><98>M2RTS
> > > <E2><80><99> cannot be found
> > > compiler exited with status 1
> > > output is:
> > > <built-in>: error: the file containing the definition module <E2><80><98>M2RTS
> > > <E2><80><99> cannot be found
> >
> > ah yes, it would be good to make it autoconf locale utf-8
>
> No, whether gcc is configured on an UTF-8 capable terminal or using UTF-8
> locale doesn't imply whether it will actually be used in such a terminal
> later on.
> See e.g. gcc/intl.c (gcc_init_libintl) how it decides whether to use UTF-8
> or normal quotes.
Right, and I build and regcheck GCC with LANG=C (and no LC_*) so I
should never see anything translated at all, and nothing should generate
UTF-8 for me.
Segher
next prev parent reply other threads:[~2021-06-23 16:35 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-17 22:26 Gaius Mulley
2021-06-18 10:19 ` Matthias Klose
2021-06-18 21:14 ` Gaius Mulley
2021-06-19 7:53 ` Gaius Mulley
2021-06-19 10:32 ` Matthias Klose
2021-06-18 10:52 ` Richard Biener
2021-06-18 12:50 ` Segher Boessenkool
2021-06-18 15:10 ` Gaius Mulley
2021-06-18 12:32 ` Segher Boessenkool
2021-06-18 21:00 ` Gaius Mulley
2021-06-19 14:09 ` Segher Boessenkool
2021-06-19 16:06 ` Segher Boessenkool
2021-06-21 22:36 ` Gaius Mulley
2021-06-21 22:41 ` Jakub Jelinek
2021-06-22 22:29 ` Gaius Mulley
2021-06-23 16:34 ` Segher Boessenkool [this message]
2021-06-20 11:57 ` Gaius Mulley
2021-06-21 11:20 ` Gaius Mulley
-- strict thread matches above, loose matches on Subject: below --
2021-01-18 1:09 Gaius Mulley
2021-01-18 10:19 ` Richard Biener
2021-01-18 13:55 ` Gaius Mulley
2021-05-27 12:02 ` Matthias Klose
2021-05-27 14:00 ` Gaius Mulley
2021-06-10 15:00 ` Gaius Mulley
2021-01-18 12:26 ` Matthias Klose
2021-01-18 19:16 ` Gaius Mulley
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=20210623163402.GF5077@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=dje.gcc@gmail.com \
--cc=doko@ubuntu.com \
--cc=gaius.mulley@southwales.ac.uk \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=rguenther@suse.de \
/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).