From: Jan Beulich <jbeulich@suse.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: binutils@sourceware.org, Michael Matz <matz@suse.de>
Subject: Re: [PATCH] x86: Warn .insn instruction with length > 15 bytes
Date: Tue, 6 Feb 2024 18:05:24 +0100 [thread overview]
Message-ID: <d4c4a7fa-5c9d-4e4b-a998-c3c34a036659@suse.com> (raw)
In-Reply-To: <CAMe9rOroVHznT1dURbbAbTCWGGw9V28fHBie_4wBPDDH0gRXjw@mail.gmail.com>
On 06.02.2024 17:28, H.J. Lu wrote:
> With as_bad, assembler will continue to assemble, just not generate
> an object file. We ran into this with APX. Not everyone checks
> assembler warnings closely. It led to mysterious crashes. I am
> not against it if someone else implements an assembler option to
> turn this error into a warning.
But it should be the other way around: The compiler could pass an
option to promote the (default) warning to an error. And if you
don#t pay attention to warning for assembly files, you could pass
the same option as well. Without harming anyone else with anything
that has worked before.
Jan
next prev parent reply other threads:[~2024-02-06 17:05 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-05 20:00 H.J. Lu
2024-02-06 8:19 ` Jan Beulich
2024-02-06 11:36 ` H.J. Lu
2024-02-06 11:41 ` Jan Beulich
2024-02-06 12:26 ` H.J. Lu
2024-02-06 14:43 ` Michael Matz
2024-02-06 14:49 ` H.J. Lu
2024-02-06 15:04 ` Michael Matz
2024-02-06 15:34 ` H.J. Lu
2024-02-06 15:48 ` Michael Matz
2024-02-06 16:28 ` H.J. Lu
2024-02-06 17:05 ` Jan Beulich [this message]
2024-02-06 18:06 ` H.J. Lu
2024-02-07 7:51 ` Jan Beulich
2024-02-07 15:24 ` H.J. Lu
2024-02-07 15:32 ` Jan Beulich
2024-02-07 16:53 ` H.J. Lu
2024-02-07 16:59 ` Jan Beulich
2024-02-07 17:03 ` H.J. Lu
2024-02-08 4:09 ` Jiang, Haochen
2024-02-08 4:47 ` Hongyu Wang
2024-02-08 8:15 ` Jan Beulich
2024-02-08 8:23 ` Jan Beulich
2024-02-08 11:38 ` H.J. Lu
2024-02-08 6:26 ` Sunil Pandey
2024-02-08 6:41 ` Cui, Lili
2024-02-08 8:18 ` Jan Beulich
2024-02-08 11:31 ` H.J. Lu
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=d4c4a7fa-5c9d-4e4b-a998-c3c34a036659@suse.com \
--to=jbeulich@suse.com \
--cc=binutils@sourceware.org \
--cc=hjl.tools@gmail.com \
--cc=matz@suse.de \
/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).