Processing of gcc-6_6.4.0-21_source.changes

gcc-6_6.4.0-21_source.changes uploaded successfully to localhost along with the files: gcc-6_6.4.0-21.dsc gcc-6_6.4.0-21.diff.gz gcc-6_6.4.0-21_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)

Bug#902293: marked as done (gcc-6: internal compiler error in convert_move on arm)

Your message dated Fri, 21 Sep 2018 11:12:00 +0200 with message-id and subject line fixed in 6.4.0-20 has caused the Debian Bug report #902293, regarding gcc-6: internal compiler error in convert_move on arm to be marked as done. This means that you claim that the problem has been dealt with. If

gcc-6_6.4.0-21_source.changes ACCEPTED into unstable

libx32stdc++-6-dev - GNU Standard C++ Library v3 (development files) libx32stdc++6-6-dbg - GNU Standard C++ Library v3 (debugging files) Changes: gcc-6 (6.4.0-21) unstable; urgency=medium . * Update to SVN 20180921 (r264459) from the gcc-6-branch. - Fix PR sanitizer/85835, PR tree

How should sparse depend on gcc?

Hello, sparse is a C code checker that reuses include files from gcc. Currently there are missing the needed dependencies (https://bugs.debian.org/906472). Now I wonder, what is the right way to depend on gcc. For sparse it would be enough to depend on libgcc-8-dev (I think), but as cgcc (which