spd: Use `ENABLE_ASSERTIONS` instead of `DEBUG`
A line in the upstream SPDs is only compiled in in `DEBUG` builds. This
line is used to help with assertions and so assertion failures can
happen in release builds with assertions enabled. Use
`ENABLE_ASSERTIONS` instead of `DEBUG`.
This bug was introduced in commit aa61368eb5
, which introduced the build
option `ENABLE_ASSERTIONS`.
Change-Id: I7977df9c89c68677b00099b2a1926fa3cb0937c6
Signed-off-by: Antonio Nino Diaz <antonio.ninodiaz@arm.com>
This commit is contained in:
parent
f9a6db0f48
commit
92cad5fa4b
|
@ -78,7 +78,7 @@ uint64_t opteed_synchronous_sp_entry(optee_context_t *optee_ctx)
|
|||
cm_set_next_eret_context(SECURE);
|
||||
|
||||
rc = opteed_enter_sp(&optee_ctx->c_rt_ctx);
|
||||
#if DEBUG
|
||||
#if ENABLE_ASSERTIONS
|
||||
optee_ctx->c_rt_ctx = 0;
|
||||
#endif
|
||||
|
||||
|
|
|
@ -131,7 +131,7 @@ uint64_t tlkd_synchronous_sp_entry(tlk_context_t *tlk_ctx)
|
|||
cm_set_next_eret_context(SECURE);
|
||||
|
||||
rc = tlkd_enter_sp(&tlk_ctx->c_rt_ctx);
|
||||
#if DEBUG
|
||||
#if ENABLE_ASSERTIONS
|
||||
tlk_ctx->c_rt_ctx = 0;
|
||||
#endif
|
||||
|
||||
|
|
|
@ -79,7 +79,7 @@ uint64_t tspd_synchronous_sp_entry(tsp_context_t *tsp_ctx)
|
|||
cm_set_next_eret_context(SECURE);
|
||||
|
||||
rc = tspd_enter_sp(&tsp_ctx->c_rt_ctx);
|
||||
#if DEBUG
|
||||
#if ENABLE_ASSERTIONS
|
||||
tsp_ctx->c_rt_ctx = 0;
|
||||
#endif
|
||||
|
||||
|
|
Loading…
Reference in New Issue