all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: 70822@debbugs.gnu.org
Subject: bug#70822: flymake mishandles GCC diagnostics in en_US.UTF-8 locale
Date: Tue, 7 May 2024 10:06:59 -0700	[thread overview]
Message-ID: <bf6871f3-a35f-4622-83e0-541995372510@cs.ucla.edu> (raw)

In the en_US.UTF-8 locale on Fedora 40, (GCC) 14.0.1 20240411 (Red Hat 
14.0.1-0) uses curved single quotes ‘like this’. This causes Emacs ‘make 
check’ to fail in the flymake tests.

For example, in the C locale 'gcc 
test/lisp/progmodes/flymake-resources/some-problems.h' outputs this:

   test/lisp/progmodes/flymake-resources/some-problems.h:3:1: warning: 
data definition has no type or storage class
       3 | strange;
         | ^~~~~~~
   test/lisp/progmodes/flymake-resources/some-problems.h:3:1: warning: 
type defaults to 'int' in declaration of 'strange' [-Wimplicit-int]
   test/lisp/progmodes/flymake-resources/some-problems.h:7:1: error: 
unknown type name 'sint'; did you mean 'int'?
       7 | sint main();
         | ^~~~
         | int

whereas in the en_US.UTF-8 locale the same command outputs this instead:

   test/lisp/progmodes/flymake-resources/some-problems.h:3:1: warning: 
data definition has no type or storage class
       3 | strange;
         | ^~~~~~~
   test/lisp/progmodes/flymake-resources/some-problems.h:3:1: error: 
type defaults to ‘int’ in declaration of ‘strange’ [-Wimplicit-int]
   test/lisp/progmodes/flymake-resources/some-problems.h:7:1: error: 
unknown type name ‘sint’; did you mean ‘int’?
       7 | sint main();
         | ^~~~
         | int

and flymake mishandles the latter set of diagnostics.





             reply	other threads:[~2024-05-07 17:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-07 17:06 Paul Eggert [this message]
2024-05-08 13:05 ` bug#70822: flymake mishandles GCC diagnostics in en_US.UTF-8 locale Eli Zaretskii
2024-05-08 17:10   ` Paul Eggert
2024-05-08 18:38     ` Eli Zaretskii

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=bf6871f3-a35f-4622-83e0-541995372510@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=70822@debbugs.gnu.org \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.