This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/80148] operand has impossible constraints
- From: "jakub at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 22 Mar 2017 14:13:54 +0000
- Subject: [Bug target/80148] operand has impossible constraints
- Auto-submitted: auto-generated
- References: <bug-80148-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80148
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bernds at gcc dot gnu.org,
| |jakub at gcc dot gnu.org,
| |vmakarov at gcc dot gnu.org
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
With just -m32 slub1.c -O2 -mpreferred-stack-boundary=2 -march=i686 this
started with r246059. Why doesn't the kernel use atomic builtins instead?
The asm uses %eax/%ebx/%ecx/%edx and needs to use up to 2 other registers to
hold the addresses of mems (unless any of them can be sp relative), if %ebp is
used for frame pointer then there are no other registers left, but it still
ought to be reloadable.