From: Alexander Boyko <alexander_boyko@xyratex.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: kbuild test robot <fengguang.wu@intel.com>,
Linux Crypto Mailing List <linux-crypto@vger.kernel.org>
Subject: Re: [cryptodev:master 22/36] arch/x86/crypto/crc32-pclmul_asm.S:87:2: warning: #warning Using 32bit code support
Date: Sun, 20 Jan 2013 09:55:37 +0400 [thread overview]
Message-ID: <50FB86D9.1070200@xyratex.com> (raw)
In-Reply-To: <20130120005545.GA3328@gondor.apana.org.au>
You can kill it.
1/20/13 4:55 AM, Herbert Xu пишет:
> On Sun, Jan 20, 2013 at 08:50:00AM +0800, kbuild test robot wrote:
>> tree: git://git.kernel.org/pub/scm/linux/kernel/git/herbert/cryptodev-2.6.git master
>> head: d3f5188dfea70e7ea6570bd4bc9d6d7dbd431e39
>> commit: 78c37d191dd6899d8c219fee597a17d6e3c5d288 [22/36] crypto: crc32 - add crc32 pclmulqdq implementation and wrappers for table implementation
>> config: make ARCH=i386 allyesconfig
>>
>> All warnings:
>>
>>>> arch/x86/crypto/crc32-pclmul_asm.S:87:2: warning: #warning Using 32bit code support [-Wcpp]
>> vim +87 arch/x86/crypto/crc32-pclmul_asm.S
>>
>> 71 /*
>> 72 * #define CRCPOLY_TRUE_LE_FULL 0x1DB710641LL
>> 73 *
>> 74 * Barrett Reduction constant (u64`) = u` = (x**64 / P(x))` = 0x1F7011641LL
>> 75 * #define CONSTANT_RU 0x1F7011641LL
>> 76 */
>> 77 .Lconstant_RUpoly:
>> 78 .octa 0x00000001F701164100000001DB710641
>> 79
>> 80 #define CONSTANT %xmm0
>> 81
>> 82 #ifdef __x86_64__
>> 83 #define BUF %rdi
>> 84 #define LEN %rsi
>> 85 #define CRC %edx
>> 86 #else
>> > 87 #warning Using 32bit code support
> Do we need this warning or can I kill it?
>
> Thanks!
next prev parent reply other threads:[~2013-01-20 5:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <50fb3f38.VIxxNsjMujPGjroT%fengguang.wu@intel.com>
2013-01-20 0:55 ` [cryptodev:master 22/36] arch/x86/crypto/crc32-pclmul_asm.S:87:2: warning: #warning Using 32bit code support Herbert Xu
2013-01-20 5:55 ` Alexander Boyko [this message]
2013-01-20 7:05 ` Herbert Xu
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=50FB86D9.1070200@xyratex.com \
--to=alexander_boyko@xyratex.com \
--cc=fengguang.wu@intel.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.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