Package: g++-4.9
Version: 4.9.1-3
Severity: minor
Many of the files in /usr/share/doc/gcc-4.9-base are compressed by xz
then by gz. This seems wrong. (Reporting to g++-4.9 since that package
owns the files.)
% ls -l /usr/share/doc/gcc-4.9-base/test-summaries
total 15316
-rw-r--r-- 1 root root
Your message dated Mon, 28 Jul 2014 11:57:22 +0200
with message-id 53d61e82.1030...@debian.org
and subject line Re: Bug#756266: g++-4.9: test summaries compressed twice (and
why install them at all..?)
has caused the Debian Bug report #756266,
regarding g++-4.9: test summaries compressed twice
On Mon, Jul 28, 2014 at 08:26:59AM -0400, Frank Ch. Eigler wrote:
Please note that the data produced by -g -fvar-tracking is consumed
by tools like systemtap, perf, crash, and makes a significant
difference to the observability of debug AND non-debug kernels. (The
presence of compiled-in
torvalds wrote:
[...]
Actually, I prefer my patch that did it with cc-option checking, and
does it unconditionally.
Because if we do it even for non-debug builds - where it ostensibly
shouldn't matter - we then have that GCC_COMPARE_DEBUG thing working
regardless of configuration.
Please
Hi -
On Mon, Jul 28, 2014 at 09:10:04AM -0400, Theodore Ts'o wrote:
[...]
I thought Markus told us that -fno-var-tracking-assignments makes
absolutely no difference for non-debug kernels?
It does affect CONFIG_DEBUG_INFO kernels, and that config option is
set for all Red Hat kernels (-debug
Am 28.07.2014 um 01:53 schrieb Christian Svensson:
Package: gcc-defaults
Version: 1.130
Severity: wishlist
Tags: patch
Dear Maintainer,
OpenRISC does not have a Java port.
I would be grateful if it could be added to java_no_arches.
I'm not sure if gcj49_arches should be modified, but
We have a stripped down port of both, but they are not close to
ready for upstream.
However I'm curious how those are related to this bug? I cannot see
that this change would make it not dependent on those two.
Alternatively, are you saying that all we need to port GCJ is libgc
and libffi?
TBH I
On Mon, Jul 28, 2014 at 5:26 AM, Frank Ch. Eigler f...@redhat.com wrote:
Please note that the data produced by -g -fvar-tracking is consumed
by tools like systemtap, perf, crash, and makes a significant
difference to the observability of debug AND non-debug kernels.
Yeah, and compared to
On Sun, Jul 27, 2014 at 8:47 PM, Michel Dänzer mic...@daenzer.net wrote:
On 27.07.2014 04:56, Linus Torvalds wrote:
Also, Michel - can you try this patch if you still have your
gcc-4.9.0 install, and send me the resulting fair.s file again?
Attached.
The frame setup looks fine to me now
Am 28.07.2014 um 18:45 schrieb Christian Svensson:
We have a stripped down port of both, but they are not close to
ready for upstream.
please file debian reports including these patches, and please file rfq's
upstream containing your current patches.
However I'm curious how those are related
Control: reopen -1
Hello,
it seems libphobos-4.9-dev still does not build on armel/armhf. Could
you take a look again please?
Regards,
Markus
signature.asc
Description: OpenPGP digital signature
Processing control commands:
reopen -1
Bug #755390 {Done: Matthias Klose d...@debian.org} [libphobos-4.9-dev]
libphobos-4.9-dev: does not build on armel/armhf anymore but did so in the past
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be
On Mon, Jul 28, 2014 at 09:45:45AM -0700, Linus Torvalds wrote:
On Mon, Jul 28, 2014 at 5:26 AM, Frank Ch. Eigler f...@redhat.com wrote:
Please note that the data produced by -g -fvar-tracking is consumed
by tools like systemtap, perf, crash, and makes a significant
difference to the
On 2014.07.28 at 10:27 -0700, Alexei Starovoitov wrote:
On Mon, Jul 28, 2014 at 09:45:45AM -0700, Linus Torvalds wrote:
On Mon, Jul 28, 2014 at 5:26 AM, Frank Ch. Eigler f...@redhat.com wrote:
Please note that the data produced by -g -fvar-tracking is consumed
by tools like systemtap,
gcc-4.7_4.7.4-2_amd64.changes uploaded successfully to localhost
along with the files:
gcc-4.7-source_4.7.4-2_all.deb
libstdc++6-4.7-doc_4.7.4-2_all.deb
gcc-4.7-locales_4.7.4-2_all.deb
gcc-4.7-base_4.7.4-2_amd64.deb
libgcc-4.7-dev_4.7.4-2_amd64.deb
lib32gcc-4.7-dev_4.7.4-2_amd64.deb
On Mon, Jul 28, 2014 at 11:09 AM, Markus Trippelsdorf
mar...@trippelsdorf.de wrote:
It shouldn't be too hard to implement a simple check for the bug in the
next release. Just compile the gcc/testsuite/gcc.target/i386/pr61801.c
testcase with -fcompare-debug. If gcc returns 0 then
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Mon, 28 Jul 2014 17:38:27 +0200
Source: gcc-4.7
Binary: gcc-4.7-base libgcc-4.7-dev lib64gcc-4.7-dev lib32gcc-4.7-dev
libn32gcc-4.7-dev libx32gcc-4.7-dev gcc-4.7 gcc-4.7-multilib gcc-4.7-plugin-dev
gcc-4.7-hppa64
On 2014.07.28 at 11:28 -0700, Linus Torvalds wrote:
On Mon, Jul 28, 2014 at 11:09 AM, Markus Trippelsdorf
mar...@trippelsdorf.de wrote:
It shouldn't be too hard to implement a simple check for the bug in the
next release. Just compile the gcc/testsuite/gcc.target/i386/pr61801.c
testcase
On Mon, Jul 28, 2014 at 10:27:39AM -0700, Alexei Starovoitov wrote:
It's not pretty, but adding it unconditionally was the right thing to do.
Black listing compiler versions is too fragile.
Look at the flip side: now size of build dir will be much smaller :)
White-listing the fixed compiler
package: src:gcc-4.4, src:gcc-4.6, src:gcc-4.7, src:gcc-4.8, src:gcc-4.9
severity: serious
tags: security
Several integer overflow issues affecting all gcc versions have been
fixed in libgfortran:
http://www.openwall.com/lists/oss-security/2014/07/23/7
Best wishes,
Mike
--
To UNSUBSCRIBE,
On 29.07.2014 01:48, Linus Torvalds wrote:
On Sun, Jul 27, 2014 at 8:47 PM, Michel Dänzer mic...@daenzer.net wrote:
On 27.07.2014 04:56, Linus Torvalds wrote:
Also, Michel - can you try this patch if you still have your
gcc-4.9.0 install, and send me the resulting fair.s file again?
21 matches
Mail list logo