From owner-freebsd-ppc@freebsd.org Sun Jun 26 23:22:51 2016 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7F835B80CAA for ; Sun, 26 Jun 2016 23:22:51 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-211-153.reflexion.net [208.70.211.153]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 361E32FA2 for ; Sun, 26 Jun 2016 23:22:50 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 3193 invoked from network); 26 Jun 2016 23:23:20 -0000 Received: from unknown (HELO mail-cs-01.app.dca.reflexion.local) (10.81.19.1) by 0 (rfx-qmail) with SMTP; 26 Jun 2016 23:23:20 -0000 Received: by mail-cs-01.app.dca.reflexion.local (Reflexion email security v7.90.3) with SMTP; Sun, 26 Jun 2016 19:23:29 -0400 (EDT) Received: (qmail 28097 invoked from network); 26 Jun 2016 23:23:28 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 26 Jun 2016 23:23:28 -0000 X-No-Relay: not in my network Received: from [192.168.0.105] (ip70-189-131-151.lv.lv.cox.net [70.189.131.151]) by iron2.pdx.net (Postfix) with ESMTPSA id 2CE1CB1E001 for ; Sun, 26 Jun 2016 16:22:38 -0700 (PDT) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: Re: svn commit: r302214 - head/sys/powerpc/aim [my PowerMac G5 testing delayed] Message-Id: Date: Sun, 26 Jun 2016 16:22:41 -0700 To: FreeBSD PowerPC ML Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Jun 2016 23:22:51 -0000 Quoting: > Author: nwhitehorn > Date: Sun Jun 26 18:43:42 2016 > New Revision: 302214 > URL:=20 > https://svnweb.freebsd.org/changeset/base/302214 >=20 >=20 > Log: > Enter 64-bit mode as early as possible in the 64-bit PowerPC boot = sequence. > Most of the effect of setting MSR[SF] is that the CPU will stop = ignoring > the high 32 bits of registers containing addresses in load/store > instructions. As such, the kernel was setting it only when it began = to > need access to high memory. MSR[SF] also affects the operation of = some > conditional instructions, however, and so setting it at late times = could > subtly break code at very early times. This fixes use of the FDT = mode in > loader, and FDT boot more generally, on 64-bit PowerPC systems. > =20 > Hardware provided by: IBM LTC > Approved by: re (kib) >=20 > Modified: > head/sys/powerpc/aim/aim_machdep.c > head/sys/powerpc/aim/locore64.S Usually I would test a couple of powerpc64 capable PowerMacs (a = so-called "Quad Core" one and a Dual Processor, single core per = processor, one) for if this changes the boot behavior noticeably for = them. But it will likely be a couple of months or more before I again = have access to them. Hopefully others will happen to test such examples = before then. Context note for PowerMacs used under powerpc64 FreeBSD: When I boot a powerpc64 PowerMac with a FreeBSD for powerpc64 I normally = run with a personal PowerMac specific change to allow reliable booting, = even when there is lots of RAM (8G, 12G, or 16G). The change is tied to = the transitions into and out of Apple's OpenFirmware and I observed it = to avoid memory trashing that I had observed otherwise. When I made this change I effectively eliminated just one instruction = from ofw_sprg_prepare(void): I went for the smallest generated-code = change that made the booting reliable on the PowerMac's that I commonly = have access to. The below just eliminates the pair: "mtsprg0 %1\n\t" and "r"(ofmsr[1]),=20 # svnlite diff /usr/src/sys/powerpc/ofw/ofw_machdep.c=20 Index: /usr/src/sys/powerpc/ofw/ofw_machdep.c =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- /usr/src/sys/powerpc/ofw/ofw_machdep.c (revision 302180) +++ /usr/src/sys/powerpc/ofw/ofw_machdep.c (working copy) @@ -111,6 +111,24 @@ * Assume that interrupt are disabled at this point, or * SPRG1-3 could be trashed */ +#if defined(AIM) && defined(__powerpc64__) +/* HACK: PowerMac G5 specific code to avoid demonstrated hangs in + * the early boot time frame: avoid mtsprg0 use. + * This would need a live test for PowerMac vs. not in order + * to remove HACK status --but without calling into + * OpenFirmware or the problem would be recreated. + */ + if (1) + __asm __volatile("mfsprg0 %0\n\t" + "mtsprg1 %1\n\t" + "mtsprg2 %2\n\t" + "mtsprg3 %3\n\t" + : "=3D&r"(ofw_sprg0_save) + : "r"(ofmsr[2]), + "r"(ofmsr[3]), + "r"(ofmsr[4])); + else +#endif __asm __volatile("mfsprg0 %0\n\t" "mtsprg0 %1\n\t" "mtsprg1 %2\n\t" I did not change the mfsprg0 nor did I change ofw_sprg_restore(void): = the booting was reliable without any change for those. [I do have access to my sources even though I do not have access to the = PowerMacs for a while.] =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-ppc@freebsd.org Sun Jun 26 23:38:36 2016 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0F41AB80EB3 for ; Sun, 26 Jun 2016 23:38:36 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) Received: from d.mail.sonic.net (d.mail.sonic.net [64.142.111.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D90B724F0 for ; Sun, 26 Jun 2016 23:38:35 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) Received: from comporellon.tachypleus.net (75-101-50-44.static.sonic.net [75.101.50.44]) (authenticated bits=0) by d.mail.sonic.net (8.15.1/8.15.1) with ESMTPSA id u5QNcWKu015602 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for ; Sun, 26 Jun 2016 16:38:33 -0700 Subject: Re: svn commit: r302214 - head/sys/powerpc/aim [my PowerMac G5 testing delayed] To: freebsd-ppc@freebsd.org References: From: Nathan Whitehorn Message-ID: <57706778.9060604@freebsd.org> Date: Sun, 26 Jun 2016 16:38:32 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Sonic-CAuth: UmFuZG9tSVYDVS1tSfqyAvwGCZXi/2g2IGDDDIFzfYr3WV4IA27rJIn1il+rTcUlWnVrfQvBXYnBF2X2f7HbJqv44Wc4kWD/p70v6lTupZQ= X-Sonic-ID: C;POIIGPc75hGEuZNwxPCmMQ== M;yklKGPc75hGEuZNwxPCmMQ== X-Spam-Flag: No X-Sonic-Spam-Details: 0.0/5.0 by cerberusd X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Jun 2016 23:38:36 -0000 On 06/26/16 16:22, Mark Millard wrote: > Quoting: > >> Author: nwhitehorn >> Date: Sun Jun 26 18:43:42 2016 >> New Revision: 302214 >> URL: >> https://svnweb.freebsd.org/changeset/base/302214 >> >> >> Log: >> Enter 64-bit mode as early as possible in the 64-bit PowerPC boot sequence. >> Most of the effect of setting MSR[SF] is that the CPU will stop ignoring >> the high 32 bits of registers containing addresses in load/store >> instructions. As such, the kernel was setting it only when it began to >> need access to high memory. MSR[SF] also affects the operation of some >> conditional instructions, however, and so setting it at late times could >> subtly break code at very early times. This fixes use of the FDT mode in >> loader, and FDT boot more generally, on 64-bit PowerPC systems. >> >> Hardware provided by: IBM LTC >> Approved by: re (kib) >> >> Modified: >> head/sys/powerpc/aim/aim_machdep.c >> head/sys/powerpc/aim/locore64.S > Usually I would test a couple of powerpc64 capable PowerMacs (a so-called "Quad Core" one and a Dual Processor, single core per processor, one) for if this changes the boot behavior noticeably for them. But it will likely be a couple of months or more before I again have access to them. Hopefully others will happen to test such examples before then. > > > Context note for PowerMacs used under powerpc64 FreeBSD: > > When I boot a powerpc64 PowerMac with a FreeBSD for powerpc64 I normally run with a personal PowerMac specific change to allow reliable booting, even when there is lots of RAM (8G, 12G, or 16G). The change is tied to the transitions into and out of Apple's OpenFirmware and I observed it to avoid memory trashing that I had observed otherwise. > > When I made this change I effectively eliminated just one instruction from ofw_sprg_prepare(void): I went for the smallest generated-code change that made the booting reliable on the PowerMac's that I commonly have access to. > > The below just eliminates the pair: > > "mtsprg0 %1\n\t" > and > "r"(ofmsr[1]), Those might be fixed with this change. Your patch (not restoring OF's SPRG0) will break a lot of Apple hardware. It's also not clear to me why it would do anything: it replaces firmware's SPRG0 with FreeBSD's SPRG0, trashing firmware state if it uses the register, in a situation (interrupts off) in which FreeBSD never uses SPRG0 either. As such, I would assume you are exposing another problem (maybe the one fixed in this commit). One thing it would be great to have some testing on after this change is the FDT layer in loader. If you set usefdt=1 from the loader prompt, loader will distill the OF device tree into an FDT and then stop Open Firmware completely before transferring control to FreeBSD. This should avoid any possible problems accessing Open Firmware from the kernel, as well as making boot a little faster. -Nathan From owner-freebsd-ppc@freebsd.org Mon Jun 27 09:28:45 2016 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5F125B84C2C for ; Mon, 27 Jun 2016 09:28:45 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-211-153.reflexion.net [208.70.211.153]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2501C2D96 for ; Mon, 27 Jun 2016 09:28:44 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 12471 invoked from network); 27 Jun 2016 09:29:17 -0000 Received: from unknown (HELO mail-cs-01.app.dca.reflexion.local) (10.81.19.1) by 0 (rfx-qmail) with SMTP; 27 Jun 2016 09:29:17 -0000 Received: by mail-cs-01.app.dca.reflexion.local (Reflexion email security v7.90.3) with SMTP; Mon, 27 Jun 2016 05:29:28 -0400 (EDT) Received: (qmail 16644 invoked from network); 27 Jun 2016 09:29:28 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 27 Jun 2016 09:29:28 -0000 X-No-Relay: not in my network X-No-Relay: not in my network Received: from [192.168.0.105] (ip70-189-131-151.lv.lv.cox.net [70.189.131.151]) by iron2.pdx.net (Postfix) with ESMTPSA id 715B11C407E; Mon, 27 Jun 2016 02:28:41 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: svn commit: r302214 - head/sys/powerpc/aim [my PowerMac G5 testing delayed] From: Mark Millard In-Reply-To: Date: Mon, 27 Jun 2016 02:28:41 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: References: To: Nathan Whitehorn , FreeBSD PowerPC ML X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Jun 2016 09:28:45 -0000 Nathan Whitehorn nwhitehorn at freebsd.org wrote on Sun Jun 26 23:38:36 = UTC 2016: > On 06/26/16 16:22, Mark Millard wrote: > > Quoting: > > > >> Author: nwhitehorn > >> Date: Sun Jun 26 18:43:42 2016 > >> New Revision: 302214 > >> URL: > >> https://svnweb.freebsd.org/changeset/base/302214 > >> > >> > >> Log: > >> Enter 64-bit mode as early as possible in the 64-bit PowerPC = boot sequence. > >> Most of the effect of setting MSR[SF] is that the CPU will stop = ignoring > >> the high 32 bits of registers containing addresses in load/store > >> instructions. As such, the kernel was setting it only when it = began to > >> need access to high memory. MSR[SF] also affects the operation = of some > >> conditional instructions, however, and so setting it at late = times could > >> subtly break code at very early times. This fixes use of the FDT = mode in > >> loader, and FDT boot more generally, on 64-bit PowerPC systems. > >> =20 > >> Hardware provided by: IBM LTC > >> Approved by: re (kib) > >> > >> Modified: > >> head/sys/powerpc/aim/aim_machdep.c > >> head/sys/powerpc/aim/locore64.S > > Usually I would test a couple of powerpc64 capable PowerMacs (a = so-called "Quad Core" one and a Dual Processor, single core per = processor, one) for if this changes the boot behavior noticeably for = them. But it will likely be a couple of months or more before I again = have access to them. Hopefully others will happen to test such examples = before then. > > > > > > Context note for PowerMacs used under powerpc64 FreeBSD: > > > > When I boot a powerpc64 PowerMac with a FreeBSD for powerpc64 I = normally run with a personal PowerMac specific change to allow reliable = booting, even when there is lots of RAM (8G, 12G, or 16G). The change is = tied to the transitions into and out of Apple's OpenFirmware and I = observed it to avoid memory trashing that I had observed otherwise. > > > > When I made this change I effectively eliminated just one = instruction from ofw_sprg_prepare(void): I went for the smallest = generated-code change that made the booting reliable on the PowerMac's = that I commonly have access to. > > > > The below just eliminates the pair: > > > > "mtsprg0 %1\n\t" > > and > > "r"(ofmsr[1]), >=20 > Those might be fixed with this change. Your patch (not restoring OF's=20= > SPRG0) will break a lot of Apple hardware. It's also not clear to me = why=20 > it would do anything: it replaces firmware's SPRG0 with FreeBSD's = SPRG0,=20 > trashing firmware state if it uses the register, in a situation=20 > (interrupts off) in which FreeBSD never uses SPRG0 either. As such, I=20= > would assume you are exposing another problem (maybe the one fixed in=20= > this commit). I'm nervous about the change because of an old memory about about the = initial instructions in Apple's openfirmware code. So I looked at at = some of my old messages, quoting one here: > the decoding of the first instructions for the openfirmware entry = point (0xff846d78 starting address on the G5 Quad-Core) is: >=20 > or r2,r0,r2, > addis r2,r0,-0x49 > ori r2,r2,0xf000 /* so %r2:=3D0xFFB7F000: fixed address (32-bit = mode). */ > std r1,r2,0x8, /* %r1 saved to have a special, separate copy = */ > std r0,r2,0x10, /* more saves to fixed locations */ > mfspr r0,lr > std r0,r2,0x120, /* more saves to fixed locations: return = address */ > mfmsr r1 > std r1,r2,0x108, /* more saves to fixed locations: msr */ > rldicl r1,r1,0,1 /* clears the most significant %r1 bit */ > 0x7c200164 (actually mtmsrd %r1) /* forces 32-bit mode */ > isync >=20 > Unfortunately for 64-bit mode at the start: %r2=3D0xFF...FFB7F000 and = std r1,r2,0x8, ends up rejecting the effective address. Apple does not = force 32-bit mode until a little later in the above. Thus ofwcall does = need to force 32-bit mode and return it back to normal, despite the msr = and other save/restore code that openfirmware has.=20 >=20 > (I've not explored trying to set up a mapping for the involved 64-bit = effective address range in order to allow the translation of the 64-bit = addresses in openfirmware's %r2 above. With that it might be that 64-bit = mode could be left in place.) >=20 > As far as I can tell this %r2 value and its use is the only reason = that FreeBSD needs to establish 32-bit mode before the call into = openfirmware. >=20 > %r2 needs to be restored after openfirmware returns since openfirmware = is using the Darwin ABI where %r2 is non-volatile and non-dedicated (no = use of TOCs), as can be seen above. (Apple's openfirmware uses Darwin's rule that %r2 is = volatile/non-dedicated --no TOC use-- and the above replaces r2's = value.) Now I may have been wrong back then about this code and its = implications. But at the moment I do not see any error in the above = quote. (Not that I have any reference materials with me beyond that = recorded in the list history. So I'm not that likely to find anything = wrong.) [If openfirmware aliases appropriate address ranges to the same memory = that might sidestep the above.] It sounds like a good experiment might be to compare and contrast = without and with my SPRG0 change after -r320214. I'd love to boot = reliably from a standard FeeBSD build. I fully agree that my change effectively switches to using FreeBSD's = SPRG0 value. It would be interesting to learn of an example type of PowerMac G5 = confirmed to fail someway with my hack present, at least if the failure = was different compared to normal FreeBSD code. Even more interesting = would be if the boot failures are repeatable on some PowerMac G5 type = when my change is present. (But I'd not have such a distinct type of G5 = to test with so I'd not be able to do much with the information.) [It is also true that in the two types of PowerMac G5's that I use I = also use only a limited range of devices: I only use the machine, RAM, = SATA SSDs, USB flash drives, Firewire hard drives, the internal Super = Drives, the video cards (a couple types of video cards, all of which = have worked), and the Ethernet ports. I only have access to the two = types of G5's.] > One thing it would be great to have some testing on after this change = is=20 > the FDT layer in loader. If you set usefdt=3D1 from the loader prompt,=20= > loader will distill the OF device tree into an FDT and then stop Open=20= > Firmware completely before transferring control to FreeBSD. This = should=20 > avoid any possible problems accessing Open Firmware from the kernel, = as=20 > well as making boot a little faster. > -Nathan Hopefully I'll remember this once I have access again. Feel free to send = me a reminder in a couple of months if you think about it. Side notes. . . Details related to FreeBSD's sprg0 use and my discoveries (other than = the code that I removed the assignment from): The evidence that I got for the crashes were tied to observed trashing = of FreeBSD memory as shown by being dumped out by DDB and detectably = incorrect %r1/%r3 values after open-firmware returned: %r1 should have = had no net change and %r3 has limited valid values. But the odd result = was: %r1=3D%r3=3D%r2+0x400, with %r2 having the before openfirware value = that is preserved to the after openfirmware context. As FreeBSD moved = things around in RAM in updates [such as by growing] the trashed area = moved around as well. The specific observed trashed areas for each = specific version that I tested stopped being trashed with the change and = the register values quit being bad as well. So something was using the only value that I changed (SPRG0) and also = touching both memory and the 2 registers with known correctness = properties that were being violated. [Note: I discovered the register value problems before I discovered the = memory trashing. I discovered the memory trashing before I discovered = the change in behavior based on SPRG0's value. That last was discovered = by cutting down a much larger change to powerpc64 specific FreeBSD code = that made things work as far as I could observe: it was the only part of = the bigger change that mattered to the behavior in question. Material = from all these stages are visible in the list history. But it s a mess = to go through my explorations.] Unfortunately I've got no good way to find the SPRG0 usage that might be = in Apple's OpenFirmware G5's and I'm not aware of any theory of = operation information available for Apple's implementations that could = be used to figure anything out about its SPRG0 use. [I sometimes wonder if interrupts are reenabled outside FreeBSD's = control sometimes during open-firmware code.] So my evidence is only the lack of the otherwise-observed trashing and = the lack of problems being noticed in the time that I've used my change. = I wish that I had better information. So far for builds with my change I've no evidence of any odd problems: = historically mostly 10.x STABLE starting when I isolated the change and = more recently mostly 11.0, many vintages of each tried. No standard = FreeBSD build that I've tried has booted the G5's reliably over the same = period and any time I've checked I've found the memory trashing and = register value oddities. (Not that I check such details for standard = builds often any more.) The sprg0 usage in FreeBSD based on "find sys -exec grep -i sprg0 {} \; = -print | more" and then looking at some of what it listed: #define GET_CPUINFO(r) \ mfsprg0 r . . . #define FRAME_SETUP(savearea) = \ /* Have to enable translation to allow access of kernel stack: */ = \ GET_CPUINFO(%r31); = \ mfsrr0 %r30; = \ std %r30,(savearea+CPUSAVE_SRR0)(%r31); /* save SRR0 */ = \ mfsrr1 %r30; = \ std %r30,(savearea+CPUSAVE_SRR1)(%r31); /* save SRR1 */ = \ . . . GET_CPUINFO(%r2); = \ ld %r27,(savearea+CPUSAVE_R27)(%r2); /* get saved r27 */ = \ ld %r28,(savearea+CPUSAVE_R28)(%r2); /* get saved r28 */ = \ ld %r29,(savearea+CPUSAVE_R29)(%r2); /* get saved r29 */ = \ ld %r30,(savearea+CPUSAVE_R30)(%r2); /* get saved r30 */ = \ ld %r31,(savearea+CPUSAVE_R31)(%r2); /* get saved r31 */ = \ . . . (from sys/powerpc/aim/trap_subr64.S) (The GET_CPUINFO macro has a lot of references. FreeBSD does store and = recall based on offsets from SPRG0 values, just in a very specific type = of context. I was never able to tell if this code was involved in the = memory trash or not.) sprgs[0] =3D mfspr(SPR_SPRG0); mtspr(SPR_SPRG0, sprgs[0]); (from sys/powerpc/aim/aim_machdep.c) #define SPR_USPRG0 0x100 /* 4.. User SPR General 0 */ #define SPR_SPRG0 0x110 /* 468 SPR General 0 */ (from sys/powerpc/include/spr.h) =3D=3D=3D Mark Millard markmi@dsl-only.net From owner-freebsd-ppc@freebsd.org Tue Jun 28 17:34:31 2016 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1618CB8594B for ; Tue, 28 Jun 2016 17:34:31 +0000 (UTC) (envelope-from jau789@gmail.com) Received: from mail-lf0-x22a.google.com (mail-lf0-x22a.google.com [IPv6:2a00:1450:4010:c07::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 94D3E2966 for ; Tue, 28 Jun 2016 17:34:30 +0000 (UTC) (envelope-from jau789@gmail.com) Received: by mail-lf0-x22a.google.com with SMTP id f6so16486886lfg.0 for ; Tue, 28 Jun 2016 10:34:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:subject:to:message-id:date:user-agent:mime-version :content-transfer-encoding; bh=hkRyQgGsCo+R2lEcAT16nEOF4GqAPqWgrCw5agxAUx4=; b=vunS4kiCi+zqP4+tXutein4Sj36n9VRBfw5lcvkeSnAs8lBlkOPql0+0ONHmJp8gEb SsFHxyW5d3/8WltLc/+DUbZI/64cNrd3dUCsInOuf3Mv2NRfQ4oIV+1ebqdDfaDSsESY W7e2F+0n/Bo3FKHclcZp3aSP7KyqAGfD4CLQGCFZdc5YR+rHiYBIuP9zspFk1vuYLoxo kCQ9TDj/Zf/AGlrvtjvydcFfWr5Pi+g296rHO8YRGaV/gwP+6j7yAAIQoFSnOOjc1DTZ RH47k+WA/RaB7NYsf+pO5SqkLidXgLs05sHJd5zFrE0WC9XFNOZc/6XKntX1em9aqYmg ZFEA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:subject:to:message-id:date:user-agent :mime-version:content-transfer-encoding; bh=hkRyQgGsCo+R2lEcAT16nEOF4GqAPqWgrCw5agxAUx4=; b=mYO2ZV4XlE37F3v9RTt8EFyW5PJQnQGXQs9vppCO8pGH8CNICoKp9bTDhJQ7briMH0 ixNLwkZGzLiPCDX0czG6Bh/AVD4IL57tuBQCyd/XYay4QSR0UUvmPKSOTTIGdnGqG7Ue JIYssofDXk1POIFnQiSqr7hZ+I2lv/C1CwCWc5kRoYLic3lLiwvG301kKtL8GvmDs7sd ItUta9uyZ2xTLEIyNtaborbFI3/DRc+E9MLICcSuM85AlR+h2NxteCKjNDUxRyNBAvJd N5NFcM2j2kxbi7kGdpcJpsKj2NGIp6FP15kz1JrEj6igXsOvOEGcCG2KqW3d7EDt5iQA vSTw== X-Gm-Message-State: ALyK8tKsin8mlqLsIfUTOrMxwnj9zdyEUT1cwAsJ/JOo8bguNYQ2HsjewwqCBGl0uwWD+g== X-Received: by 10.25.43.213 with SMTP id r204mr1677134lfr.112.1467135268568; Tue, 28 Jun 2016 10:34:28 -0700 (PDT) Received: from [192.168.1.131] (xdsl-205-1.nblnetworks.fi. [83.145.205.1]) by smtp.googlemail.com with ESMTPSA id 206sm4411202ljj.0.2016.06.28.10.34.27 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 28 Jun 2016 10:34:28 -0700 (PDT) From: "Jukka A. Ukkonen" Subject: Compiler dependent problems again on ppc64 To: FreeBSD PowerPC ML Message-ID: <3de3c40b-4edc-327e-f262-26230c7a3b12@gmail.com> Date: Tue, 28 Jun 2016 20:34:26 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jun 2016 17:34:31 -0000 Hello all, It seems there is yet another compiler dependent problem on ppc64. Most likely the same problem applies to all platforms using the old gcc as the default compiler. When trying to build gnu/lib/libstdc++ the compiler seems to get the option -std=c++11. The gcc complains about this and the build gets invariably broken at that point. This has now been going on for two days or so. This makes me believe nobody is actively running rebuilds of the latest current on any gcc based platform. --jau From owner-freebsd-ppc@freebsd.org Tue Jun 28 18:14:47 2016 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9600DB85549 for ; Tue, 28 Jun 2016 18:14:47 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: from mail-vk0-x231.google.com (mail-vk0-x231.google.com [IPv6:2607:f8b0:400c:c05::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DE772203; Tue, 28 Jun 2016 18:14:47 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: by mail-vk0-x231.google.com with SMTP id j3so33567492vkb.0; Tue, 28 Jun 2016 11:14:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=9yOd73eHDfTI35QcoFeeUklEVJ7YejH8jA+TgWxGGSs=; b=VT4yo2phHFMA/6inOt+TqBlGujegIqlPblXFkQJUOW5V/L61Frj94KBV15/Qj5KZ7h 9qpHrw312i6Q1T2xmPl0x/tGScxKB6CZlVFkDDVNnW3y6AeFzv5R1sFz8+2PjgAfdqmK H/+aUss7g5mz6Ggo0yAFk3u4HIosKOoyhi6YO7HL6xAgfTQbTIPs/Nl+SU+hSfvmTsQa twifvmPR6glZl9BkF5C+92ufw0Kd/bio/yVpSa95FkW6SdWMcfHGPlAX93tIFc7f4j6V cx2SamyasoCFntiTlFVCpZV9fXR4gDpBW4VTR0kd+w08vYfcqoVQ4TNcFMheHhWpKIUC rp2g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=9yOd73eHDfTI35QcoFeeUklEVJ7YejH8jA+TgWxGGSs=; b=dvuw1XW24XmRPQxhyVLVAbxkgA4f+yVjjVjcF7fvi1c/JAie+wjJ8UtUsZazhwauDE DmghumbBQxpy/OoXzCc79cakDvsXSOcCPfvI+SseBgMbWXBnMY184Yos0a9Cv7XupzQO y5t1MD5azJ8DKeHH4dmm83wQmu1bwzxOQmAI+iBYGZMt8OaNC+uSHGu2s+L/3Rjw4Pgi zG/2f1V8cZ0+XVlz68U+emazN9EsXIia/F4DqUKi5XSCgv/niQr72vIfVi6ohqh/Setj UtfzWcurBc6U4Z1z+5GhuyYIQB9/46qxo+G3wFw7HJ3R97TQ47bESuz6c3R3A3jpvXSL Evpw== X-Gm-Message-State: ALyK8tIBDsnwlCtVJ1YZBgMh0HdSdXpDd+m2deJ555fOWB089Aq3VnqEfv+F6tLKsneFCG+HhblGpNH/cvxrrA== X-Received: by 10.176.0.87 with SMTP id 81mr1426501uai.28.1467137686331; Tue, 28 Jun 2016 11:14:46 -0700 (PDT) MIME-Version: 1.0 Sender: chmeeedalf@gmail.com Received: by 10.103.103.198 with HTTP; Tue, 28 Jun 2016 11:14:45 -0700 (PDT) In-Reply-To: <3de3c40b-4edc-327e-f262-26230c7a3b12@gmail.com> References: <3de3c40b-4edc-327e-f262-26230c7a3b12@gmail.com> From: Justin Hibbits Date: Tue, 28 Jun 2016 13:14:45 -0500 X-Google-Sender-Auth: cKjubzwsrpw4nsFuvYUyIlHfrFU Message-ID: Subject: Re: Compiler dependent problems again on ppc64 To: "Jukka A. Ukkonen" Cc: FreeBSD PowerPC ML , Bryan Drewery Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jun 2016 18:14:47 -0000 On Tue, Jun 28, 2016 at 12:34 PM, Jukka A. Ukkonen wrote: > > Hello all, > > It seems there is yet another compiler dependent problem on > ppc64. Most likely the same problem applies to all platforms > using the old gcc as the default compiler. > When trying to build gnu/lib/libstdc++ the compiler seems to > get the option -std=c++11. The gcc complains about this and > the build gets invariably broken at that point. This has now > been going on for two days or so. This makes me believe nobody > is actively running rebuilds of the latest current on any gcc > based platform. > > --jau Which revision are you using? This should've been fixed a couple weeks ago. Adding Bryan Drewery, who made the fix. - Justin From owner-freebsd-ppc@freebsd.org Tue Jun 28 19:43:49 2016 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 84282B8603A for ; Tue, 28 Jun 2016 19:43:49 +0000 (UTC) (envelope-from jau789@gmail.com) Received: from mail-wm0-x22c.google.com (mail-wm0-x22c.google.com [IPv6:2a00:1450:400c:c09::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0B4B12899; Tue, 28 Jun 2016 19:43:49 +0000 (UTC) (envelope-from jau789@gmail.com) Received: by mail-wm0-x22c.google.com with SMTP id f126so153498217wma.1; Tue, 28 Jun 2016 12:43:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=2egqEgx2fEzpazX8o6cA4VVe/sWuNDq34ObgFb+5g18=; b=Rv9AAsgFjp4GP7kxYX8iZaYugNXCLY1mKm7yhA1aW1FAeh1MqFRH/8cR4eDxYyHeGs uuSJunIsfJzr76gsX7+FHwGNt4xEEqKMqS3cl1tUnm9aUM2PeZJH91h/WF9cdAWixnse CMdfd1QB9FX0ECVmR1PAunU772LPdgmOpVctkKxOrWi9YuZZUGO5nDFEgqM0t+GAYe9B bruzLDqn2kD1EtDxDdjsn4m6JJqRO0q7F25Z+I39pBR9WSS/Rq5U+ahz70itVvd2nXuk gA3IgiYTy4I8fYAiqHgmchSrlvwTTKJuEGvBYSFY6bTBhZwJO+qoyqEQgixGA+sIOE/j xNeQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=2egqEgx2fEzpazX8o6cA4VVe/sWuNDq34ObgFb+5g18=; b=AG1rXtFclYUlfmuz2glZiz54X6GUMCsh+EofNR7aY4fxRKMhEgfQ+cXQMJao3ML3EA fhi0mh/R+nHHXSxv5P6GwFZyzWg07k4kOdAb9J/blBrEWzcNrM3AAoREVfbqFWbYWDmS KDDB2uvTerMja2n+nMk+MIrGRAbCljqPH5fItZxjY3TYImhuW2UOyO+/3icw8N/Dz75K 7EjwCLxvIyNa6rcMEm0FZL4guz8Zoy9plGhQCzxTYpS0EhnWj4SOvhpwZli7SulIxDUB 3kmmLKHkbFB/Cn5Sh096ctGp3S+parMV3InCwF2ap8ThzIpo31OW0CprPZ15VSL+rQga Ji+Q== X-Gm-Message-State: ALyK8tK8jcunC7JaDgO5w8Ebi2Kh4RaUhknPwkMw6gvvqAmd7PEovKaEkju4T+Sc1Ji2Cw== X-Received: by 10.194.153.98 with SMTP id vf2mr4632564wjb.72.1467143027523; Tue, 28 Jun 2016 12:43:47 -0700 (PDT) Received: from [192.168.1.193] (xdsl-205-1.nblnetworks.fi. [83.145.205.1]) by smtp.gmail.com with ESMTPSA id g195sm437150wme.23.2016.06.28.12.43.46 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 28 Jun 2016 12:43:46 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (1.0) Subject: Re: Compiler dependent problems again on ppc64 From: Jukka Ukkonen X-Mailer: iPad Mail (13F69) In-Reply-To: Date: Tue, 28 Jun 2016 22:43:40 +0300 Cc: FreeBSD PowerPC ML , Bryan Drewery Content-Transfer-Encoding: quoted-printable Message-Id: <993E1F7C-F18B-42A7-BA08-9A815B1A7CD3@gmail.com> References: <3de3c40b-4edc-327e-f262-26230c7a3b12@gmail.com> To: Justin Hibbits X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jun 2016 19:43:49 -0000 The last version I tried was current pulled from svn today only a few hours ago. I guess around 16:00 GMT today is the best estimate I can give right now. The system on which I did the test is already powered down. I can check the exact svn release number tomorrow, though. The latest successful rebuild I have done was on the 19th. After that I tried a new rebuild only yesterday morning, and then it suddenly failed. --jau > On 28 Jun 2016, at 21:14, Justin Hibbits wrote: >=20 >> On Tue, Jun 28, 2016 at 12:34 PM, Jukka A. Ukkonen wro= te: >>=20 >> Hello all, >>=20 >> It seems there is yet another compiler dependent problem on >> ppc64. Most likely the same problem applies to all platforms >> using the old gcc as the default compiler. >> When trying to build gnu/lib/libstdc++ the compiler seems to >> get the option -std=3Dc++11. The gcc complains about this and >> the build gets invariably broken at that point. This has now >> been going on for two days or so. This makes me believe nobody >> is actively running rebuilds of the latest current on any gcc >> based platform. >>=20 >> --jau >=20 > Which revision are you using? This should've been fixed a couple > weeks ago. Adding Bryan Drewery, who made the fix. >=20 > - Justin From owner-freebsd-ppc@freebsd.org Tue Jun 28 19:50:06 2016 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CB035B860CD; Tue, 28 Jun 2016 19:50:06 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id ADF502A1B; Tue, 28 Jun 2016 19:50:06 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from mail.xzibition.com (localhost [IPv6:::1]) by freefall.freebsd.org (Postfix) with ESMTP id A09BA1ABF; Tue, 28 Jun 2016 19:50:06 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from mail.xzibition.com (localhost [172.31.3.2]) by mail.xzibition.com (Postfix) with ESMTP id 530A71D8CD; Tue, 28 Jun 2016 19:50:06 +0000 (UTC) X-Virus-Scanned: amavisd-new at mail.xzibition.com Received: from mail.xzibition.com ([172.31.3.2]) by mail.xzibition.com (mail.xzibition.com [172.31.3.2]) (amavisd-new, port 10026) with LMTP id JQWhB9BKL2g5; Tue, 28 Jun 2016 19:50:02 +0000 (UTC) Subject: Re: Compiler dependent problems again on ppc64 DKIM-Filter: OpenDKIM Filter v2.9.2 mail.xzibition.com 179EF1D8C4 To: Jukka Ukkonen , Justin Hibbits References: <3de3c40b-4edc-327e-f262-26230c7a3b12@gmail.com> <993E1F7C-F18B-42A7-BA08-9A815B1A7CD3@gmail.com> Cc: FreeBSD PowerPC ML , current@FreeBSD.org From: Bryan Drewery Openpgp: id=F9173CB2C3AAEA7A5C8A1F0935D771BB6E4697CF; url=http://www.shatow.net/bryan/bryan2.asc Organization: FreeBSD Message-ID: Date: Tue, 28 Jun 2016 12:50:01 -0700 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1 MIME-Version: 1.0 In-Reply-To: <993E1F7C-F18B-42A7-BA08-9A815B1A7CD3@gmail.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="gTgU3XgDplqJVwpBTuoDTkRdSXIbkbIbu" X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jun 2016 19:50:06 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --gTgU3XgDplqJVwpBTuoDTkRdSXIbkbIbu Content-Type: multipart/mixed; boundary="tqFARMMNlA5nOUK8puqmmL71n6OP8FVBN" From: Bryan Drewery To: Jukka Ukkonen , Justin Hibbits Cc: FreeBSD PowerPC ML , current@FreeBSD.org Message-ID: Subject: Re: Compiler dependent problems again on ppc64 References: <3de3c40b-4edc-327e-f262-26230c7a3b12@gmail.com> <993E1F7C-F18B-42A7-BA08-9A815B1A7CD3@gmail.com> In-Reply-To: <993E1F7C-F18B-42A7-BA08-9A815B1A7CD3@gmail.com> --tqFARMMNlA5nOUK8puqmmL71n6OP8FVBN Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable It's probably the switch to WITH_SYSTEM_COMPILER, which is confusing the logic to think a newer external compiler is being used. This problem will likely creep up on any platform using GCC 4.2 in base that meets the WITH_SYSTEM_COMPILER test. Try this patch please: https://people.freebsd.org/~bdrewery/patches/ppc-system-compiler-std-c++1= 1.diff On 6/28/2016 12:43 PM, Jukka Ukkonen wrote: >=20 > The last version I tried was current pulled from svn today > only a few hours ago. I guess around 16:00 GMT today is > the best estimate I can give right now. The system on > which I did the test is already powered down. I can check > the exact svn release number tomorrow, though. > The latest successful rebuild I have done was on the 19th. > After that I tried a new rebuild only yesterday morning, and > then it suddenly failed. >=20 > --jau >=20 >=20 >> On 28 Jun 2016, at 21:14, Justin Hibbits wrote= : >> >>> On Tue, Jun 28, 2016 at 12:34 PM, Jukka A. Ukkonen = wrote: >>> >>> Hello all, >>> >>> It seems there is yet another compiler dependent problem on >>> ppc64. Most likely the same problem applies to all platforms >>> using the old gcc as the default compiler. >>> When trying to build gnu/lib/libstdc++ the compiler seems to >>> get the option -std=3Dc++11. The gcc complains about this and >>> the build gets invariably broken at that point. This has now >>> been going on for two days or so. This makes me believe nobody >>> is actively running rebuilds of the latest current on any gcc >>> based platform. >>> >>> --jau >> >> Which revision are you using? This should've been fixed a couple >> weeks ago. Adding Bryan Drewery, who made the fix. >> >> - Justin --=20 Regards, Bryan Drewery --tqFARMMNlA5nOUK8puqmmL71n6OP8FVBN-- --gTgU3XgDplqJVwpBTuoDTkRdSXIbkbIbu Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBAgAGBQJXctTpAAoJEDXXcbtuRpfP7EUH/0u6aCnTkuvaWlaZh2XX+dZe hkogtMOI5wsP3IM0PeM+NLsQMiw0Ko09Nbuz+u53bUYDs+u09wRoKTlhyDL6rwuR Wdjupu1Z5cTCzhLVdDbazIXj9EE2tPyTGP0HXEMNTw6OMGZ1WvwDw+xvJ/Km0Pqc y8K5f/TJBEP3fJq/MWbSWLjCIy9c9ZJi2Q0rA9WqfBILHFa0RhBcXPS9AAdDwjTz 7oYMRJXyvMaFmM3dsWNTiazAsxCHKVdkyCmmHe8IP0VkZuPSRxiQydMYPXHitfhT 56RvAb0JtCpW6xHxemp/jjwLDcIHZMsdYFK/M8e5HgimCStSVUoUZjxSVzJJpeU= =9ReS -----END PGP SIGNATURE----- --gTgU3XgDplqJVwpBTuoDTkRdSXIbkbIbu-- From owner-freebsd-ppc@freebsd.org Wed Jun 29 12:27:49 2016 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 641CEAC5D91 for ; Wed, 29 Jun 2016 12:27:49 +0000 (UTC) (envelope-from no-reply@x252.vip.6pm-coupon.com) Received: from x252.vip.6pm-coupon.com (x252.vip.6pm-coupon.com [104.148.25.252]) by mx1.freebsd.org (Postfix) with ESMTP id 41B9D2CCC for ; Wed, 29 Jun 2016 12:27:48 +0000 (UTC) (envelope-from no-reply@x252.vip.6pm-coupon.com) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; s=6pm-coupon; d=x252.vip.6pm-coupon.com; h=MIME-Version:From:To:Date:Subject:Content-Type:Content-Transfer-Encoding; i=no-reply@x252.vip.6pm-coupon.com; bh=KIM8srrISlkixNLztu2RupmO8so=; b=fWr5vIHhmXzIWp8Zy05PMQxJOuHqWFrcHb7Vz7I9UrFCIPWk2pWfyiicnq/7Ncit4tG0GW2GuP+G Rk1HqiUf0FkR6armMinop3qltPi3u+KrcVK30WIRCQuUJq9xP7/dRFaoZO6mPZe3DNIXMhNS/IRe K7x0GMcIKs6ypkCRk/g= DomainKey-Signature: a=rsa-sha1; c=nofws; q=dns; s=6pm-coupon; d=x252.vip.6pm-coupon.com; b=RevLvpSNnNrSQJ348N9P8da7Zmc1xyxAZyxvL6uvQdyVxO2YO9+FaiIlrwDKuOMJXMcWEgdpm9Jf AZ9JwnQd3+JLKarMeWfMw/LvbZoClZiNJsMMnA1IPg7G4HUDasNtXdoeXQCzIowU/99G0720VzCh 4jaSejTPtNGKElfjqog=; From: "Ray.Ban Sunglasses" To: freebsd-ppc@freebsd.org Date: 29 Jun 2016 20:17:52 +0800 Subject: Must-See:Save Up To 90% OFF and Free Delivery349 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Jun 2016 12:27:49 -0000 From owner-freebsd-ppc@freebsd.org Wed Jun 29 13:00:51 2016 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0E179B73D0B; Wed, 29 Jun 2016 13:00:51 +0000 (UTC) (envelope-from jau789@gmail.com) Received: from mail-wm0-x234.google.com (mail-wm0-x234.google.com [IPv6:2a00:1450:400c:c09::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A956D2053; Wed, 29 Jun 2016 13:00:50 +0000 (UTC) (envelope-from jau789@gmail.com) Received: by mail-wm0-x234.google.com with SMTP id v199so179971398wmv.0; Wed, 29 Jun 2016 06:00:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=WOxoxgvtrANEvuSZ+NIJScz+1pl5Isp5Sj318oag2BY=; b=PNyHnPexht7d8u21D0FJQZKqLHyo9T3jrkln3KQSMrOT4FFZUKoj2hZuVqteQRgqva chl5sEy34QDkMvICckJGqzWOxOjdqP6f/YL9DH5wbRsgt3wvvfpvnog78Xio5c7dv4mo QNTH1XOSM6bEcMbbqwH2BwbsU2u1TftJICiHZvXA/uE80a1H5t1VoT0sevkFu9MMzacT 0GyCLpD7WYrYN5GolsxXbCPQ2fVK4O3ym/umrkaOYX43gSUJxG1GfToqWTLZpbVQh3ct pUkilDpeCJUiQ8YYBtgd3FR/pek7y0e0fanOGPoaVlHNqq/wDY7i2kJk35ohATHl9Upt +aRg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=WOxoxgvtrANEvuSZ+NIJScz+1pl5Isp5Sj318oag2BY=; b=eyBTzJcAEy3kKUWhQHgJJmk46Y3BXAM1s+tUGsDts9hNy/PHjudux1Lrwaavey2fn+ HZIDz7ecd7Y7Gg/NHhCmGlJMayYG5tRkPQLu7O5XOtC8qx2JJLQu/57/4gdthC2a9fm5 5PIbHYz/+LpnRcKDXrFnR7czM+58tG6miRyjuDhLz8k8UoWxzRgp/7J0ZzTtQJVugvK8 uw8NKmKLEElAvDKkHQHWeSuVYaU0WK3YpKVKyAfw+iLP3t1gvN1+N4URPozYUbjutVJb T6UijM1xuJHulLjhxiALtHsRbsrObbdZ+3F35/IhKXgh5t2UWAfcYN+v1B/zuASA1dhp ZY4Q== X-Gm-Message-State: ALyK8tKyDSX1uJGYJM/ZlRvy7yQEIuy36ZFxWkw9u/0v+FShUp/iwD+/x9tlYN3pqLIw1A== X-Received: by 10.28.132.15 with SMTP id g15mr9387305wmd.67.1467205249049; Wed, 29 Jun 2016 06:00:49 -0700 (PDT) Received: from [192.168.1.193] (xdsl-205-1.nblnetworks.fi. [83.145.205.1]) by smtp.gmail.com with ESMTPSA id ue1sm3609721wjc.44.2016.06.29.06.00.47 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Wed, 29 Jun 2016 06:00:48 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (1.0) Subject: Re: Compiler dependent problems again on ppc64 From: Jukka Ukkonen X-Mailer: iPad Mail (13F69) In-Reply-To: Date: Wed, 29 Jun 2016 16:00:42 +0300 Cc: Justin Hibbits , FreeBSD PowerPC ML , current@FreeBSD.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <3de3c40b-4edc-327e-f262-26230c7a3b12@gmail.com> <993E1F7C-F18B-42A7-BA08-9A815B1A7CD3@gmail.com> To: Bryan Drewery X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Jun 2016 13:00:51 -0000 With that patch included the build seems to run just fine. Thanks. --jau > On 28 Jun 2016, at 22:50, Bryan Drewery wrote: >=20 > It's probably the switch to WITH_SYSTEM_COMPILER, which is confusing the > logic to think a newer external compiler is being used. This problem > will likely creep up on any platform using GCC 4.2 in base that meets > the WITH_SYSTEM_COMPILER test. >=20 > Try this patch please: >=20 > https://people.freebsd.org/~bdrewery/patches/ppc-system-compiler-std-c++11= .diff >=20 >> On 6/28/2016 12:43 PM, Jukka Ukkonen wrote: >>=20 >> The last version I tried was current pulled from svn today >> only a few hours ago. I guess around 16:00 GMT today is >> the best estimate I can give right now. The system on >> which I did the test is already powered down. I can check >> the exact svn release number tomorrow, though. >> The latest successful rebuild I have done was on the 19th. >> After that I tried a new rebuild only yesterday morning, and >> then it suddenly failed. >>=20 >> --jau >>=20 >>=20 >>>> On 28 Jun 2016, at 21:14, Justin Hibbits wrote:= >>>>=20 >>>> On Tue, Jun 28, 2016 at 12:34 PM, Jukka A. Ukkonen w= rote: >>>>=20 >>>> Hello all, >>>>=20 >>>> It seems there is yet another compiler dependent problem on >>>> ppc64. Most likely the same problem applies to all platforms >>>> using the old gcc as the default compiler. >>>> When trying to build gnu/lib/libstdc++ the compiler seems to >>>> get the option -std=3Dc++11. The gcc complains about this and >>>> the build gets invariably broken at that point. This has now >>>> been going on for two days or so. This makes me believe nobody >>>> is actively running rebuilds of the latest current on any gcc >>>> based platform. >>>>=20 >>>> --jau >>>=20 >>> Which revision are you using? This should've been fixed a couple >>> weeks ago. Adding Bryan Drewery, who made the fix. >>>=20 >>> - Justin >=20 >=20 > --=20 > Regards, > Bryan Drewery >=20 From owner-freebsd-ppc@freebsd.org Wed Jun 29 15:41:25 2016 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9683DB868EA; Wed, 29 Jun 2016 15:41:25 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 845DD29A0; Wed, 29 Jun 2016 15:41:25 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from mail.xzibition.com (localhost [IPv6:::1]) by freefall.freebsd.org (Postfix) with ESMTP id 7E3D71F3D; Wed, 29 Jun 2016 15:41:25 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from mail.xzibition.com (localhost [172.31.3.2]) by mail.xzibition.com (Postfix) with ESMTP id 2E12121A80; Wed, 29 Jun 2016 15:41:25 +0000 (UTC) X-Virus-Scanned: amavisd-new at mail.xzibition.com Received: from mail.xzibition.com ([172.31.3.2]) by mail.xzibition.com (mail.xzibition.com [172.31.3.2]) (amavisd-new, port 10026) with LMTP id 1boZ-MtmHW66; Wed, 29 Jun 2016 15:41:17 +0000 (UTC) Subject: Re: Compiler dependent problems again on ppc64 DKIM-Filter: OpenDKIM Filter v2.9.2 mail.xzibition.com 8162C21A77 To: Jukka Ukkonen References: <3de3c40b-4edc-327e-f262-26230c7a3b12@gmail.com> <993E1F7C-F18B-42A7-BA08-9A815B1A7CD3@gmail.com> Cc: Justin Hibbits , FreeBSD PowerPC ML , current@FreeBSD.org From: Bryan Drewery Organization: FreeBSD Message-ID: Date: Wed, 29 Jun 2016 08:41:16 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.1.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Jun 2016 15:41:25 -0000 It has been committed. Thanks! On 6/29/16 6:00 AM, Jukka Ukkonen wrote: > > With that patch included the build seems to run just fine. > Thanks. > > --jau > > >> On 28 Jun 2016, at 22:50, Bryan Drewery wrote: >> >> It's probably the switch to WITH_SYSTEM_COMPILER, which is confusing the >> logic to think a newer external compiler is being used. This problem >> will likely creep up on any platform using GCC 4.2 in base that meets >> the WITH_SYSTEM_COMPILER test. >> >> Try this patch please: >> >> https://people.freebsd.org/~bdrewery/patches/ppc-system-compiler-std-c++11.diff >> >>> On 6/28/2016 12:43 PM, Jukka Ukkonen wrote: >>> >>> The last version I tried was current pulled from svn today >>> only a few hours ago. I guess around 16:00 GMT today is >>> the best estimate I can give right now. The system on >>> which I did the test is already powered down. I can check >>> the exact svn release number tomorrow, though. >>> The latest successful rebuild I have done was on the 19th. >>> After that I tried a new rebuild only yesterday morning, and >>> then it suddenly failed. >>> >>> --jau >>> >>> >>>>> On 28 Jun 2016, at 21:14, Justin Hibbits wrote: >>>>> >>>>> On Tue, Jun 28, 2016 at 12:34 PM, Jukka A. Ukkonen wrote: >>>>> >>>>> Hello all, >>>>> >>>>> It seems there is yet another compiler dependent problem on >>>>> ppc64. Most likely the same problem applies to all platforms >>>>> using the old gcc as the default compiler. >>>>> When trying to build gnu/lib/libstdc++ the compiler seems to >>>>> get the option -std=c++11. The gcc complains about this and >>>>> the build gets invariably broken at that point. This has now >>>>> been going on for two days or so. This makes me believe nobody >>>>> is actively running rebuilds of the latest current on any gcc >>>>> based platform. >>>>> >>>>> --jau >>>> >>>> Which revision are you using? This should've been fixed a couple >>>> weeks ago. Adding Bryan Drewery, who made the fix. >>>> >>>> - Justin >> >> >> -- >> Regards, >> Bryan Drewery >> -- Regards, Bryan Drewery From owner-freebsd-ppc@freebsd.org Thu Jun 30 00:28:44 2016 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2757CB87DA8 for ; Thu, 30 Jun 2016 00:28:44 +0000 (UTC) (envelope-from tirajepipe@res17-42.cp.htz.privatedns.biz) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 0E1B42AFE for ; Thu, 30 Jun 2016 00:28:44 +0000 (UTC) (envelope-from tirajepipe@res17-42.cp.htz.privatedns.biz) Received: by freefall.freebsd.org (Postfix) id 0D1EF1252; Thu, 30 Jun 2016 00:28:44 +0000 (UTC) Delivered-To: freebsd-powerpc@localmail.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by freefall.freebsd.org (Postfix) with ESMTP id 0C52E1251 for ; Thu, 30 Jun 2016 00:28:44 +0000 (UTC) (envelope-from tirajepipe@res17-42.cp.htz.privatedns.biz) Received: from res17-42.cp.htz.privatedns.biz (res17-42.cp.htz.privatedns.biz [144.76.173.42]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id AA4CA2AFC for ; Thu, 30 Jun 2016 00:28:43 +0000 (UTC) (envelope-from tirajepipe@res17-42.cp.htz.privatedns.biz) Received: from tirajepipe by res17-42.cp.htz.privatedns.biz with local (Exim 4.87) (envelope-from ) id 1bIOfG-0003kQ-PP for freebsd-powerpc@freebsd.org; Thu, 30 Jun 2016 01:13:02 +0200 To: freebsd-powerpc@freebsd.org Subject: Problem with parcel shipping, ID:000970884 X-PHP-Script: www.tirajepipe.com/post.php for 75.98.175.121 Date: Wed, 29 Jun 2016 18:13:02 -0500 From: "FedEx SmartPost" Reply-To: "FedEx SmartPost" Message-ID: <87423b3bd2c9fb1bbed1ca1ec43a8ce1@tirajepipe.com> X-Priority: 3 MIME-Version: 1.0 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - res17-42.cp.htz.privatedns.biz X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [1128 497] / [47 12] X-AntiAbuse: Sender Address Domain - res17-42.cp.htz.privatedns.biz X-Get-Message-Sender-Via: res17-42.cp.htz.privatedns.biz: authenticated_id: tirajepipe/from_h X-Authenticated-Sender: res17-42.cp.htz.privatedns.biz: glenn.faulkner@tirajepipe.com X-Source: X-Source-Args: X-Source-Dir: Content-Type: text/plain; charset=us-ascii X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jun 2016 00:28:44 -0000 Dear Customer, We could not deliver your parcel. Please, open email attachment to print shipment label. Yours faithfully, Glenn Faulkner, FedEx Operation Manager. From owner-freebsd-ppc@freebsd.org Thu Jun 30 06:34:25 2016 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4A114B87C77 for ; Thu, 30 Jun 2016 06:34:25 +0000 (UTC) (envelope-from tinkr@openmailbox.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 2F4322038 for ; Thu, 30 Jun 2016 06:34:25 +0000 (UTC) (envelope-from tinkr@openmailbox.org) Received: by freefall.freebsd.org (Postfix) id 2E6671976; Thu, 30 Jun 2016 06:34:25 +0000 (UTC) Delivered-To: freebsd-powerpc@localmail.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by freefall.freebsd.org (Postfix) with ESMTP id 2DBBD1975 for ; Thu, 30 Jun 2016 06:34:25 +0000 (UTC) (envelope-from tinkr@openmailbox.org) Received: from mail2.openmailbox.org (mail2.openmailbox.org [62.4.1.33]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E68432037; Thu, 30 Jun 2016 06:34:24 +0000 (UTC) (envelope-from tinkr@openmailbox.org) Received: by mail2.openmailbox.org (Postfix, from userid 1001) id AD8AC11404B; Thu, 30 Jun 2016 08:22:11 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=openmailbox.org; s=openmailbox; t=1467267731; bh=a27hgdzD2reN2m6AoVuCFqJTPhA7RMf/dyTy2HvuOp4=; h=Date:From:To:Subject:In-Reply-To:References:From; b=nKSXTpTL5U0SICU5UiGjJv/Zhq3PYf5R/DKTZONQsTvNOtx3DfXDY4VN8WgmastN8 xkQcbDYDbxnGtbHgOHGhET321Vm4Wj383YpQqDHFGPv00Tsv6h3VtdOH5j1hdw288v DP/QBV1kTO0sqp4/W8S5KadLYNIvLqGMKsowLYfo= X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on h3 X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from www.openmailbox.org (unknown [10.91.130.55]) by mail2.openmailbox.org (Postfix) with ESMTP id 70657102E82; Thu, 30 Jun 2016 08:22:04 +0200 (CEST) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Thu, 30 Jun 2016 14:22:04 +0800 From: Tinker To: freebsd-powerpc@freebsd.org, owner-freebsd-ppc@freebsd.org, FedEx SmartPost , FedEx SmartPost , FedEx International MailService Subject: How can we remove this =?UTF-8?Q?spam=3F=20=20=20It=27s=20getting?= =?UTF-8?Q?=20tiring=2E=20=20=20=28GLENN=20F=2C=20NATHAN=20G=2C=20DEREK=20?= =?UTF-8?Q?H=29=20=20Re=3A=20Problem=20with=20parcel=20shipping=2C=20ID=3A?= =?UTF-8?Q?=30=30=30=39=37=30=38=38=34?= In-Reply-To: <87423b3bd2c9fb1bbed1ca1ec43a8ce1@tirajepipe.com> References: <87423b3bd2c9fb1bbed1ca1ec43a8ce1@tirajepipe.com> Message-ID: X-Sender: tinkr@openmailbox.org User-Agent: Roundcube Webmail/1.0.6 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jun 2016 06:34:25 -0000 We should kick this one out. It's from FedEx SmartPost , FedEx SmartPost and FedEx International MailService . Do these guys have viruses or what? Thanks. On 2016-06-30 07:13, FedEx SmartPost wrote: > Dear Customer, > > We could not deliver your parcel. > Please, open email attachment to print shipment label. > > Yours faithfully, > Glenn Faulkner, > FedEx Operation Manager. > > _______________________________________________ > freebsd-ppc@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ppc > To unsubscribe, send any mail to "freebsd-ppc-unsubscribe@freebsd.org"