public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "eric.pouech at orange dot fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/104399] Mingw to generate bogus.o on French locale
Date: Sun, 06 Feb 2022 08:33:37 +0000 [thread overview]
Message-ID: <bug-104399-4-RBXdRHLAUV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104399-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104399
--- Comment #2 from eric.pouech at orange dot fr ---
output of compiling with -save-temp
generating the good.s, good-eng.s and fail.s (with same naming conventions as
in #1)
[eric]$ diff good.s good-eng.s
7812c7812
< .ascii "Unknown PCI vendor ID 0x%04x.\12\0"
---
> .ascii "Unknown PCI vendor ID 0x%04lx.\12\0"
adding the letter to the string (only diff of two .s files)
[eric]$ diff fail.s good-eng.s
no difference shown...
opening the issue with binutils then
--------------
(for the record the compiler invocation)
i686-w64-mingw32-gcc -c -o dlls/dxdiagn/container.cross.o
/home/eric/work/wine-format/dlls/dxdiagn/container.c -Idlls/dxdiagn \
-I/home/eric/work/wine-format/dlls/dxdiagn -Iinclude
-I/home/eric/work/wine-format/include \
-I/home/eric/work/wine-format/include/msvcrt -D__WINESRC__ -D_UCRT
-D__WINE_PE_BUILD -Wall \
-fno-strict-aliasing -Wdeclaration-after-statement -Wempty-body
-Wignored-qualifiers -Winit-self \
-Wno-packed-not-aligned -Wshift-overflow=2 -Wstrict-prototypes -Wtype-limits
\
-Wunused-but-set-parameter -Wvla -Wwrite-strings -Wpointer-arith -Wlogical-op
-Wabsolute-value \
-fno-omit-frame-pointer -gdwarf-4 -g -O2
next prev parent reply other threads:[~2022-02-06 8:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-05 17:52 [Bug c/104399] New: " eric.pouech at orange dot fr
2022-02-05 19:21 ` [Bug c/104399] " pinskia at gcc dot gnu.org
2022-02-06 8:33 ` eric.pouech at orange dot fr [this message]
2022-02-06 11:21 ` [Bug middle-end/104399] " eric.pouech at orange dot fr
2022-02-06 19:58 ` pinskia at gcc dot gnu.org
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=bug-104399-4-RBXdRHLAUV@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.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.
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).