On Mon, 31 Oct 2016 07:19:56 +0100 Klaus Ethgen wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Am Do den 27. Okt 2016 um 9:20 schrieb Eric Valette:
> I have reverted to 6.2.0-6 anyway using testing as a source for the gcc
> package. But that will work as long as the "broken for kernel"
LAST_UPDATED: Thu Nov 24 12:56:58 UTC 2016 (revision 242836)
=== acats tests ===
FAIL: c41104a
FAIL: c64201b
FAIL: c761007
FAIL: c97204b
FAIL: c97304b
FAIL: c9a009a
FAIL: c9a009c
FAIL: c9a009f
FAIL: c9a009g
FAIL: cb1010a
=== acats Summary ===
#
LAST_UPDATED: Thu Nov 24 12:10:52 UTC 2016 (revision 242831)
Target: i686-gnu
gcc version 6.2.1 20161124 (Debian 6.2.1-5)
Native configuration is i686-pc-gnu
=== g++ tests ===
Running target unix
FAIL: g++.dg/abi/abi-tag23.C -std=gnu++98 (test for warnings, line 22)
FAIL: g+
Svante Signell, on Sun 27 Nov 2016 18:17:17 +0100, wrote:
> On Sun, 2016-11-27 at 18:02 +0100, Samuel Thibault wrote:
> > > But as you wish, an updated patch is attached.
> >
> > _Bool
> > Continued (uint32_t *w)
> > {
> > +#ifndef WCONTINUED
> > + *w = 0;
> > + return 0;
> > +#else
> > re
On Sun, 2016-11-27 at 18:02 +0100, Samuel Thibault wrote:
> Hello,
...
> > But as you wish, an updated patch is attached.
>
> _Bool
> Continued (uint32_t *w)
> {
> +#ifndef WCONTINUED
> + *w = 0;
> + return 0;
> +#else
> return WIFCONTINUED (*w) != 0;
> +#endif
> }
>
> Err, recheck the s
Hello,
Svante Signell, on Sun 27 Nov 2016 17:33:52 +0100, wrote:
> > > Index: gcc-6-6.2.1-4.1/src/libgo/go/syscall/wait.c
> > > ===
> > > --- gcc-6-6.2.1-4.1.orig/src/libgo/go/syscall/wait.c
> > > +++ gcc-6-6.2.1-4.1/src/libgo/go/sysc
On Sun, 2016-11-27 at 00:17 +0100, Samuel Thibault wrote:
> Hello,
>
> Nice work!
Thanks :)
> Mmm, why making changes in each file in a separate patch? I don't
> think
> it makes things easier to review, I'd say rather send a big patch,
> it's
> altogether that it makes sense anyway.
It's just
Processing commands for cont...@bugs.debian.org:
> forwarded 845751 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71873
Bug #845751 [gcc-6] yadifa FTBFS on ppc64el: internal compiler error: in
push_reload, at reload.c:1349
Changed Bug forwarded-to-address to
'https://gcc.gnu.org/bugzilla/show_bug
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 27 Nov 2016 16:37:59 +0100
Source: gcc-defaults
Binary: cpp gcc gcc-multilib g++ g++-multilib gobjc gobjc-multilib gobjc++
gobjc++-multilib gfortran gfortran-multilib gccgo gccgo-multilib libgcj-common
libgcj-bc
gcc-defaults_1.169_amd64.changes uploaded successfully to localhost
along with the files:
gcc-defaults_1.169.dsc
gcc-defaults_1.169.tar.gz
cpp-aarch64-linux-gnu_7-20161116-2_amd64.deb
cpp-arm-linux-gnueabi_7-20161116-2_amd64.deb
cpp-arm-linux-gnueabihf_7-20161116-2_amd64.deb
cpp-mips-li
Your message dated Sun, 27 Nov 2016 14:25:54 +0100
with message-id <9ee717dd-652f-16cd-9f85-a5351b462...@debian.org>
and subject line Re: gcc-6-arm-linux-gnueabihf: cross-compiled code fails to
link on target with native gcc-6
has caused the Debian Bug report #844780,
regarding gcc-6-arm-linux-gnu
> On Nov 27, 2016, at 2:14 PM, Matthias Klose wrote:
>
> The patches to configure --with-cpu-32= and --with-cpu-64= are availabe in GCC
> 6, so we should use them and ensure that the defaults for the sparc/64 and
> sparc64, and sparc and sparc64/32 targets match. Just forcing ultrasparc for
> a
On 24.11.2016 19:10, Jose E. Marchesi wrote:
>
> I'm pretty confident that --with-cpu=ultrasparc won't do any harm in
> 64-bit mode, but Jose (CC'ed as gcc upstream) will hopefully correct
> me here if I'm wrong.
>
> The cpu selected in --with-cpu impacts both -m64 and -m32 in a b
Processing commands for cont...@bugs.debian.org:
> reopen 845377
Bug #845377 {Done: Matthias Klose } [gdc-6] gdc-6: libdl
trouble again
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No lon
Processing commands for cont...@bugs.debian.org:
> forwarded 845751 https://gcc.gnu.org/PR78543
Bug #845751 [gcc-6] yadifa FTBFS on ppc64el: internal compiler error: in
push_reload, at reload.c:1349
Set Bug forwarded-to-address to 'https://gcc.gnu.org/PR78543'.
> tags 845751 + upstream
Bug #84575
Your message dated Sun, 27 Nov 2016 13:18:16 +0100
with message-id <20e8e786-a621-6145-a322-7aa6b1a59...@debian.org>
and subject line fixed in 6.2.0-6
has caused the Debian Bug report #838892,
regarding [ppc64el] boot arguments (passed as CONFIG_CMDLINE) are not being
picked up by kernel
to be mar
On Sat, Nov 26, 2016 at 3:48 PM, Matthias Klose wrote:
> Control: severity -1 important
> Control: reassign -1 gcc-6
>
> Mathieu, these issues are not RC issues, gcc doesn't become unusable.
I managed to skrew up the `reassign` and missed the original
`severity` report. Sorry for the mess :(
Processing control commands:
> reassign -1 src:gcc-6 6.2.0-7
Bug #845730 [src:torus-trooper] torus-trooper: FTBFS: relocation R_X86_64_PC32
against symbol
`_D3std6format18__T10FormatSpecTaZ10FormatSpec6flZeroMFNaNbNdNiNfbZv' can not
be used when making a shared object; recompile with -fPIC
Bug
Control: reassign -1 src:gcc-6 6.2.0-7
Control: affects -1 src:torus-trooper
On Sat, Nov 26, 2016 at 10:59:23AM +0100, Chris Lamb wrote:
>...
> torus-trooper fails to build from source in unstable/amd64:
>
> […]
>
> dh_auto_build -- DFLAGS="-frelease"
> make -j1 DFLAGS=-frelease
> ma
19 matches
Mail list logo
