From: Paul Koning <paulkoning@comcast.net>
To: Jan Beulich <jbeulich@suse.com>
Cc: jacob navia <jacob@jacob.remcomp.fr>, binutils@sourceware.org
Subject: Re: P.S. Follow up to my last post
Date: Fri, 25 Aug 2023 09:40:24 -0400 [thread overview]
Message-ID: <E981B0F2-F141-4079-8C20-CC8F52FDAE5A@comcast.net> (raw)
In-Reply-To: <60877e9d-f6b1-a319-2383-0a87c980aea8@suse.com>
> On Aug 25, 2023, at 9:30 AM, Jan Beulich via Binutils <binutils@sourceware.org> wrote:
>
> On 25.08.2023 15:07, jacob navia wrote:
>> OK, there is no bug, I didn’t expect anything else.
>>
>> SO:
>>
>> To use all the instruction of the processor he/she is running on, the user should:
>>
>> 1)Be aware that gcc doesn’t see crucial instructions of the processor by verifying its assembler output.
>>
>> 2) Be aware that there is an (undocumented) option -march… that will enable the assembler and the compiler to generate all the instructions of the current processor.
>>
>> Well, there is NO BUG!
>
> Well, if -march= is indeed undocumented for gcc, that's something
> worth reporting there then, I would say.
It would be if it were true, but of course it is not. -march is clearly mentioned in the info pages, the man pages, and in "gcc --target-help". Likewise, it is documented in the info pages, man pages, and "as --help".
paul
next prev parent reply other threads:[~2023-08-25 13:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-25 11:52 jacob navia
2023-08-25 12:00 ` Jan Beulich
2023-08-25 13:07 ` jacob navia
2023-08-25 13:30 ` Jan Beulich
2023-08-25 13:40 ` Paul Koning [this message]
[not found] <AEF14E89-14CF-4474-8822-B0139F3F740B@jacob.remcomp.fr>
2023-08-25 15:32 ` Palmer Dabbelt
2023-08-25 16:10 ` jacob navia
2023-08-25 17:03 ` Paul Koning
2023-08-25 19:44 ` jacob navia
2023-08-28 6:17 ` Jan Beulich
2023-08-28 7:04 ` jacob navia
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=E981B0F2-F141-4079-8C20-CC8F52FDAE5A@comcast.net \
--to=paulkoning@comcast.net \
--cc=binutils@sourceware.org \
--cc=jacob@jacob.remcomp.fr \
--cc=jbeulich@suse.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.
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).