| Summary: | none/test/arm/vfp.c doesn't build with binutils 2.31 gas | ||
|---|---|---|---|
| Product: | [Developer tools] valgrind | Reporter: | Mark Wielaard <mark> |
| Component: | general | Assignee: | Julian Seward <jseward> |
| Status: | RESOLVED MOVED | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Mark Wielaard
2018-07-12 21:16:33 UTC
Mark, what's the status of this now? I have a vague memory that this was resolved somehow, but I can't remember how. Wasn't there some change subsequently pushed into binutils, that "fixes" this? Yes, this was resolved in binutils by allowing the existing construct again: commit 524496887011b46736f4c5865a5faedd46be6f54 Author: Nick Clifton <nickc@redhat.com> Date: Fri Jul 13 11:44:49 2018 +0100 Allow bit-patterns in the immediate field of ARM neon mov instructions. * config/tc-arm.c (do_neon_mov): When converting an integer immediate into a floating point value, check that the conversion is valid. Also warn if the immediate is valid as both a floating point value and a bit pattern. * testsuite/gas/arm/vfp-mov-enc.s: Add instructions that use floating point bit patterns. * testsuite/gas/arm/vfp-mov-enc.d: Add regexps for the disassembly of the new insns. Which is on both the binutils master and 2.31 branches. I removed the valgrind workaround in fedora already. |