Placing Constants at a Specific RAM Address

I'm implementing an application with the MSP430F6723 which requires use of a RAM ISR table, so as per some example code from TI I've made a table of ISR addresses and located it at the proper RAM address:

#pragma RETAIN
#pragma location=INT_VECT_START_ADDR
isr_struct_t const ram_isr_table =
{
	{
		EMPTY_ISR, EMPTY_ISR, EMPTY_ISR, EMPTY_ISR, EMPTY_ISR, EMPTY_ISR,
		EMPTY_ISR, EMPTY_ISR, EMPTY_ISR, EMPTY_ISR, EMPTY_ISR, EMPTY_ISR,
		EMPTY_ISR, EMPTY_ISR, EMPTY_ISR, EMPTY_ISR, EMPTY_ISR, EMPTY_ISR,
		EMPTY_ISR, EMPTY_ISR, EMPTY_ISR, EMPTY_ISR, EMPTY_ISR, EMPTY_ISR,
		EMPTY_ISR, EMPTY_ISR, EMPTY_ISR, EMPTY_ISR, EMPTY_ISR, EMPTY_ISR,
		EMPTY_ISR, EMPTY_ISR, EMPTY_ISR, EMPTY_ISR, EMPTY_ISR, EMPTY_ISR,
		EMPTY_ISR, EMPTY_ISR, EMPTY_ISR, EMPTY_ISR
	},
	(isr_type_t) &RTC_RAM_ISR,
	// ... etc ...
};

This works fine during debugging, but once power is removed then restored, the table is not restored in RAM. Those addresses just contain random noise. Looking at the disassembly file, I don't actually see any code to initialize this table - I suspect that the debugger simply loaded the table into RAM during programming.

However, this behavior is fixed when I remove the "const" keyword. In this case, the table is stored in the Data section of flash and loaded into RAM during boot.

I would like to understand what logic in the compiler is causing this to happen. The program works now, but I would like to be able to mark this table as "const" to ensure that no user code modifies it. As far as I know, "const" normally causes the compiler to put variables into Flash, so perhaps specifying a location in RAM together with "const" are conflicting orders. Can somebody with more insight to the compiler please explain the cause of this behavior?