This is the mail archive of the
mailing list for the glibc project.
[Bug build/20621] glibc 2.24 fails to compile on x86_64 with "operand type mismatch" in fpu/e_expl.S
- From: "joseph at codesourcery dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Thu, 22 Sep 2016 18:14:33 +0000
- Subject: [Bug build/20621] glibc 2.24 fails to compile on x86_64 with "operand type mismatch" in fpu/e_expl.S
- Auto-submitted: auto-generated
- References: <email@example.com/bugzilla/>
--- Comment #11 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
On Thu, 22 Sep 2016, michael.tremer at ipfire dot org wrote:
> So am I correct when I take this as this configuration should be supported but
> is currently just broken?
I'm not sure "should be supported" is meaningful for undocumented
features. Such combinations of features will inevitably bitrot unless
there are people taking an active role in keeping them working during
development, including sending patches to fix issues that arise.
I'm not clear on what the problem actually is. Is it that certain forms
of operands, generated by HIDDEN_JUMPTARGET, are supported by some
instructions but not by others, and so the intended optimization is not
possible in this case? If so, that would suggest needing additional
macros for the different contexts in which HIDDEN_JUMPTARGET is used. Or
is some other syntax for the operand needed in this particular context?
You are receiving this mail because:
You are on the CC list for the bug.