Your message dated Fri, 28 Sep 2012 14:47:38 +0000
with message-id <[email protected]>
and subject line Bug#686231: fixed in dragonegg 3.1-3
has caused the Debian Bug report #686231,
regarding dragonegg-4.6 built incorrectly - internal compiler error: 
Segmentation fault with llvm-gcc / cpp-4.6 4.6.3-9
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
686231: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686231
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dragonegg-4.6
Version: 3.1-2
Severity: important

I get the following ICE on the following program:

int f (unsigned int u)
{
  unsigned int c;
  __asm__ ("bsr %1,%0" : "=r" (c) : "rm" (u));
  return 0;
}

$ llvm-gcc -c test.i
*** WARNING *** there are active plugins, do not report this as a bug unless 
you can reproduce it without enabling any plugins.
Event                            | Plugins
PLUGIN_FINISH_UNIT               | dragonegg
PLUGIN_FINISH                    | dragonegg
PLUGIN_START_UNIT                | dragonegg
PLUGIN_ALL_IPA_PASSES_END        | dragonegg
test.i: In function ‘f’:
test.i:4:3: internal compiler error: Segmentation fault
[...]

This is due to the dragonegg plugin, because gcc-4.6 alone is fine
on this example.

Due to this bug, GNU MPFR cannot be built with llvm-gcc.

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages dragonegg-4.6 depends on:
ii  libc6       2.13-35
ii  libffi5     3.0.10-3
ii  libgcc1     1:4.7.1-7
ii  libstdc++6  4.7.1-7

Versions of packages dragonegg-4.6 recommends:
ii  g++-4.6  4.6.3-9
ii  gcc-4.6  4.6.3-9

dragonegg-4.6 suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
Source: dragonegg
Source-Version: 3.1-3

We believe that the bug you reported is fixed in the latest version of
dragonegg, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sylvestre Ledru <[email protected]> (supplier of updated dragonegg package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Fri, 28 Sep 2012 16:25:09 +0200
Source: dragonegg
Binary: dragonegg dragonegg-4.6 dragonegg-4.7 llvm-gcc-4.6 llvm-gcc-4.7
Architecture: source amd64
Version: 3.1-3
Distribution: unstable
Urgency: low
Maintainer: LLVM Packaging Team <[email protected]>
Changed-By: Sylvestre Ledru <[email protected]>
Description: 
 dragonegg  - GCC plugin that uses LLVM for optimization and code generation
 dragonegg-4.6 - GCC plugin that uses LLVM for optimization and code generation
 dragonegg-4.7 - GCC plugin that uses LLVM for optimization and code generation
 llvm-gcc-4.6 - C front end for LLVM C/C++ compiler
 llvm-gcc-4.7 - C front end for LLVM C/C++ compiler
Closes: 676499 686231
Changes: 
 dragonegg (3.1-3) unstable; urgency=low
 .
   * Rebuild against the lastest version of gcc
   (Closes: #686231, #676499)
 .
   [ Matthias Klose ]
   * Use GCC 4.7 by default.
Checksums-Sha1: 
 126cd06ffdeac856b09e81b254ff7968509e06e6 1709 dragonegg_3.1-3.dsc
 71465f6ae33b03821e3287ced4e052d99573ee3f 15333 dragonegg_3.1-3.debian.tar.gz
 7123a734f4220fbea4fbc7b992ee3fdfbbed9ce8 7670 dragonegg_3.1-3_amd64.deb
 1d6c41dd765f0d0cbc3da00d004889b88d4fcedb 4346136 dragonegg-4.6_3.1-3_amd64.deb
 dcd44f868a344ef3bed3fe98495d99afcb22e5e7 4346492 dragonegg-4.7_3.1-3_amd64.deb
 f3fb7be260463ea67c787491bbe79b3763c1c8b7 7940 llvm-gcc-4.6_3.1-3_amd64.deb
 f9417664f06b3b63e1d31cb8af98aaf3fd29e52e 7916 llvm-gcc-4.7_3.1-3_amd64.deb
Checksums-Sha256: 
 02b3d5363871591987c4d878a7d74115e53ff0431b2d0d8c49ca40a747cee125 1709 
dragonegg_3.1-3.dsc
 8a1bf63832a35316224295d9d0c0064c8a80f0f488daef8d7db152f60b881854 15333 
dragonegg_3.1-3.debian.tar.gz
 7665e31687066a9c0d486d8262b7b8c0f75eb62a32c0871b6af9cdbf0e62067c 7670 
dragonegg_3.1-3_amd64.deb
 9136542d372502f78f1a78096452cd3677cce3cc82dcb56e47ca38205f3abef3 4346136 
dragonegg-4.6_3.1-3_amd64.deb
 7ddbb2123af13a5d0429a6e637c43ed238ede8f6c049159850f6f01818e24019 4346492 
dragonegg-4.7_3.1-3_amd64.deb
 b90a182f47f9489cc35ade851a977e1b90c319d2c5af8b4940a0f2fcbbee41ce 7940 
llvm-gcc-4.6_3.1-3_amd64.deb
 e5fd5db3fb93690dce2f82d035f13d458f657f9874d07dfc5c08c75cc20dbe4c 7916 
llvm-gcc-4.7_3.1-3_amd64.deb
Files: 
 f3a5818bb4c08f4f3890a71f76672b72 1709 devel optional dragonegg_3.1-3.dsc
 5bff6321edad1dabc12fb379a7b1eeea 15333 devel optional 
dragonegg_3.1-3.debian.tar.gz
 a455b611ad4319ffff4c5034ef72a984 7670 devel optional dragonegg_3.1-3_amd64.deb
 7cbf502b44464e50951138c8c4befb70 4346136 devel optional 
dragonegg-4.6_3.1-3_amd64.deb
 e85022af13430bbd3d040e445cb7e7b3 4346492 devel optional 
dragonegg-4.7_3.1-3_amd64.deb
 b76f240747a7875ac872275f89b494fa 7940 devel optional 
llvm-gcc-4.6_3.1-3_amd64.deb
 da90012a99c7510aa344e58ff5488c05 7916 devel optional 
llvm-gcc-4.7_3.1-3_amd64.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlBltBgACgkQiOXXM92JlhAAxwCg9sU6uv8Kpcxc4pm44pOZ621M
Yp4An2XP1TbohRIJLxd/VnBzaII2uqQc
=5Aw+
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to