From: Matt Whitlock <sourceware@mattwhitlock.name>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: <libc-alpha@sourceware.org>
Subject: Re: [PATCH] x86: fix Autoconf caching of instruction support checks [BZ #27991]
Date: Wed, 11 Aug 2021 16:16:54 -0400 [thread overview]
Message-ID: <2631fea6-3600-48d6-8220-ede71e2d2a27@mattwhitlock.name> (raw)
In-Reply-To: <fa1d55fb-889d-fda8-ad17-adf9250a0db4@linaro.org>
On Wednesday, August 11, 2021 12:44:09 PM EDT, Adhemerval Zanella wrote:
>
> On 17/06/2021 00:40, Matt Whitlock wrote:
>> The Autoconf documentation for the AC_CACHE_CHECK macro states:
>>
>> The commands-to-set-it must have no side effects except for setting
>> the variable cache-id, see below.
>>
>> However, the tests for support of -msahf and -mmovbe were embedded in
>> the commands-to-set-it for lib_cv_include_x86_isa_level. This had the ...
>
> LGTM, thanks. Also, please confirm that you're the original author and
> are authorized to contribute this patch by adding either a DCO, i.e. add a
> Signed-off-by to indicate that; or by copyright assignment to the FSF
> (check 2.1 and 2.2 on the Contribution Checklist [1])
The lawyers are ruining free software development. Not being one myself, I
make no legal claims about my contribution, but I do assert that it is the
product of my own work that I performed without interactive assistance or
collaboration and, as I do not believe in the concept of intellectual
property, that it is my intention to refuse in perpetuity any and all
claims of ownership that anyone may ever have believed that I had over this
material. If you need a few extra bytes at the end of this email message to
help you feel good, then here they are:
Signed-off-by: Matt Whitlock <sourceware@mattwhitlock.name>
prev parent reply other threads:[~2021-08-11 20:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-17 3:40 Matt Whitlock
2021-08-11 16:44 ` Adhemerval Zanella
2021-08-11 20:16 ` Matt Whitlock [this message]
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=2631fea6-3600-48d6-8220-ede71e2d2a27@mattwhitlock.name \
--to=sourceware@mattwhitlock.name \
--cc=adhemerval.zanella@linaro.org \
--cc=libc-alpha@sourceware.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).