From: LIU Hao <lh_mouse@126.com>
To: Dave Blanchard <dave@killthe.net>, gcc@gcc.gnu.org
Subject: Re: Please, really, make `-masm=intel` the default for x86
Date: Fri, 25 Nov 2022 16:03:56 +0800 [thread overview]
Message-ID: <d5f67737-d91d-883b-b479-5db42adb1361@126.com> (raw)
In-Reply-To: <20221125014822.563a07773cdc2a33b4c872b7@killthe.net>
[-- Attachment #1.1: Type: text/plain, Size: 869 bytes --]
在 2022/11/25 15:48, Dave Blanchard 写道:
> While I sympathize with the desire to get rid of crud (and I agree that AT&T syntax is crud), as stated above it wouldn't really make a practical difference. For distro maintainers it would likely break some/many older packages which assumed the old default behavior, thus requiring a number of patches. Usually not a big deal in and of itself (though it can be if the build system for that package is particularly junky), but when you consider there are so many packages including GCC always deprecating and changing things, it adds up to a lot of work to keep up with it all.
>
I hope that, if we decide to make Intel syntax the default since GCC 14, then such crud will be
eventually got rid of since GCC 24. OTOH, if we don't do that, we would have to live with it forever.
--
Best regards,
LIU Hao
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next prev parent reply other threads:[~2022-11-25 8:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-25 7:48 Dave Blanchard
2022-11-25 8:03 ` LIU Hao [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-11-25 6:39 LIU Hao
2022-11-25 7:37 ` Hi-Angel
2022-11-25 7:56 ` LIU Hao
2022-11-25 8:50 ` Marc Glisse
2022-11-25 9:11 ` LIU Hao
2022-11-25 9:30 ` Jonathan Wakely
2022-11-25 9:56 ` Iain Sandoe
2022-11-25 9:32 ` Jakub Jelinek
2022-11-25 12:01 ` LIU Hao
2022-11-25 13:00 ` Richard Biener
2022-11-25 13:31 ` David Brown
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=d5f67737-d91d-883b-b479-5db42adb1361@126.com \
--to=lh_mouse@126.com \
--cc=dave@killthe.net \
--cc=gcc@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).