Daniel Towner <[EMAIL PROTECTED]> writes:
> I maintain a port of gcc for an embedded processor which has a HALT
> instruction. This instruction stops the processor, and generates an
> appropriate interrupt to indicate to its parent system that it has
> stopped. The instruction is accessed by the p
>
> Hi Andrew,
>
> The problem with calling __builtin_trap directly comes when several
> traps are called in the same function. For example, if a function
> contains several identical assertions on different code paths, then gcc
> will generate a single copy of the assertion, and branch to tha
Hi Andrew,
The problem with calling __builtin_trap directly comes when several
traps are called in the same function. For example, if a function
contains several identical assertions on different code paths, then gcc
will generate a single copy of the assertion, and branch to that copy
from e
>
> Hi all,
>
> I maintain a port of gcc for an embedded processor which has a HALT
> instruction. This instruction stops the processor, and generates an
> appropriate interrupt to indicate to its parent system that it has
> stopped. The instruction is accessed by the programmer using a
> por
Hi all,
I maintain a port of gcc for an embedded processor which has a HALT
instruction. This instruction stops the processor, and generates an
appropriate interrupt to indicate to its parent system that it has
stopped. The instruction is accessed by the programmer using a
port-specific built
