rs6000: rs6000_dbx_register_number for fp/ap/mq
authorSegher Boessenkool <segher@kernel.crashing.org>
Mon, 6 May 2019 22:01:27 +0000 (00:01 +0200)
committerSegher Boessenkool <segher@gcc.gnu.org>
Mon, 6 May 2019 22:01:27 +0000 (00:01 +0200)
commite294835aed9d0ad48131b1c91c9a7c774ea64a37
tree1adf12b612d3c464f78f48fc5deecc0208ba2e44
parent3afd514bca6ea572e614b5289c4429ace693311b
rs6000: rs6000_dbx_register_number for fp/ap/mq

The frame pointer and the argument pointer aren't real registers.  MQ
was a register on old POWER.  All three are still used as arguments to
rs6000_dbx_register_number during initialisation.  If we handle them
explicitly we can do a gcc_unreachable to catch other unexpected
registers.

* config/rs6000/rs6000.c (rs6000_dbx_register_number): Handle
FRAME_POINTER_REGNUM, ARG_POINTER_REGNUM, and 64 (which was MQ).

From-SVN: r270925
gcc/ChangeLog
gcc/config/rs6000/rs6000.c