aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRoger Sayle <roger@nextmovesoftware.com>2023-07-06 09:58:17 +0100
committerRoger Sayle <roger@nextmovesoftware.com>2023-07-06 09:58:17 +0100
commit11578db6e2a0da8fa7921713093e91ea0e599bef (patch)
tree39e3a385d55bb31983086bffe734abd5592476c3
parent6ded65b8e6c55a9280e381775a64b2c282df6207 (diff)
downloadgcc-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.
-rw-r--r--gcc/dwarf2out.cc1
1 files changed, 1 insertions, 0 deletions
diff --git a/gcc/dwarf2out.cc b/gcc/dwarf2out.cc
index e973644..238d0a9 100644
--- a/gcc/dwarf2out.cc
+++ b/gcc/dwarf2out.cc
@@ -16941,6 +16941,7 @@ mem_loc_descriptor (rtx rtl, machine_mode mode,
case SMUL_HIGHPART:
case UMUL_HIGHPART:
case BITREVERSE:
+ case COPYSIGN:
break;
case CONST_STRING: