diff options
| author | Roger Sayle <roger@nextmovesoftware.com> | 2023-07-06 09:58:17 +0100 |
|---|---|---|
| committer | Roger Sayle <roger@nextmovesoftware.com> | 2023-07-06 09:58:17 +0100 |
| commit | 11578db6e2a0da8fa7921713093e91ea0e599bef (patch) | |
| tree | 39e3a385d55bb31983086bffe734abd5592476c3 /gcc/ggc-internal.h | |
| parent | 6ded65b8e6c55a9280e381775a64b2c282df6207 (diff) | |
| download | gcc-11578db6e2a0da8fa7921713093e91ea0e599bef.zip gcc-11578db6e2a0da8fa7921713093e91ea0e599bef.tar.gz gcc-11578db6e2a0da8fa7921713093e91ea0e599bef.tar.bz2 | |
[Committed] Handle COPYSIGN in dwarf2out.cc's mem_loc_descriptor.
Many thanks to Hans-Peter Nilsson for reminding me that new RTX codes
need to be added to dwarf2out.cc's mem_loc_descriptor, and for doing
this for BITREVERSE. This patch does the same for the recently added
COPYSIGN. I'd been testing these on a target that doesn't use DWARF
(nvptx-none) and so didn't exhibit the issue, and my additional testing
on x86_64-pc-linux-gnu to double check that changes were safe, doesn't
(yet) trigger the problematic assert in dwarf2out.cc's mem_loc_descriptor.
2023-07-06 Roger Sayle <roger@nextmovesoftware.com>
gcc/ChangeLog
* dwarf2out.cc (mem_loc_descriptor): Handle COPYSIGN.
Diffstat (limited to 'gcc/ggc-internal.h')
0 files changed, 0 insertions, 0 deletions