Re: [BUILDROBOT] RISC-V: ‘profile_probability’ has not been declared

2017-07-13 Thread Jan-Benedict Glaw
Hi Jeff! On Thu, 2017-07-13 14:43:52 -0600, Jeff Law wrote: > On 07/13/2017 02:39 PM, Jan-Benedict Glaw wrote: > > On Thu, 2017-06-29 14:27:41 +0200, Jan Hubicka wrote: > >> this is second step of the profile maintenance revamp. It implements > >> profile_probability type which is pretty much s

Re: [BUILDROBOT] RISC-V: ‘profile_probability’ has not been declared

2017-07-13 Thread Palmer Dabbelt
On Thu, 13 Jul 2017 13:43:52 PDT (-0700), l...@redhat.com wrote: > On 07/13/2017 02:39 PM, Jan-Benedict Glaw wrote: >> Hi Jan, >> hi Kito, Palmer and Andrew! >> >> On Thu, 2017-06-29 14:27:41 +0200, Jan Hubicka wrote: >>> this is second step of the profile maintenance revamp. It implements >>> pr

Re: [BUILDROBOT] RISC-V: ‘profile_probability’ has not been declared

2017-07-13 Thread Jeff Law
On 07/13/2017 02:39 PM, Jan-Benedict Glaw wrote: > Hi Jan, > hi Kito, Palmer and Andrew! > > On Thu, 2017-06-29 14:27:41 +0200, Jan Hubicka wrote: >> this is second step of the profile maintenance revamp. It implements >> profile_probability type which is pretty much symmetric to profile_count >

Re: [BUILDROBOT] error: format ‘%d’ expects argument of type ‘int’, but argument 3 has type ‘long int’ (was: [PATCH] [ARC] Recognise add_n and sub_n in combine again)

2017-06-25 Thread Jan-Benedict Glaw
Hi Graham, On Mon, 2017-06-12 11:40:39 +0200, Jan-Benedict Glaw wrote: > On Fri, 2017-05-12 20:14:23 +0100, Graham Markall > wrote: > > Since the combine pass canonicalises shift-add insns using plus and > > ashift (as opposed to plus and mult which it previously used to do), it > > no longer c

Re: [BUILDROBOT] No rule to make target '/home/jbglaw/repos/gcc/gcc/config/rs6000/e500.h', needed by 's-gtype' (was: [PATCH 01/14] rs6000: Remove TARGET_FPRS)

2017-06-12 Thread Segher Boessenkool
Hi! On Mon, Jun 12, 2017 at 12:01:34PM +0200, Jan-Benedict Glaw wrote: > On Tue, 2017-06-06 15:56:17 +, Segher Boessenkool > wrote: > > Since rs6000 no longer supports SPE, TARGET_FPRS now always is true. > > > > This makes TARGET_{SF,DF}_SPE always false. Many patterns in spe.md > > can n

Re: [BUILDROBOT] Maybe uninitialized warnings in mips targets

2017-04-04 Thread Jeff Law
On 03/18/2017 12:20 PM, Jan-Benedict Glaw wrote: Hi Richard, Catherine, Matthew On Thu, 2017-03-02 14:40:46 +0100, Richard Biener wrote: [...] On IRC we decided to wait&see for the TREE_NO_WARNING issue. So the following is what I committed. Bootstrapped / tested on x86_64-unknown-linux-gnu.

Re: [BUILDROBOT] Maybe uninitialized warnings in mips targets

2017-03-19 Thread Jeff Law
On 03/18/2017 12:20 PM, Jan-Benedict Glaw wrote: Hi Richard, Catherine, Matthew On Thu, 2017-03-02 14:40:46 +0100, Richard Biener wrote: [...] On IRC we decided to wait&see for the TREE_NO_WARNING issue. So the following is what I committed. Bootstrapped / tested on x86_64-unknown-linux-gnu.

Re: [BUILDROBOT] arm-netbsdelf: Error during -fself-test (was: [PATCH] TS_OPTIMIZATION/TS_TARGET_OPTION need no chain/type)

2017-02-28 Thread Jan-Benedict Glaw
On Mon, 2017-02-27 09:19:51 +0100, Richard Biener wrote: > On Mon, 27 Feb 2017, Jan-Benedict Glaw wrote: > > On Wed, 2017-01-11 16:28:33 +0100, Richard Biener wrote: > > > On Wed, 11 Jan 2017, Richard Biener wrote: > > > > LTO bootstrapped on x86_64-unknown-linux-gnu, testing in progress. > > > >

Re: [BUILDROBOT] arm-netbsdelf: Error during -fself-test (was: [PATCH] TS_OPTIMIZATION/TS_TARGET_OPTION need no chain/type)

2017-02-27 Thread Richard Biener
On Mon, 27 Feb 2017, Jan-Benedict Glaw wrote: > Hi Richard, > > On Wed, 2017-01-11 16:28:33 +0100, Richard Biener wrote: > > On Wed, 11 Jan 2017, Richard Biener wrote: > > > LTO bootstrapped on x86_64-unknown-linux-gnu, testing in progress. > > > > > > (most "gross" are still TS_LIST having a t

Re: [BUILDROBOT] dwarf2out.c:22452:14: error: variable ‘origin_die’ set but not used [-Werror=unused-but-set-variable]

2016-11-01 Thread Jakub Jelinek
On Tue, Nov 01, 2016 at 11:34:08PM +0100, Jan-Benedict Glaw wrote: > Hi Jakub! > > Seems this patch caused some breakage when building via > config-list.mk with a recent compiler (ie. with itself) : > > +2016-11-01 Jakub Jelinek > + > + * dwarf2out.c (add_name_and_src_coords_attributes):

Re: [BUILDROBOT] [Ada] error: alignment of array elements is greater than element size (was: [PATCH] GIMPLE store merging pass)

2016-10-29 Thread Markus Trippelsdorf
On 2016.10.29 at 19:56 +0200, Jan-Benedict Glaw wrote: > Hi Kyrill! > > On Mon, 2016-10-24 15:56:48 +0100, Kyrill Tkachov > wrote: > > This is a slight update over [1] with Richard's feedback addressed. > > In terminate_all_aliasing_chains we now terminate the chain early if > > the destination

Re: [BUILDROBOT] Selftest failed for i686-wrs-vxworks

2016-10-12 Thread Thomas Schwinge
Hi! On Wed, 5 Oct 2016 16:36:01 +0200, Bernd Schmidt wrote: > On 10/05/2016 04:14 PM, David Malcolm wrote: > > Thanks. I'm not able to formally approve these changes, but FWIW these > > patches look good to me (assuming usual testing). > > LGTM too, so OK. Without changes, committed to trunk i

Re: [BUILDROBOT] Selftest failed for i686-wrs-vxworks

2016-10-05 Thread Bernd Schmidt
On 10/05/2016 04:14 PM, David Malcolm wrote: Thanks. I'm not able to formally approve these changes, but FWIW these patches look good to me (assuming usual testing). LGTM too, so OK. Bernd

Re: [BUILDROBOT] Selftest failed for i686-wrs-vxworks

2016-10-05 Thread David Malcolm
On Wed, 2016-10-05 at 14:34 +0200, Thomas Schwinge wrote: > Hi! > > I've now also run into this issue, during contrib/config-list.mk > testing; > log/arm-wrs-vxworks-make.out, log/i686-wrs-vxworks-make.out, > log/i686-wrs-vxworksae-make.out, log/mips-wrs-vxworks-make.out, > log/powerpc-wrs-vxworks

Re: [BUILDROBOT] Selftest failed for i686-wrs-vxworks

2016-10-05 Thread Thomas Schwinge
Hi! I've now also run into this issue, during contrib/config-list.mk testing; log/arm-wrs-vxworks-make.out, log/i686-wrs-vxworks-make.out, log/i686-wrs-vxworksae-make.out, log/mips-wrs-vxworks-make.out, log/powerpc-wrs-vxworks-make.out, log/powerpc-wrs-vxworksae-make.out, log/powerpc-wrs-vxworksmi

Re: [BUILDROBOT] dwarf2out_do_cfi_startproc(bool)’: may write a terminating nul past the end of the destination

2016-10-02 Thread Jason Merrill
OK. On Sat, Oct 1, 2016 at 4:30 PM, Jakub Jelinek wrote: > On Fri, Sep 30, 2016 at 08:59:52PM +0200, Jakub Jelinek wrote: >> Ok if it passes bootstrap/regtest? > > Passed bootstrap/regtest on x86_64-linux and i686-linux. >> >> 2016-09-30 Jakub Jelinek >> >> * dwarf2out.c (output_fde, out

Re: [BUILDROBOT] dwarf2out_do_cfi_startproc(bool)’: may write a terminating nul past the end of the destination

2016-10-01 Thread Jakub Jelinek
On Fri, Sep 30, 2016 at 08:59:52PM +0200, Jakub Jelinek wrote: > Ok if it passes bootstrap/regtest? Passed bootstrap/regtest on x86_64-linux and i686-linux. > > 2016-09-30 Jakub Jelinek > > * dwarf2out.c (output_fde, output_call_frame_info, > dwarf2out_do_cfi_startproc, set_indire

Re: [BUILDROBOT] dwarf2out_do_cfi_startproc(bool)’: may write a terminating nul past the end of the destination

2016-09-30 Thread Jakub Jelinek
On Fri, Sep 30, 2016 at 07:07:22PM +0200, Jan-Benedict Glaw wrote: > When building for --target=sparc-leon-elf (using config-list.mk) with > a current GCC, I get this error message (cf. > http://toolchain.lug-owl.de/buildbot/show_build_details.php?id=632317): > > g++ -fno-PIE -c -g -O2 -DIN_GCC

Re: [BUILDROBOT] tic6x-uclinux: undefined reference to `gnu_libc_printf_pointer_format(tree_node*, char const**)' (was: [PATCH] - improve sprintf buffer overflow detection (middle-end/49905))

2016-09-28 Thread Segher Boessenkool
On Tue, Sep 27, 2016 at 12:08:46AM +0200, Jan-Benedict Glaw wrote: > Hi Martin, > > On Thu, 2016-09-08 13:03:12 -0600, Martin Sebor wrote: > > Attached is another update to the patch to address the last round > > of comments and suggestions, most notably to: > [...] > > with the currently commit

Re: [BUILDROBOT] tic6x-uclinux: undefined reference to `gnu_libc_printf_pointer_format(tree_node*, char const**)'

2016-09-27 Thread Martin Sebor
On 09/26/2016 04:08 PM, Jan-Benedict Glaw wrote: Hi Martin, On Thu, 2016-09-08 13:03:12 -0600, Martin Sebor wrote: Attached is another update to the patch to address the last round of comments and suggestions, most notably to: [...] with the currently committed version, the tic6x-uclinux tar

Re: [BUILDROBOT] vax-netbsdelf / vax-linux: ‘ELIMINABLE_REGS’ was not declared in this scope

2016-09-20 Thread Jeff Law
On 09/19/2016 04:24 PM, Bernd Edlinger wrote: On 09/19/16 23:51, Jeff Law wrote: On 09/17/2016 05:29 PM, Bernd Edlinger wrote: On 09/17/16 22:29, Jan-Benedict Glaw wrote: On Fri, 2016-09-09 21:40:38 +, Bernd Edlinger wrote: Hi, I think it is time to remove support for INITIAL_FRAME_POIN

Re: [BUILDROBOT] vax-netbsdelf / vax-linux: ‘ELIMINABLE_REGS’ was not declared in this scope

2016-09-19 Thread Bernd Edlinger
On 09/19/16 23:51, Jeff Law wrote: > On 09/17/2016 05:29 PM, Bernd Edlinger wrote: >> On 09/17/16 22:29, Jan-Benedict Glaw wrote: >>> On Fri, 2016-09-09 21:40:38 +, Bernd Edlinger >>> wrote: Hi, I think it is time to remove support for INITIAL_FRAME_POINTER_OFFSET, which is

Re: [BUILDROBOT] vax-netbsdelf / vax-linux: ‘ELIMINABLE_REGS’ was not declared in this scope

2016-09-19 Thread Jeff Law
On 09/17/2016 05:29 PM, Bernd Edlinger wrote: On 09/17/16 22:29, Jan-Benedict Glaw wrote: On Fri, 2016-09-09 21:40:38 +, Bernd Edlinger wrote: Hi, I think it is time to remove support for INITIAL_FRAME_POINTER_OFFSET, which is no longer used by any target today. This removes a bunch of

Re: [BUILDROBOT] vax-netbsdelf / vax-linux: ‘ELIMINABLE_REGS’ was not declared in this scope

2016-09-17 Thread Bernd Edlinger
On 09/17/16 22:29, Jan-Benedict Glaw wrote: > On Fri, 2016-09-09 21:40:38 +, Bernd Edlinger > wrote: >> Hi, >> >> I think it is time to remove support for INITIAL_FRAME_POINTER_OFFSET, which >> is no longer >> used by any target today. This removes a bunch of conditional code, and >> fixes

Re: [BUILDROBOT] x86_64: Segmentation fault during -fself-test (was: Implement C _FloatN, _FloatNx types [version 6]

2016-08-22 Thread Joseph Myers
On Mon, 22 Aug 2016, Jan-Benedict Glaw wrote: > Between dee8cef0c1c1ebf85fceb5c37996ed12a2bec352 (Fri Aug 19 15:42:11 > 2016 +) and 82c85aba845985e55c27a7a9c448810d433adb17 (Fri Aug 19 > 17:43:26 2016 +), a new build regression for > x86_64-{linux,rtems,elf} showed up and I think this patc

Re: [BUILDROBOT] avr broken

2016-08-17 Thread Jan-Benedict Glaw
On Tue, 2016-08-16 14:26:38 -0400, Nathan Sidwell wrote: > On 08/16/16 13:04, Jan-Benedict Glaw wrote: > > > That'll probably work. But after all, I'm not an AVR maintainer > > (not even an user), but just running the Build Robot. > > Does your robot approve? :) Ohoooh! See there! :) http://to

Re: [BUILDROBOT] avr broken

2016-08-17 Thread Martin Liška
On 08/17/2016 09:20 AM, Denis Chertykov wrote: > 2016-08-16 21:26 GMT+03:00 Nathan Sidwell : >> On 08/16/16 13:04, Jan-Benedict Glaw wrote: >> >>> That'll probably work. But after all, I'm not an AVR maintainer (not >>> even an user), but just running the Build Robot. >> >> >> Does your robot appro

Re: [BUILDROBOT] avr broken

2016-08-17 Thread Denis Chertykov
2016-08-16 21:26 GMT+03:00 Nathan Sidwell : > On 08/16/16 13:04, Jan-Benedict Glaw wrote: > >> That'll probably work. But after all, I'm not an AVR maintainer (not >> even an user), but just running the Build Robot. > > > Does your robot approve? :) > I'm an AVR maintainer. The patch does not have

Re: [BUILDROBOT] avr broken

2016-08-16 Thread Nathan Sidwell
On 08/16/16 13:04, Jan-Benedict Glaw wrote: That'll probably work. But after all, I'm not an AVR maintainer (not even an user), but just running the Build Robot. Does your robot approve? :)

Re: [BUILDROBOT] avr broken

2016-08-16 Thread Jan-Benedict Glaw
On Tue, 2016-08-16 10:31:41 -0400, Nathan Sidwell wrote: > On 08/16/16 10:23, Martin Liška wrote: > > On 08/16/2016 03:36 PM, Nathan Sidwell wrote: > > > On 08/16/16 08:49, Martin Liška wrote: > > > > On 08/13/2016 02:14 PM, Jan-Benedict Glaw wrote: > > > > > This doesn't work for AVR since their

Re: [BUILDROBOT] avr broken

2016-08-16 Thread Nathan Sidwell
On 08/16/16 10:23, Martin Liška wrote: On 08/16/2016 03:36 PM, Nathan Sidwell wrote: On 08/16/16 08:49, Martin Liška wrote: On 08/13/2016 02:14 PM, Jan-Benedict Glaw wrote: This doesn't work for AVR since their LONG_LONG_TYPE_SIZE depents on target flags (see eg. build http://toolchain.lug-owl

Re: [BUILDROBOT] avr broken

2016-08-16 Thread Nathan Sidwell
On 08/16/16 08:49, Martin Liška wrote: On 08/13/2016 02:14 PM, Jan-Benedict Glaw wrote: This doesn't work for AVR since their LONG_LONG_TYPE_SIZE depents on target flags (see eg. build http://toolchain.lug-owl.de/buildbot/show_build_details.php?id=602648) Hello. Sorry for the breakage, I have

Re: [BUILDROBOT] Selftest failed for i686-wrs-vxworks

2016-07-06 Thread Jan-Benedict Glaw
On Thu, 2016-06-30 16:09:23 -0400, David Malcolm wrote: > On Thu, 2016-06-30 at 08:38 -0400, Nathan Sidwell wrote: > > > I haven't given it any additional manual testing so far. It's > > > pre-installation though. Maybe I'd just set WIND_BASE to some > > > arbitrary value, just to make xgcc pass i

Re: [BUILDROBOT] Selftest failed for i686-wrs-vxworks

2016-06-30 Thread David Malcolm
On Thu, 2016-06-30 at 08:38 -0400, Nathan Sidwell wrote: > Jan-Benedict, > > > I haven't given it any additional manual testing so far. It's > > pre-installation though. Maybe I'd just set WIND_BASE to some > > arbitrary value, just to make xgcc pass it's initial start-up test > > so > > that it c

Re: [BUILDROBOT] Selftest failed for i686-wrs-vxworks

2016-06-30 Thread Nathan Sidwell
Jan-Benedict, I haven't given it any additional manual testing so far. It's pre-installation though. Maybe I'd just set WIND_BASE to some arbitrary value, just to make xgcc pass it's initial start-up test so that it can continue with self-testing? Or shall we set some value in gcc/Makefile.in fo

Re: [BUILDROBOT] Selftest failed for rs6000-ibm-aix4.3

2016-06-19 Thread David Edelsohn
On Sat, Jun 18, 2016 at 9:56 AM, David Malcolm wrote: > On Sat, 2016-06-18 at 15:06 +0200, Jan-Benedict Glaw wrote: >> Hi David, Segher, Aldy! >> >> Davids new selftest code found something for the rs6000-ibm-aix4.3 >> target, maybe you're interested: >> >> /home/jbglaw/src/toolchain/build/./gcc/x

Re: [BUILDROBOT] Selftest failed for rs6000-ibm-aix4.3

2016-06-18 Thread David Malcolm
On Sat, 2016-06-18 at 15:06 +0200, Jan-Benedict Glaw wrote: > Hi David, Segher, Aldy! > > Davids new selftest code found something for the rs6000-ibm-aix4.3 > target, maybe you're interested: > > /home/jbglaw/src/toolchain/build/./gcc/xgcc > -B/home/jbglaw/src/toolchain/build/./gcc/ -xc -S -c /d

Re: [BUILDROBOT] MPS430 build problem due to new enum

2016-06-13 Thread Martin Liška
On 06/13/2016 10:46 AM, Jan Hubicka wrote: > Hmm, namespace conflict. I guess renaming enum items to REASON_* should > solve it easily. > Or we can add a namespace. > > Martin, both variants of fix are pre-approved. > Honza OK, I've just installed (r237370) a patch that prefixes all enum values

Re: [BUILDROBOT] MPS430 build problem due to new enum (was: [PATCH 2/2] Add edge predictions pruning)

2016-06-13 Thread Jan Hubicka
> Hi Martin, > > On Thu, 2016-06-09 13:24:10 +0200, Martin Liška wrote: > > On 06/08/2016 02:41 PM, Jan Hubicka wrote: > > > Adding hash for this prupose is bit of an overkill (there are > > > definitly cheaper ways of solving so), but it will hardly affect compile > > > time, so the pathc is OK.

Re: [BUILDROBOT] MPS430 build problem due to new enum

2016-06-13 Thread Martin Liška
On 06/12/2016 01:55 PM, Jan-Benedict Glaw wrote: > The new `NONE' from your enum clashes with a NONE used in a MSP430 > private enum. > > MfG, JBG Hi. Thanks for having heads up, I've been testing following patch. The patch survives with --target=msp430-elf. Ready after it finishes? Thanks, Mar

RE: [BUILDROBOT] "error: null argument where non-null required" on multiple targets

2015-12-21 Thread Moore, Catherine
than Wakely; > gcc-patches > Subject: Re: [BUILDROBOT] "error: null argument where non-null required" > on multiple targets > > On 12/16/2015 03:46 AM, Jan-Benedict Glaw wrote: > > On Tue, 2015-12-15 10:43:58 -0700, Jeff Law wrote: > >> On 12/14/2015 01:07 P

Re: [BUILDROBOT] "error: null argument where non-null required" on multiple targets

2015-12-17 Thread Jeff Law
On 12/16/2015 03:46 AM, Jan-Benedict Glaw wrote: On Tue, 2015-12-15 10:43:58 -0700, Jeff Law wrote: On 12/14/2015 01:07 PM, Jan-Benedict Glaw wrote: On Mon, 2015-12-14 18:54:28 +, Moore, Catherine wrote: avr-rtems http://toolchain.lug-owl.de/buildbot/show_build_details.ph

Re: [BUILDROBOT] "error: null argument where non-null required" on multiple targets

2015-12-16 Thread Jan-Benedict Glaw
On Tue, 2015-12-15 10:43:58 -0700, Jeff Law wrote: > On 12/14/2015 01:07 PM, Jan-Benedict Glaw wrote: > >On Mon, 2015-12-14 18:54:28 +, Moore, Catherine > > wrote: > >>>avr-rtems > >>>http://toolchain.lug-owl.de/buildbot/show_build_details.php?id=478544 > >>>mipsel-elf > >>

Re: [BUILDROBOT] "error: null argument where non-null required" on multiple targets

2015-12-15 Thread Jeff Law
On 12/14/2015 01:07 PM, Jan-Benedict Glaw wrote: On Mon, 2015-12-14 18:54:28 +, Moore, Catherine wrote: avr-rtems http://toolchain.lug-owl.de/buildbot/show_build_details.php?id=478544 mipsel-elf http://toolchain.lug-owl.de/buildbot/show_build_details.php?id=478

Re: [BUILDROBOT] "error: null argument where non-null required" on multiple targets

2015-12-14 Thread Jan-Benedict Glaw
On Mon, 2015-12-14 18:54:28 +, Moore, Catherine wrote: > > avr-rtems > > http://toolchain.lug-owl.de/buildbot/show_build_details.php?id=478544 > > mipsel-elf > > http://toolchain.lug-owl.de/buildbot/show_build_details.php?id=478844 > > mipsisa64r2-sde-elf > > http://tool

RE: [BUILDROBOT] "error: null argument where non-null required" on multiple targets

2015-12-14 Thread Moore, Catherine
> -Original Message- > From: Jan-Benedict Glaw [mailto:jbg...@lug-owl.de] > Sent: Sunday, December 06, 2015 4:49 PM > To: Denis Chertykov; Moore, Catherine; Eric Christopher; Matthew Fortune; > David Edelsohn; Alexandre Oliva; Kaz Kojima; Oleg Endo > Cc: Jonathan Wakely; gcc-patches > Sub

Re: [BUILDROBOT] ./insn-flags.h:342:7: error: ‘operands’ was not declared in this scope

2015-12-06 Thread Kaz Kojima
Jan-Benedict Glaw wrote: > shle-linux breaks with: > > g++ -fno-PIE -c -g -O2 -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE > -fno-exceptions -fno-rtti -fasynchronous-unwind-tables -W -Wall > -Wno-narrowing -Wwrite-strings -Wcast-qual -Wmissing-format-attribute > -Woverloaded-virtual -pedantic -Wn

Re: [BUILDROBOT] Bootstrap broken in Ada

2015-10-11 Thread Jan Hubicka
> On 10/11/2015 02:58 PM, Jan-Benedict Glaw wrote: > >On Thu, 2015-10-08 09:37:03 -0400, Andrew MacLeod > >wrote: > >[...] > >>Heres the patch for reordered headers. Building as we speak. Hard to fully > >>verify since Ada doesn't seem to bootstrap on trunk at the moment: > >> > >>+

Re: [BUILDROBOT] Bootstrap broken in Ada

2015-10-11 Thread Jeff Law
On 10/11/2015 02:58 PM, Jan-Benedict Glaw wrote: On Thu, 2015-10-08 09:37:03 -0400, Andrew MacLeod wrote: [...] Heres the patch for reordered headers. Building as we speak. Hard to fully verify since Ada doesn't seem to bootstrap on trunk at the moment: +===GNAT BUG D

[commit, spu] Re: [BUILDROBOT] spu: left shift of negative value

2015-09-21 Thread Ulrich Weigand
Jan-Benedict Glaw wrote: > I just noticed that (for config_list.mk builds), current GCC errors > out at spu.c, see eg. build > http://toolchain.lug-owl.de/buildbot/show_build_details.php?id=3D469639 : > > g++ -fno-PIE -c -g -O2 -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE -fno-excep= > tions -fno-rt

Re: [BUILDROBOT] Go runtime: calling ‘__builtin_frame_address’ with a nonzero argument is unsafe

2015-08-03 Thread Jeff Law
On 08/03/2015 08:48 AM, Martin Sebor wrote: On 08/03/2015 05:55 AM, Jan-Benedict Glaw wrote: On Sun, 2015-08-02 17:15:27 -0600, Martin Sebor wrote: OK for the trunk. Sorry for the delay. Thank you. Committed in revision 226480. ...und breaks native builds. When doing builds using config-l

Re: [BUILDROBOT] Go runtime: calling ‘__builtin_frame_address’ with a nonzero argument is unsafe

2015-08-03 Thread Martin Sebor
On 08/03/2015 05:55 AM, Jan-Benedict Glaw wrote: On Sun, 2015-08-02 17:15:27 -0600, Martin Sebor wrote: OK for the trunk. Sorry for the delay. Thank you. Committed in revision 226480. ...und breaks native builds. When doing builds using config-list.mk, I first build a GCC for the build mac

Re: [BUILDROBOT]

2015-06-08 Thread Andreas Krebbel
On 06/05/2015 01:04 AM, Jan-Benedict Glaw wrote: > Hi Andreas, > > On Mon, 2015-05-11 15:23:33 +0200, Andreas Krebbel > wrote: >> gcc/ >> * config/s390/constraints.md (j00, jm1, jxx, jyy, v): New >> constraints. >> * config/s390/predicates.md (const0_operand, constm1_operand) >>

Re: [BUILDROBOT] arc-elf: match_code "REG" matches nothing

2015-06-02 Thread Richard Sandiford
Jan-Benedict Glaw writes: > On Fri, 2015-05-22 16:42:44 +0100, Richard Sandiford > wrote: >> This patch adjusts the fix for PR target/65689 along the lines suggested >> in https://gcc.gnu.org/ml/gcc-patches/2015-04/msg01559.html. The idea >> is to reuse the existing gensupport.c routine to work

Re: [BUILDROBOT] RFA: RL78: Add support for G13 and G14 multiply and divide

2015-04-23 Thread Nicholas Clifton
Hi Jan-Benedict. ../../../gcc/gcc/config/rl78/rl78.c:390:14: error: enumeration value ‘MUL_RL78’ not handled in switch [-Werror=switch] switch (rl78_mul_type) ../../../gcc/gcc/config/rl78/rl78.c:4649:34: error: unused parameter ‘x’ [-Werror=unused-parameter] rl78_preferred_reload_

Re: [BUILDROBOT] tilepro-linux/tilegx-linux fallout from flattening

2015-01-11 Thread Prathamesh Kulkarni
On 12 January 2015 at 11:19, Michael Collison wrote: > The issue is that tilegx includes expr.h which includes tree-core.h. A > simple solution is to include "symtab.h" before "expr.h" in tilegx.c. The > port has a unrelated link error after this change. Yes, I am seeing this link error after buil

Re: [BUILDROBOT] tilepro-linux/tilegx-linux fallout from flattening

2015-01-11 Thread Michael Collison
The issue is that tilegx includes expr.h which includes tree-core.h. A simple solution is to include "symtab.h" before "expr.h" in tilegx.c. The port has a unrelated link error after this change. The second possiblity is to resolve this using Prathmesh latest patch (submitted today) for flatte

Re: [BUILDROBOT, PATCH] config-list.mk: Extract target name correctly

2015-01-05 Thread Jeff Law
On 12/29/14 13:02, Jan-Benedict Glaw wrote: Hi! With my last change, `sed' is used to cut out the target name from a listed target. Since there may be additional OPTions encoded in the "target", I tried to get only the first submatch before an `OPT'. However, `sed' uses longest match, so I'm re-

Re: [BUILDROBOT, PATCH] MSP430: Fix unused arg warning

2014-12-17 Thread Jan-Benedict Glaw
Hi Nick, On Wed, 2014-12-17 17:05:09 +, Nicholas Clifton wrote: > > 2014-12-17 Jan-Benedict Glaw > > > > * config/msp430/msp430.c (msp430_asm_output_addr_const_extra): Fix > > unused argument warning. > > Approved - please apply. Thanks. Committed as r218828. MfG, JBG --

Re: [BUILDROBOT, PATCH] MSP430: Fix unused arg warning

2014-12-17 Thread Nicholas Clifton
Hi Jan-Benedict, 2014-12-17 Jan-Benedict Glaw * config/msp430/msp430.c (msp430_asm_output_addr_const_extra): Fix unused argument warning. Approved - please apply. Cheers Nick

Re: [BUILDROBOT] nios2: build breakage

2014-11-19 Thread Sandra Loosemore
On 11/19/2014 09:34 PM, Jan Hubicka wrote: [snip] I see three possible fixes: 1) extend the AWk script to recognize arrays and stream them specially (it already recognizes string so it is not hard to do, just bit wasteful) 2) add attribute to .opt file allowing user to specify his own

Re: [BUILDROBOT] nios2: build breakage

2014-11-19 Thread Jan Hubicka
Sandra, > > > >I can explain why this is needed, at least. > > > >The Nios II architecture optionally allows "custom instructions" that > >are typically used to implement floating-point operations. The nios2 > >GCC backend knows to generate these instructions if the user tells it > >what opcodes i

Re: [BUILDROBOT] nios2: build breakage

2014-11-19 Thread Sandra Loosemore
On 11/15/2014 06:46 PM, Sandra Loosemore wrote: On 11/15/2014 04:49 PM, Jan-Benedict Glaw wrote: Hi, On Sun, 2014-11-16 00:36:27 +0100, Jan Hubicka wrote: Yep, it is because my code does not handle streaming of arrays into the target optimization nodes. I will take a look on why that array i

Re: [BUILDROBOT] Build breakage in builtin.c (was: [PATCH, Pointer Bounds Checker, Builtins instrumentation 3/5] Expand instrumented builtin calls)

2014-11-17 Thread Jan-Benedict Glaw
On Mon, 2014-11-17 19:17:34 +0300, Ilya Enkovich wrote: > On 17 Nov 16:12, Jan-Benedict Glaw wrote: > > On Mon, 2014-11-17 15:59:41 +0100, Markus Trippelsdorf > > wrote: > > > On 2014.11.17 at 15:52 +0100, Jan-Benedict Glaw wrote: > > > > On Thu, 2014-11-06 15:24:59 +0300, Ilya Enkovich > > > >

Re: [BUILDROBOT] Build breakage in builtin.c (was: [PATCH, Pointer Bounds Checker, Builtins instrumentation 3/5] Expand instrumented builtin calls)

2014-11-17 Thread Ilya Enkovich
On 17 Nov 16:12, Jan-Benedict Glaw wrote: > On Mon, 2014-11-17 15:59:41 +0100, Markus Trippelsdorf > wrote: > > On 2014.11.17 at 15:52 +0100, Jan-Benedict Glaw wrote: > > > On Thu, 2014-11-06 15:24:59 +0300, Ilya Enkovich > > > wrote: > [...] > > > It seems this part of the patch series causes

Re: [BUILDROBOT] Build breakage in builtin.c (was: [PATCH, Pointer Bounds Checker, Builtins instrumentation 3/5] Expand instrumented builtin calls)

2014-11-17 Thread Jan-Benedict Glaw
On Mon, 2014-11-17 15:59:41 +0100, Markus Trippelsdorf wrote: > On 2014.11.17 at 15:52 +0100, Jan-Benedict Glaw wrote: > > On Thu, 2014-11-06 15:24:59 +0300, Ilya Enkovich > > wrote: [...] > > It seems this part of the patch series causes some build breakage > > right now, see eg. build > > htt

Re: [BUILDROBOT] Build breakage in builtin.c (was: [PATCH, Pointer Bounds Checker, Builtins instrumentation 3/5] Expand instrumented builtin calls)

2014-11-17 Thread Markus Trippelsdorf
On 2014.11.17 at 15:52 +0100, Jan-Benedict Glaw wrote: > On Thu, 2014-11-06 15:24:59 +0300, Ilya Enkovich > wrote: > > Hi, > > > > This patch adds support of instrumented builtin calls in expand. > > Calls are mostly expanded as calls. But some of them reuse existing > > string function calls e

Re: [BUILDROBOT] nios2: build breakage

2014-11-15 Thread Sandra Loosemore
On 11/15/2014 04:49 PM, Jan-Benedict Glaw wrote: Hi, On Sun, 2014-11-16 00:36:27 +0100, Jan Hubicka wrote: Yep, it is because my code does not handle streaming of arrays into the target optimization nodes. I will take a look on why that array is really needed. It seems like a overkill? I am

Re: [BUILDROBOT] error: �??cl_target_option_stream_in�?? was not declared in this scope (was: LTO streaming of TARGET_OPTIMIZE_NODE)

2014-11-15 Thread Jan-Benedict Glaw
On Fri, 2014-11-14 19:53:33 +0100, Jan Hubicka wrote: > > Breaks build: > > > > g++ -c -g -O2 -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE -fno-exceptions > > -fno-rtti -fasynchronous-unwind-tables -W -Wall -Wno-narrowing > > -Wwrite-strings -Wcast-qual -Wmissing-format-attribute -Woverloaded-virtu

Re: [BUILDROBOT] error: �??cl_target_option_stream_in�?? was not declared in this scope (was: LTO streaming of TARGET_OPTIMIZE_NODE)

2014-11-14 Thread Jan Hubicka
> > Breaks build: > > g++ -c -g -O2 -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE -fno-exceptions > -fno-rtti -fasynchronous-unwind-tables -W -Wall -Wno-narrowing > -Wwrite-strings -Wcast-qual -Wmissing-format-attribute -Woverloaded-virtual > -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overl

RE: [BUILDROBOT] s390x-linux: Breaking in ifcvt.c (was: [PATCH, ifcvt] Allow CC mode if HAVE_cbranchcc4)

2014-11-03 Thread Zhenqiang Chen
Krebbel > Cc: 'Richard Henderson'; gcc-patches@gcc.gnu.org > Subject: Re: [BUILDROBOT] s390x-linux: Breaking in ifcvt.c (was: [PATCH, > ifcvt] > Allow CC mode if HAVE_cbranchcc4) > > On Mon, 2014-11-03 11:06:06 +0100, Jan-Benedict Glaw > wrote: > > On Wed, 2

RE: [BUILDROBOT] s390x-linux: Breaking in ifcvt.c (was: [PATCH, ifcvt] Allow CC mode if HAVE_cbranchcc4)

2014-11-03 Thread Zhenqiang Chen
> -Original Message- > From: Jan-Benedict Glaw [mailto:jbg...@lug-owl.de] > Sent: Monday, November 03, 2014 6:16 PM > To: Zhenqiang Chen; Hartmut Penner; Ulrich Weigand; Andreas Krebbel > Cc: 'Richard Henderson'; gcc-patches@gcc.gnu.org > Subject: Re: [BUILD

Re: [BUILDROBOT] s390x-linux: Breaking in ifcvt.c (was: [PATCH, ifcvt] Allow CC mode if HAVE_cbranchcc4)

2014-11-03 Thread Jan-Benedict Glaw
On Mon, 2014-11-03 11:06:06 +0100, Jan-Benedict Glaw wrote: > On Wed, 2014-10-29 18:27:57 +0800, Zhenqiang Chen > wrote: > > Hi, > > > > The patch enhances ifcvt to allow_cc_mode if HAVE_cbranchcc4. > > > > Bootstrap and no make check regression on X86-64. > > Will add new test cases after ccm

Re: [BUILDROBOT] s390x-linux: Breaking in ifcvt.c (was: [PATCH, ifcvt] Allow CC mode if HAVE_cbranchcc4)

2014-11-03 Thread Jakub Jelinek
On Mon, Nov 03, 2014 at 11:06:06AM +0100, Jan-Benedict Glaw wrote: > On Wed, 2014-10-29 18:27:57 +0800, Zhenqiang Chen > wrote: > > Hi, > > > > The patch enhances ifcvt to allow_cc_mode if HAVE_cbranchcc4. > > > > Bootstrap and no make check regression on X86-64. > > Will add new test cases aft

Re: [BUILDROBOT] genrecog fix uncovers problem in bfin.md (was: [Patch] Teach genrecog/genoutput that scratch registers require write constraint modifiers)

2014-09-22 Thread Jan-Benedict Glaw
On Mon, 2014-09-22 08:58:34 +0100, James Greenhalgh wrote: > On Sat, Sep 20, 2014 at 08:40:01PM +0100, Jan-Benedict Glaw wrote: > > My build robot shows a new build error, which I guess is > > caused/uncovered by your genrecog change on bfin-elf (see eg. build > > http://toolchain.lug-owl.de/buil

Re: [BUILDROBOT] genrecog fix uncovers problem in bfin.md (was: [Patch] Teach genrecog/genoutput that scratch registers require write constraint modifiers)

2014-09-22 Thread James Greenhalgh
On Sat, Sep 20, 2014 at 08:40:01PM +0100, Jan-Benedict Glaw wrote: > Hi! > > On Thu, 2014-09-18 11:19:21 +0100, James Greenhalgh > wrote: > > As discussed in https://gcc.gnu.org/ml/gcc-patches/2014-09/msg01334.html > > The construct > > > > (clobber (match_scratch 0 "r")) > > > > is invalid

Re: [BUILDROBOT] [PATCH] rx-elf: error: logical not is only applied to the left hand side of comparison

2014-09-08 Thread Nicholas Clifton
Hi Jan-Benedict, 2014-09-04 Jan-Benedict Glaw * config/rx/rx.h (HARD_REGNO_MODE_OK): Add braces. Approved - please apply - thanks! Cheers Nick

Re: [BUILDROBOT] [PATCH] rx-elf: error: logical not is only applied to the left hand side of comparison

2014-09-04 Thread Richard Biener
On Thu, Sep 4, 2014 at 10:48 AM, Jan-Benedict Glaw wrote: > Hi! > > -Wlogical-not-parentheses was enabled recently via -Wall, and it > triggered for rx-elf > (http://toolchain.lug-owl.de/buildbot/show_build_details.php?id=350506) > on a build with config-list.mk, where a GCC of the same revision i

Re: [BUILDROBOT][PATCH] Fix warnings in the mep-elf target

2014-08-28 Thread Jan-Benedict Glaw
On Thu, 2014-08-28 15:47:07 -0700, Andrew Pinski wrote: > On Thu, Aug 28, 2014 at 3:00 PM, Jan-Benedict Glaw wrote: > > The following patch silences two warnings in the mep-elf target, > > fixing the config-list.mk build: > > > I thought -Werror was only on when the versions of GCC match. See

Re: [BUILDROBOT][PATCH] Fix warnings in the mep-elf target

2014-08-28 Thread Jan-Benedict Glaw
On Thu, 2014-08-28 15:47:07 -0700, Andrew Pinski wrote: > On Thu, Aug 28, 2014 at 3:00 PM, Jan-Benedict Glaw wrote: > > Hi! > > > > The following patch silences two warnings in the mep-elf target, > > fixing the config-list.mk build: > > > I thought -Werror was only on when the versions of GCC

Re: [BUILDROBOT][PATCH] Fix warnings in the mep-elf target

2014-08-28 Thread DJ Delorie
> This patch should fix it. Okay to apply? Ok. Thanks! > 2014-08-28 Jan-Benedict Glaw > > * config/mep/mep-pragma.c (mep_pragma_coprocessor_subclass): Rework > to silence warning. > * config/mep/mep.c (VECTOR_TYPE_P): Remove duplicate definition.

Re: [BUILDROBOT][PATCH] Fix warnings in the mep-elf target

2014-08-28 Thread Andrew Pinski
On Thu, Aug 28, 2014 at 3:00 PM, Jan-Benedict Glaw wrote: > Hi! > > The following patch silences two warnings in the mep-elf target, > fixing the config-list.mk build: I thought -Werror was only on when the versions of GCC match. Thanks, Andrew > > > First one: > ~~ > g++ -c -DIN_GCC_

Re: [BUILDROBOT][PATCH] frv-linux fallout (was: [PATCH 009/236] Replace BB_HEAD et al macros with functions)

2014-08-25 Thread Mike Stump
On Aug 25, 2014, at 12:45 PM, Steven Bosscher wrote: > On Mon, Aug 25, 2014 at 9:29 PM, Mike Stump wrote: >> On Aug 25, 2014, at 7:08 AM, David Malcolm wrote: >>> It's too late now to switch to this approach, so in the meantime I've >>> been working on ways to make my bootstraps as fast as possibl

Re: [BUILDROBOT][PATCH] frv-linux fallout (was: [PATCH 009/236] Replace BB_HEAD et al macros with functions)

2014-08-25 Thread Steven Bosscher
On Mon, Aug 25, 2014 at 9:29 PM, Mike Stump wrote: > On Aug 25, 2014, at 7:08 AM, David Malcolm wrote: >> It's too late now to switch to this approach, so in the meantime I've >> been working on ways to make my bootstraps as fast as possible. > > -j64 works wonders. :-) Though, it is annoying wat

Re: [BUILDROBOT][PATCH] frv-linux fallout (was: [PATCH 009/236] Replace BB_HEAD et al macros with functions)

2014-08-25 Thread Mike Stump
On Aug 25, 2014, at 7:08 AM, David Malcolm wrote: > > I'm testing and committing individual patches, but this > could have gone into trunk in one go. Yeah, it’s a hard choice between bit rot and incrementally going in. > what I realize now is that I should have > continued rebasing my patches i

Re: [BUILDROBOT][PATCH] ppc{,64}-linux broken (IPA C++ refactoring 4/N)

2014-08-25 Thread Jan-Benedict Glaw
On Mon, 2014-08-25 18:09:09 +0200, Martin Liška wrote: > On 08/25/2014 05:29 PM, Jan-Benedict Glaw wrote: > > Your recent change left one cgraph_state in place in the rs6000 > > backend, resulting in (see > > http://toolchain.lug-owl.de/buildbot/show_build_details.php?id=346638 > > and > > http://

Re: [BUILDROBOT][PATCH] ppc{,64}-linux broken (IPA C++ refactoring 4/N)

2014-08-25 Thread Martin Liška
On 08/25/2014 05:29 PM, Jan-Benedict Glaw wrote: Hi! Your recent change left one cgraph_state in place in the rs6000 backend, resulting in (see http://toolchain.lug-owl.de/buildbot/show_build_details.php?id=346638 and http://toolchain.lug-owl.de/buildbot/show_build_details.php?id=346630): g++

Re: [BUILDROBOT][PATCH] ppc{,64}-linux broken (IPA C++ refactoring 4/N)

2014-08-25 Thread Jan-Benedict Glaw
On Mon, 2014-08-25 11:44:58 -0400, David Edelsohn wrote: > 2014-08.25 Jan-Benedict Glaw > > * config/rs6000/rs6000.c (rs6000_return_in_msb): Fix fallout from > cgraph_state conversion. > > > The patch seems reasonable to me based on the other changes. Committed as r214429. MfG, JBG --

Re: [BUILDROBOT][PATCH] ppc{,64}-linux broken (IPA C++ refactoring 4/N)

2014-08-25 Thread David Edelsohn
2014-08.25 Jan-Benedict Glaw * config/rs6000/rs6000.c (rs6000_return_in_msb): Fix fallout from cgraph_state conversion. The patch seems reasonable to me based on the other changes. Thanks, David

Re: [BUILDROBOT][PATCH] frv-linux fallout (was: [PATCH 009/236] Replace BB_HEAD et al macros with functions)

2014-08-25 Thread David Malcolm
On Sat, 2014-08-23 at 20:49 +0200, Jan-Benedict Glaw wrote: > On Wed, 2014-08-06 13:19:48 -0400, David Malcolm wrote: > > This is further scaffolding; convert the BB_* and SET_BB_* macros > > into functions. Convert the BB_* rvalue-style functions into returning > > rtx_insn * rather than plain r

Re: werror fallout for cross-builds (was: Re: [BUILDROBOT][PATCH] Fix mmix (unused variable))

2014-08-22 Thread Jan-Benedict Glaw
On Sat, 2014-07-26 13:31:42 -0400, Hans-Peter Nilsson wrote: > On Fri, 25 Jul 2014, Hans-Peter Nilsson wrote: > > Anyway, on to the point of this message: by the quoted list it > > seems you have a local host called pluto using 4.9.1 as the host > > gcc for some build; does config-list.mk work for

Re: werror fallout for cross-builds (was: Re: [BUILDROBOT][PATCH] Fix mmix (unused variable))

2014-07-26 Thread Hans-Peter Nilsson
On Fri, 25 Jul 2014, Hans-Peter Nilsson wrote: > Anyway, on to the point of this message: by the quoted list it > seems you have a local host called pluto using 4.9.1 as the host > gcc for some build; does config-list.mk work for that? Never mind, I found a 4.9.1 installation on gcc110 and the ans

Re: werror fallout for cross-builds (was: Re: [BUILDROBOT][PATCH] Fix mmix (unused variable))

2014-07-25 Thread Hans-Peter Nilsson
On Fri, 25 Jul 2014, Jan-Benedict Glaw wrote: > On Thu, 2014-07-24 16:30:13 -0400, Hans-Peter Nilsson > wrote: > > On Thu, 24 Jul 2014, Jan-Benedict Glaw wrote: > > > On Tue, 2014-07-22 16:40:31 -0400, Hans-Peter Nilsson > > > wrote: > > > > Jan-Benedict, which host gcc version do you use when

Re: werror fallout for cross-builds (was: Re: [BUILDROBOT][PATCH] Fix mmix (unused variable))

2014-07-25 Thread Jan-Benedict Glaw
On Thu, 2014-07-24 16:30:13 -0400, Hans-Peter Nilsson wrote: > On Thu, 24 Jul 2014, Jan-Benedict Glaw wrote: > > On Tue, 2014-07-22 16:40:31 -0400, Hans-Peter Nilsson > > wrote: > > > Jan-Benedict, which host gcc version do you use when getting > > > most targets to build with config-list.mk? M

Re: werror fallout for cross-builds (was: Re: [BUILDROBOT][PATCH] Fix mmix (unused variable))

2014-07-24 Thread Hans-Peter Nilsson
On Thu, 24 Jul 2014, Jan-Benedict Glaw wrote: > On Tue, 2014-07-22 16:40:31 -0400, Hans-Peter Nilsson > wrote: > > Jan-Benedict, which host gcc version do you use when getting > > most targets to build with config-list.mk? Maybe we can just > > set the initial version to that instead of 4.4.4. >

Re: werror fallout for cross-builds (was: Re: [BUILDROBOT][PATCH] Fix mmix (unused variable))

2014-07-24 Thread Maciej W. Rozycki
On Tue, 22 Jul 2014, Mike Stump wrote: > Then I’m shadow boxing. I assumed that people wanted to turn it on by > default. I’m all for that, I think it is a good idea and a fine > direction. :-) The only limitation is whitelisting exactly when it > pops on and preflighting those at least onc

Re: werror fallout for cross-builds (was: Re: [BUILDROBOT][PATCH] Fix mmix (unused variable))

2014-07-23 Thread Jan-Benedict Glaw
On Tue, 2014-07-22 16:40:31 -0400, Hans-Peter Nilsson wrote: > In the name of "dealing with the fallout": with the patch below > (don't forget to re-generate configure) I get build errors in > generic code r212915 for *both* x86_64 "gcc version 4.7.2 > 20120921 (Red Hat 4.7.2-2) (GCC)" for mmix-kn

Re: werror fallout for cross-builds (was: Re: [BUILDROBOT][PATCH] Fix mmix (unused variable))

2014-07-22 Thread Mike Stump
On Jul 22, 2014, at 6:22 PM, Hans-Peter Nilsson wrote: > Note that I didn't actually ask for approval. Then I’m shadow boxing. I assumed that people wanted to turn it on by default. I’m all for that, I think it is a good idea and a fine direction. :-) The only limitation is whitelisting exa

Re: werror fallout for cross-builds (was: Re: [BUILDROBOT][PATCH] Fix mmix (unused variable))

2014-07-22 Thread Hans-Peter Nilsson
On Tue, 22 Jul 2014, Mike Stump wrote: > On Jul 22, 2014, at 1:40 PM, Hans-Peter Nilsson wrote: > > > > *Developers* (or rather, people cross-building non-released gcc > > source in their usual setup) don't use the fairly old or even > > broken host gcc versions that can be expected in use in the

Re: werror fallout for cross-builds (was: Re: [BUILDROBOT][PATCH] Fix mmix (unused variable))

2014-07-22 Thread Mike Stump
On Jul 22, 2014, at 1:40 PM, Hans-Peter Nilsson wrote: > > *Developers* (or rather, people cross-building non-released gcc > source in their usual setup) don't use the fairly old or even > broken host gcc versions that can be expected in use in the > general public (well, the users that still wan

  1   2   >