mvme162 has invalid code in start up

[Eric Williams]

TRAP #7 generated in code for bsp_start(). This is same issue as ticket #2204, fix needs to be extended to all m68k BSPs.

[Chris Johns]

Thanks Eric.

Is this important for 4.11?

[Joel Sherrill]

The very prompt response from the gcc community is this is expected behaviour when writing to 0 on the target. The -fno-delete-null-pointer-checks option disables the check.
I am happy to have our code built with this option because we should not be writing to 0 unless it is a special case such as setting up the vector table.
I am now wondering about the state of our other BSPs.

Given this was the response on #2204. Should this option be swept into all m68k BSPs? Or should it be added in a place (not sure offhand of the spot) where it will apply to all targets and BSPs?

I am prone to say we need to do this for 4.11. It likely breaks every BSP on any architecture which touches memory at 0.

[Chris Johns]

I did not add the option and fixed the BSP as per the commit that closes the ticket. I suggest we fix the m68k BSPs.

[Joel Sherrill]

OK. Is there any easy way to identify the BSPs impacted? It would be nice to have a master list to work through.