Re: Are there SPARC [or other] aligned memory access requirements to avoid exceptions? [now that 11.0's armv6/v7 is allowing more unaligned accesses]

2016-05-27 Thread Matthias Andree
Am 27.05.2016 um 06:14 schrieb Cedric Blancher: > SPARCv7, SPARCv8 and SPARCv9 mandate natural alignment like all > 'normal' RISC implementations. SPARCv9 ABI adds some 'special' > instructions (separate from the normal load/store instructions) for > unaligned access, but as said they come with cos

Re: Are there SPARC [or other] aligned memory access requirements to avoid exceptions? [now that 11.0's armv6/v7 is allowing more unaligned accesses]

2016-05-27 Thread Mark Millard
On 2016-May-27, at 12:30 AM, Matthias Andree wrote: > Am 27.05.2016 um 06:14 schrieb Cedric Blancher: >> SPARCv7, SPARCv8 and SPARCv9 mandate natural alignment like all >> 'normal' RISC implementations. SPARCv9 ABI adds some 'special' >> instructions (separate from the normal load/store instructi

Re: Are there SPARC [or other] aligned memory access requirements to avoid exceptions? [now that 11.0's armv6/v7 is allowing more unaligned accesses]

2016-05-27 Thread Mark Cave-Ayland
On 27/05/16 12:35, Mark Millard wrote: >> 1 - figure if this affects other RISC architectures. Cedric got the >> SPARC on the hook, but I'm open for input on other arch's. >> >> If someone can report back if the lzo2 port runs into >> unaligned-access-emulation traps on FreeBSD/sparc*, that would

Re: Are there SPARC [or other] aligned memory access requirements to avoid exceptions? [now that 11.0's armv6/v7 is allowing more unaligned accesses]

2016-05-27 Thread Ian Lepore
On Fri, 2016-05-27 at 04:35 -0700, Mark Millard wrote: > On 2016-May-27, at 12:30 AM, Matthias Andree > wrote: > > > Am 27.05.2016 um 06:14 schrieb Cedric Blancher: > > > [...] > The rpi vintage matters: > > Original rpi's (before rpi2): ARM1176JZF-S, 32-bit (not armv6 nor > armv7-a/cortex-a7)

Re: Are there SPARC [or other] aligned memory access requirements to avoid exceptions? [now that 11.0's armv6/v7 is allowing more unaligned accesses]

2016-05-27 Thread Ian Lepore
On Fri, 2016-05-27 at 09:30 +0200, Matthias Andree wrote: > Am 27.05.2016 um 06:14 schrieb Cedric Blancher: > > [...] > > > 2 - find someone to review the ARM and AARCH related #if preprocessor > stuff in ./include/lzo/lzodefs.h in the port's WRKSRC after > unpacking. > I just had a look. I t

Re: 11.0-CURRENT -r300770 libc++ update vs. lang/powerpc64-xtoolchain-gcc: no go [self hosted powerpc64 context]

2016-05-27 Thread Dimitry Andric
On 27 May 2016, at 01:53, Mark Millard wrote: > > I do buildworld/buildkernel on a powerpc64 targeting itself via > lang/powerpc64-xtoolchain-gcc (a.k.a. lang/powerpc64-gcc for the most part). > [Getting that lang/powerpc64-gcc installed for self-hosted use does take some > work-around activit

Re: 11.0-CURRENT -r300770 libc++ update vs. lang/powerpc64-xtoolchain-gcc: no go [self hosted powerpc64 context]

2016-05-27 Thread Mark Millard
On 2016-May-27, at 1:50 PM, Dimitry Andric wrote: > > On 27 May 2016, at 01:53, Mark Millard wrote: >> >> I do buildworld/buildkernel on a powerpc64 targeting itself via >> lang/powerpc64-xtoolchain-gcc (a.k.a. lang/powerpc64-gcc for the most part). >> [Getting that lang/powerpc64-gcc install

Re: 11.0-CURRENT -r300770 libc++ update vs. lang/powerpc64-xtoolchain-gcc: no go [self hosted powerpc64 context]

2016-05-27 Thread Mark Millard
[I'm top posting the results of the failed build.] It looks like the following has been addresses in -r300884. libcompat also got a -isystem in -r300885. -r300886 did "Move external GCC compiler hacks to bsd.sys.mk". So I'll retry based on -r300886. Failure details. . . Both the powerpc64

Re: svn commit: r297435 - head: still problems for stage 3 when gcc 4.2.1 is avoided (powerpc64 self-hosted build)

2016-05-27 Thread Bryan Drewery
On 3/31/2016 8:33 PM, Mark Millard wrote: > I appears that C++ needs its own override for where to find C++ header before > looking in the gcc49 specific places. Yes, the hacks for that are builtin already. Passing C_INCLUDE_PATH and others may break it. > These sorts of odd, hard to avoid depe

Re: svn commit: r297435 - head: still problems for stage 3 when gcc 4.2.1 is avoided (powerpc64 self-hosted build)

2016-05-27 Thread Mark Millard
On 2016-May-27, at 4:48 PM, Bryan Drewery wrote: > On 3/31/2016 8:33 PM, Mark Millard wrote: >> I appears that C++ needs its own override for where to find C++ header >> before looking in the gcc49 specific places. > > Yes, the hacks for that are builtin already. Passing C_INCLUDE_PATH and >

Re: svn commit: r297435 - head: still problems for stage 3 when gcc 4.2.1 is avoided (powerpc64 self-hosted build)

2016-05-27 Thread Bryan Drewery
On 5/27/2016 5:15 PM, Mark Millard wrote: > + --with-local-prefix=/usr/include \ > > looks wrong to me. The default is not /usr/local/include but just /usr/local > . Quoting https://gcc.gnu.org/install/configure.html : > > --with-local-prefix=dirname > Specify the installation direct

Re: 11.0-CURRENT -r300770 libc++ update vs. lang/powerpc64-xtoolchain-gcc: no go [self hosted powerpc64 context]

2016-05-27 Thread Mark Millard
[Top posting failure results again.] -r300886 for powerpc64 failed for each of: /usr/src/lib/clang/libclanganalysis/../../../contrib/llvm/tools/clang/lib/Analysis/AnalysisDeclContext.cpp /usr/src/lib/clang/libclangarcmigrate/../../../contrib/llvm/tools/clang/lib/ARCMigrate/ARCMT.cpp with the li

Re: svn commit: r297435 - head: still problems for stage 3 when gcc 4.2.1 is avoided (powerpc64 self-hosted build)

2016-05-27 Thread Mark Millard
FYI. . . I expect that building gcc49 with: + --with-local-prefix=/usr \ will help with system build activities via gcc49/g++49 by avoiding /usr/local/include interfering. But I also expect that various port builds based on that same gcc49/g++49 will have problems from not expli

Re: svn commit: r297435 - head: still problems for stage 3 when gcc 4.2.1 is avoided (powerpc64 self-hosted build)

2016-05-27 Thread Mark Millard
On 2016-May-27, at 7:04 PM, Mark Millard wrote: > FYI. . . > > I expect that building gcc49 with: > > + --with-local-prefix=/usr \ > > will help with system build activities via gcc49/g++49 by avoiding > /usr/local/include interfering. > > But I also expect that various port buil

Re: 11.0-CURRENT -r300770 libc++ update vs. lang/powerpc64-xtoolchain-gcc: no go [self hosted powerpc64 context]

2016-05-27 Thread Mark Millard
On 2016-May-27, at 6:04 PM, Mark Millard wrote: > [Top posting failure results again.] > > -r300886 for powerpc64 failed for each of: > > /usr/src/lib/clang/libclanganalysis/../../../contrib/llvm/tools/clang/lib/Analysis/AnalysisDeclContext.cpp > > /usr/src/lib/clang/libclangarcmigrate/../../.