This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: Unreviewed patch (was: another bootstrap failure onsparc-sun-solaris28 in cp/xref.o)


> On Thu, Sep 27, 2001 at 07:05:29PM -0400, John Wehle wrote:
> > However unaligned_integer_asm_op doesn't which makes
> > UNALIGNED_DOUBLE_INT_ASM_OP being null dangerous.
> 
> I don't see the difference between abort and SEGV, myself.

The abort tells you exactly where the problem is.  Otherwise
a NULL is returned which is eventially passed to some other
routine which blows up.  The person debugging the problem
has to do more work to determine where things went wrong.
In this example fputs will probably go boom ... is there
a core generated, can the person run a debugger on the core,
can the debugger provide a reasonable backtrace, etc.  I
find an abort in unaligned_integer_asm_op a little more
obvious.

-- John
-------------------------------------------------------------------------
|   Feith Systems  |   Voice: 1-215-646-8000  |  Email: john@feith.com  |
|    John Wehle    |     Fax: 1-215-540-5495  |                         |
-------------------------------------------------------------------------


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]