[lkml]   [2002]   [Jan]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH] C undefined behavior fix
    Date said:
    > > (and for CONSTANT < 5 it of course generated correct code to fill dst
    > > with string contents; and yes, I know that code will sigsegv on run
    > > because of dst is not initialized - but it should die at runtime, not
    > > at compile time).
    > An ICE, while it's not quite what was expected and it'll probably get fixed,
    > is nonetheless a perfectly valid implementation of 'undefined behaviour'.

    Not for GCC it isn't. Our standards say that a compiler crash, for any
    input whatsoever, no matter how invalid (even if you feed in line noise),
    is a bug. Other than that we shouldn't make promises, though the old gcc1
    behavior of trying to launch a game of rogue or hack when encountering a
    #pragma was cute.

    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2005-03-22 13:15    [W:0.020 / U:12.456 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site