Date: Sun, 20 May 2007 19:17:43 +0200 From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@des.no> To: Alexander Kabaev <kabaev@gmail.com> Cc: Michiel Boland <michiel@boland.org>, freebsd-current@freebsd.org, Rosenman <ler@lerctr.org>, Larry@FreeBSD.ORG, Hans Petter Selasky <hselasky@c2i.net> Subject: Re: HEADS UP: OpenSSL problems after GCC 4.2 upgrade Message-ID: <86ps4vifd4.fsf@dwp.des.no> In-Reply-To: <20070520085627.1b7de382@kan.dnsalias.net> (Alexander Kabaev's message of "Sun\, 20 May 2007 08\:56\:27 -0400") References: <20070520022722.1f5a0cda@kan.dnsalias.net> <200705201013.39171.hselasky@c2i.net> <20070520085627.1b7de382@kan.dnsalias.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Alexander Kabaev <kabaev@gmail.com> writes: > Hans Petter Selasky <hselasky@c2i.net> writes: > > Why does it not break on compile/link time? > That is extremely good question. GCC issues warning that the code will > abort if execution ever reaches this point, but compiles the file > anyway. I see no logical explanation for this behaviour. Interested > parties can take this to GCC mailing lists. The build would stop if -Werror were enabled. Speaking of which, it is interesting to note the amount of warnings gcc emits when building the toolchain... DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86ps4vifd4.fsf>