From: "Óscar Fuentes" <ofv@wanadoo.es>
To: Po Lu <luangruo@yahoo.com>
Cc: 53377@debbugs.gnu.org
Subject: bug#53377: 28.0.91: Build fails on MSYS2/MinGW-w64 with Clang
Date: Thu, 20 Jan 2022 04:59:55 +0100 [thread overview]
Message-ID: <87r1936oqs.fsf@telefonica.net> (raw)
In-Reply-To: <87ee532hwu.fsf@yahoo.com> (Po Lu's message of "Thu, 20 Jan 2022 11:41:05 +0800")
Po Lu <luangruo@yahoo.com> writes:
> Óscar Fuentes <ofv@wanadoo.es> writes:
>
>> Your information is outdated. The only clear advantage GCC has over
>> Clang is at being compatible with GCC.
>
> The last I tried, I could not even step through Clang-generated code
> with GDB on MS-Windows. The line numbers were all wrong. Admittedly
> that was 4 months ago, but I don't see that it's likely for much to have
> changed since then.
Dunno, I use a debugger maybe once every several months, mostly on
GNU/Linux, where recent versions of Clang play reasonably well with gdb,
or at least not much worse than GCC. Besides, Clang has its own
debugger.
> So this is why I think we shouldn't worry about building on Windows with
> Clang. There are enough real problems to worry about.
Then, by all means, keep working on those "real" problems and ignore
this issue. But please don't try to discourage others from working on
this.
next prev parent reply other threads:[~2022-01-20 3:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-19 23:41 bug#53377: 28.0.91: Build fails on MSYS2/MinGW-w64 with Clang Óscar Fuentes
2022-01-20 1:14 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-20 3:32 ` Óscar Fuentes
2022-01-20 3:41 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-20 3:59 ` Óscar Fuentes [this message]
2022-01-20 4:52 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-20 7:54 ` Eli Zaretskii
2022-01-20 7:40 ` Eli Zaretskii
2022-01-21 4:14 ` Richard Stallman
2022-01-20 7:33 ` 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=87r1936oqs.fsf@telefonica.net \
--to=ofv@wanadoo.es \
--cc=53377@debbugs.gnu.org \
--cc=luangruo@yahoo.com \
/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.