Re: HEADS UP: OpenSSL problems after GCC 4.2 upgrade

Hello Alexander,

* Alexander Kabaev <kabaev@xxxxxxxxx> wrote:
there were several reports of OpenSSL being broken when compiled with
GCC 4.2. It turns out OpenSSL uses function casting feature that was
aggressively de-supported by GCC 4.2 and GCC goes as far as inserting
invalid instructions ON PURPOSE to discourage the practice.

Is that the reason why portsnap returns SIGILL's on my box after the
upgrade?

Yours,
--
Ed Schouten <ed@xxxxxx>
WWW: http://g-rave.nl/

Attachment: pgpImHpc1Vxjl.pgp
Description: PGP signature

Relevant Pages

  • Re: [RFC PATCH 1/2] Marker probes in futex.c
    ... burned by the compiler inserting a jmp there. ... I wonder if just sticking in 2 barriers around your code make gcc stop ... extra instruction. ... For flags that are unaffected by gcc's ...
    (Linux-Kernel)
  • Re: HEADS UP: OpenSSL problems after GCC 4.2 upgrade
    ... It turns out OpenSSL uses function casting feature that was ... aggressively de-supported by GCC 4.2 and GCC goes as far as inserting ...
    (freebsd-current)
  • Re: HEADS UP: OpenSSL problems after GCC 4.2 upgrade
    ... It turns out OpenSSL uses function casting feature that was ... aggressively de-supported by GCC 4.2 and GCC goes as far as inserting ... invalid instructions ON PURPOSE to discourage the practice. ...
    (freebsd-hackers)
  • Re: HEADS UP: OpenSSL problems after GCC 4.2 upgrade
    ... It turns out OpenSSL uses function casting feature that was ... aggressively de-supported by GCC 4.2 and GCC goes as far as inserting ... invalid instructions ON PURPOSE to discourage the practice. ...
    (freebsd-current)
  • Re: HEADS UP: OpenSSL problems after GCC 4.2 upgrade
    ... aggressively de-supported by GCC 4.2 and GCC goes as far as inserting ... invalid instructions ON PURPOSE to discourage the practice. ... intentionally generating incorrect code? ...
    (freebsd-hackers)