Package: libobjc4
Version: 4.9.1-2
Severity: important
The patches gcc-elfv2-abi-warn*.diff are apparently incomplete as
linking with libobjc fails on powerpc/ppc64/ppc64el with:
| gcc -rdynamic -Wl,-z,relro -Wl,--no-undefined -Wl,--as-needed
| -pthread -fexceptions -fgnu-runtime -o
Processing commands for cont...@bugs.debian.org:
found 756096 4.8.3-5
Bug #756096 [libobjc4] libobjc4: Linking fails with undefined reference to
`rs6000_special_adjust_field_align_p'
There is no source info for the package 'libobjc4' at version '4.8.3-5' with
architecture ''
Unable to make a
Package: gcc-defaults
Version: 1.130
Severity: wishlist
Dear Maintainer,
It would be nice if there were a libstdc++-doc metapackage to automatically
pull in the latest libstdc++-X.Y-doc, so I don't have to keep remembering to
manually remove the old and install the new documentation with each
LAST_UPDATED: Fri Jul 25 10:21:03 UTC 2014 (revision 213051)
Target: s390x-linux-gnu
gcc version 4.8.3 (Debian 4.8.3-6)
Native configuration is s390x-ibm-linux-gnu
=== g++ tests ===
Running target unix
FAIL: g++.dg/init/const9.C -std=c++98 scan-assembler-not rodata
FAIL:
LAST_UPDATED: Fri Jul 25 10:21:03 UTC 2014 (revision 213051)
Native configuration is arm-unknown-linux-gnueabihf
=== boehm-gc tests ===
Running target unix
=== boehm-gc Summary ===
# of expected passes12
# of unsupported tests 1
LAST_UPDATED: Fri Jul 25 10:21:03 UTC 2014 (revision 213051)
Native configuration is arm-unknown-linux-gnueabi
=== boehm-gc tests ===
Running target unix
=== boehm-gc Summary ===
# of expected passes12
# of unsupported tests 1
LAST_UPDATED: Thu Jul 24 22:07:18 UTC 2014 (revision 213031)
Native configuration is arm-unknown-linux-gnueabi
=== boehm-gc tests ===
Running target unix
=== boehm-gc Summary ===
# of expected passes12
# of unsupported tests 1
LAST_UPDATED: Thu Jul 24 22:07:18 UTC 2014 (revision 213031)
Native configuration is arm-unknown-linux-gnueabihf
=== boehm-gc tests ===
Running target unix
=== boehm-gc Summary ===
# of expected passes12
# of unsupported tests 1
LAST_UPDATED: Fri Jul 25 10:21:03 UTC 2014 (revision 213051)
Target: x86_64-linux-gnu
gcc version 4.8.3 (Debian 4.8.3-6)
Native configuration is x86_64-pc-linux-gnu
=== g++ tests ===
Running target unix
FAIL: g++.dg/asan/deep-stack-uaf-1.C -O0 output pattern test, is
LAST_UPDATED: Fri Jul 25 10:21:03 UTC 2014 (revision 213051)
Target: i486-linux-gnu
gcc version 4.8.3 (Debian 4.8.3-6)
Native configuration is i486-pc-linux-gnu
=== g++ tests ===
Running target unix
FAIL: g++.dg/asan/deep-stack-uaf-1.C -O0 output pattern test, is
LAST_UPDATED: Thu Jul 24 22:07:18 UTC 2014 (revision 213031)
Target: s390x-linux-gnu
gcc version 4.9.1 (Debian 4.9.1-2)
Native configuration is s390x-ibm-linux-gnu
=== g++ tests ===
Running target unix
FAIL: g++.dg/init/const9.C -std=c++98 scan-assembler-not rodata
FAIL:
LAST_UPDATED: Thu Jul 24 22:07:18 UTC 2014 (revision 213031)
Target: i486-kfreebsd-gnu
gcc version 4.9.1 (Debian 4.9.1-2)
Native configuration is i486-pc-kfreebsd-gnu
=== g++ tests ===
Running target unix
FAIL: g++.dg/ipa/pr61160-3.C -std=gnu++98 execution test
FAIL:
LAST_UPDATED: Thu Jul 24 22:07:18 UTC 2014 (revision 213031)
Target: x86_64-kfreebsd-gnu
gcc version 4.9.1 (Debian 4.9.1-2)
Native configuration is x86_64-pc-kfreebsd-gnu
=== g++ tests ===
Running target unix
FAIL: g++.dg/guality/pr55665.C -O2 line 23 p == 40
FAIL:
Hi Michel,
On 25/07/14 02:25, Michel Dänzer wrote:
Attached is fair.s from Debian gcc 4.8.3-5. Does that look better? I'm
going to try reproducing the problem with a kernel built by that now.
It looks like gcc-4.9 Debian package version 4.9.1-2 available in
sid/jessie may have already fixed
On Fri, Jul 25, 2014 at 11:29 AM, Linus Torvalds
torva...@linux-foundation.org wrote:
I'm sure it's possible, but it sounds potentially complicated.
Hmm. The bugzilla entry just taught me a new gcc flag:
-fcompare-debug. That apparently makes gcc compile things twice,
once with debugging and
On Sat, Jul 26, 2014 at 11:28 AM, Linus Torvalds
torva...@linux-foundation.org wrote:
That's a bit worrisome. I haven't actually checked if the code
generation differs in significant ways yet..
Nope. Just three instructions that got re-ordered from ABC to CAB in a
way that makes no difference.
On Sat, Jul 26, 2014 at 09:35:57PM +0200, Markus Trippelsdorf wrote:
But fortunately the workaround for the new inode.c bug is the same as
for the original bug: -fno-var-tracking-assignments.
It would make sense to enabled it unconditionally for all debug
configurations for now.
What's
On 2014.07.26 at 11:39 -0700, Linus Torvalds wrote:
On Sat, Jul 26, 2014 at 11:28 AM, Linus Torvalds
torva...@linux-foundation.org wrote:
That's a bit worrisome. I haven't actually checked if the code
generation differs in significant ways yet..
Nope. Just three instructions that got
On Sat, Jul 26, 2014 at 12:35 PM, Markus Trippelsdorf
mar...@trippelsdorf.de wrote:
But fortunately the workaround for the new inode.c bug is the same as
for the original bug: -fno-var-tracking-assignments.
It would make sense to enabled it unconditionally for all debug
configurations for
On Sat, Jul 26, 2014 at 12:56 PM, Linus Torvalds
torva...@linux-foundation.org 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?
Hmm. The good news is that with that patch, the GCC_COMPARE_DEBUG
build succeeds.
On 2014.07.26 at 15:55 -0400, Theodore Ts'o wrote:
On Sat, Jul 26, 2014 at 09:35:57PM +0200, Markus Trippelsdorf wrote:
But fortunately the workaround for the new inode.c bug is the same as
for the original bug: -fno-var-tracking-assignments.
It would make sense to enabled it
On 2014.07.26 at 12:56 -0700, Linus Torvalds wrote:
On Sat, Jul 26, 2014 at 12:35 PM, Markus Trippelsdorf
mar...@trippelsdorf.de wrote:
But fortunately the workaround for the new inode.c bug is the same as
for the original bug: -fno-var-tracking-assignments.
It would make sense to
On Sat, Jul 26, 2014 at 1:19 PM, Markus Trippelsdorf
mar...@trippelsdorf.de wrote:
Yes. The option only affects -g builds.
Ok, good. I'll wait a bit to hopefully get confirmation from Michel's
setup, but this does seem to be the solution.
So, the option should only be enabled for debugging
On Sat, Jul 26, 2014 at 10:20:55PM +0200, Markus Trippelsdorf wrote:
On 2014.07.26 at 15:55 -0400, Theodore Ts'o wrote:
On Sat, Jul 26, 2014 at 09:35:57PM +0200, Markus Trippelsdorf wrote:
But fortunately the workaround for the new inode.c bug is the same as
for the original bug:
24 matches
Mail list logo
