| Summary: | dev-libs/libgcrypt-1.7.0: impossible constraints on 'asm' operand | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Phil Stracchino (Unix Ronin) <phils> |
| Component: | [OLD] Development | Assignee: | No maintainer - Look at https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers if you want to take care of it <maintainer-needed> |
| Status: | RESOLVED OBSOLETE | ||
| Severity: | normal | CC: | candrews, klaus.kusche, k_f, phils |
| Priority: | Normal | Keywords: | UPSTREAM |
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | https://bugs.gnupg.org/gnupg/issue2325 | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | Build log | ||
|
Description
Phil Stracchino (Unix Ronin)
2016-04-16 20:36:48 UTC
Can you still reproduce this with gcc 4.9.3? Hmm,. I hadn't noticed I'd neglected to switch gcc-config. Give me a few minutes, I'll retest. ...And the answer appears to be, "With gcc 4.9.3, it works." (In reply to Phil Stracchino (Unix Ronin) from comment #3) > ...And the answer appears to be, "With gcc 4.9.3, it works." Well thats good at least, will see whether we can work with upstream to get it fixed or adding a check to gcc version downstream Similar problem but different error message here:
In file included from /usr/include/features.h:368:0,
from /usr/include/stdio.h:27,
from /var/portage/portage/dev-libs/libgcrypt-1.7.0/work/libgcrypt-1.7.0/cipher/rijndael-ssse3-amd64.c:38:
/var/portage/portage/dev-libs/libgcrypt-1.7.0/work/libgcrypt-1.7.0/cipher/rijndael-ssse3-amd64.c: In function '_gcry_aes_ssse3_do_setkey':
/usr/include/bits/string3.h:50:1: error: inlining failed in call to always_inline 'memcpy': target specific option mismatch
__NTH (memcpy (void *__restrict __dest, const void *__restrict __src,
^
/var/portage/portage/dev-libs/libgcrypt-1.7.0/work/libgcrypt-1.7.0/cipher/rijndael-ssse3-amd64.c:175:3: error: called from here
memcpy(&ctx->keyschdec32[0][0], key, keybits / 8);
^
gcc 5.3.0
(In reply to Klaus Kusche from comment #5) > Similar problem but different error message here: Please file a separate bug for this issue |