This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Fwd: crash: longjmp vs -fprofile-arcs
- From: Richard Henderson <rth at redhat dot com>
- To: Dale Johannesen <dalej at apple dot com>
- Cc: gcc at gcc dot gnu dot org
- Date: Mon, 9 Dec 2002 11:25:35 -0800
- Subject: Re: Fwd: crash: longjmp vs -fprofile-arcs
- References: <3FC4EB69-0B9B-11D7-B9DC-000393D76DAA@apple.com>
On Mon, Dec 09, 2002 at 09:25:44AM -0800, Dale Johannesen wrote:
> now what? cc -fprofile-arcs lj.c
> lj.c: In function `foo':
> lj.c:2: internal error: Bus error
> Please submit a full bug report, blah blah
>
> It seems the block that calls longjmp has no successors, and the code
> in profile.c is not expecting that. Could somebody clarify which code
> is right?
Before the invocation of the profiling routines, no successors is correct.
During the invocation of the profiling routines, however, we add fake
edges from calls to the exit block. I would not expect this to change
for a noreturn function like longjmp.
So I guess the quesion is "where did you get this null, exactly?"
r~