Bug#686231: still not fixed

[Vincent Lefevre]

reopen 686231
found 686231 3.1-3
thanks

On 2012-09-28 14:51:08 +0000, Debian Bug Tracking System wrote:
> Changes: 
>  dragonegg (3.1-3) unstable; urgency=low
>  .
>    * Rebuild against the lastest version of gcc
>    (Closes: #686231, #676499)

The crash still occurs on the same testcase, with llvm-gcc
(provided by llvm-gcc-4.6), which is equivalent to:

  gcc-4.6 -fplugin=/usr/lib/gcc/x86_64-linux-gnu/4.6/plugin/dragonegg.so

But

  gcc-4.7 -fplugin=/usr/lib/gcc/x86_64-linux-gnu/4.7/plugin/dragonegg.so

is fine.

Upgrading to 4.7 completely would be fine for me, but the current
dragonegg-4.6 package is broken. In this case, make sure that
  * dragonegg-4.6 and llvm-gcc-4.6 are no longer built (and are
    no longer available in unstable);
  * an upgrade of the dragonegg package uninstalls dragonegg-4.6
    (and llvm-gcc-4.6 as a consequence).

-- 
Vincent Lefèvre <vincent at vinc17.net> - Web: <http://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)