[RTEMS Project] #2473: mvme162 has invalid code in start up

RTEMS trac trac at rtems.org
Thu Nov 19 00:14:48 UTC 2015

#2473: mvme162 has invalid code in start up
 Reporter:  ecwilliams  |       Owner:  chrisj
     Type:  defect      |      Status:  new
 Priority:  high        |   Milestone:  4.11.1
Component:  bsps        |     Version:  4.11
 Severity:  blocker     |  Resolution:
 Keywords:  bsp m68k    |

Comment (by 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
 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.

Ticket URL: <http://devel.rtems.org/ticket/2473#comment:2>
RTEMS Project <http://www.rtems.org/>
RTEMS Project

More information about the bugs mailing list