From owner-freebsd-toolchain@freebsd.org Sun Nov 15 00:31:44 2015 Return-Path: Delivered-To: freebsd-toolchain@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 B2FF6A2E422 for ; Sun, 15 Nov 2015 00:31:44 +0000 (UTC) (envelope-from wam@hiwaay.net) Received: from fly.hiwaay.net (fly.hiwaay.net [216.180.54.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 76BA71283 for ; Sun, 15 Nov 2015 00:31:44 +0000 (UTC) (envelope-from wam@hiwaay.net) Received: from kabini1.local (dynamic-216-186-213-32.knology.net [216.186.213.32] (may be forged)) (authenticated bits=0) by fly.hiwaay.net (8.13.8/8.13.8/fly) with ESMTP id tAF0VZCj020490 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Sat, 14 Nov 2015 18:31:36 -0600 Subject: Re: amd64-gcc question To: FreeBSD toolchain mailing list !!!! References: <56449EF8.7070806@hiwaay.net> From: "William A. Mahaffey III" Message-ID: <5647D267.4070808@hiwaay.net> Date: Sat, 14 Nov 2015 18:37:05 -0553.75 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: <56449EF8.7070806@hiwaay.net> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Nov 2015 00:31:44 -0000 On 11/12/15 08:20, William A. Mahaffey III wrote: > > > Howdy, new to this list. I posted this to FreeBSD-users & was advised > to try this list or the GNU GCC list, so here goes: > > > I pkg-installed amd64-gcc over the weekend hoping for Graphite > (auto-loop parallelization) support, but no go. I looked around over > the weekend & found that there was no port for that package, only the > pkg. I just did a 'portsnap fetch upgrade' & there is now a port for > amd64-gcc, but it includes no files & no pkg-descr file. I determined > over the weekend that the gcc's from about V4.3 on can indeed be built > w/ Graphite support, but you need to do it manually. I found a post > dated 2010 from someone who did it under linux: > http://openwall.info/wiki/internal/gcc-local-build. I see no configure > files for any of the gcc ports (I have the entire ports tree > downloaded & local, & freshly updated as of a few min. ago). What is > the canonical/BPP (FreeBSD 9.3R) way of recompiling a port with > different config flags ? > > > I did find ports/pkgs for the 2 main components apparently needed for > Graphite support (cloog & ppl) & pkg-installed them over the weekend, > so I am ready to go on that front. > > > I have gotten as far as running 'make showconfig' in the various gcc* > & amd64-gcc directories to see what info I could get on default config > options. In all cases they gave options & said to run 'make config' to > change options. I didn't even see a 'config:' entry in the Makefiles > (probably included from elsewhere, but I didn't chase it). I only want > to make the minimum # of config mods necessary (trusting that pkg/port > maintainers probably know more than I about their various pkg's & > ports) to add the cloog & ppl support & recompile. > > > I have been using pkg almost exclusively to maintain my (now 3) > FreeBSD 9.3R boxen, except for recompiling the linux-c6 flash plugin > for this box whenever it get upgraded, so I have *no* experience with > getting more nitty-gritty w/ FreeBSD ports than that :-/. TIA & have a > good one. > > > BTW: > > [wam@devbox, pre, 8:19:58am] 676 % uname -a > FreeBSD devbox 9.3-RELEASE-p24 FreeBSD 9.3-RELEASE-p24 #0: Sat Aug 22 > 01:54:44 UTC 2015 > root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 > [wam@devbox, pre, 8:20:00am] 677 % sysctl -A | grep -A1 -B1 model > hw.machine: amd64 > hw.model: AMD A8-6500 APU with Radeon(tm) HD Graphics > hw.ncpu: 4 > -- > dev.rgephy.0.%location: phyno=1 > dev.rgephy.0.%pnpinfo: oui=0xe04c model=0x0 rev=0x0 > dev.rgephy.0.%parent: miibus0 > [wam@devbox, pre, 8:20:12am] 678 % > > Updated info & a question or 2: [wam@devbox, pre, 1:07:58pm] 876 % ^8^9^ gcc49 -v --help Using built-in specs. COLLECT_GCC=gcc49 COLLECT_LTO_WRAPPER=/usr/local/libexec/gcc49/gcc/x86_64-portbld-freebsd9.3/4.9.4/lto-wrapper Usage: gcc49 [options] file... Options: -pass-exit-codes Exit with highest error code from a phase --help Display this information --target-help Display target specific command line options --help={common|optimizers|params|target|warnings|[^]{joined|separate|undocumented}}[,...] Display specific types of command line options --version Display compiler version information -dumpspecs Display all of the built in spec strings -dumpversion Display the version of the compiler -dumpmachine Display the compiler's target processor -print-search-dirs Display the directories in the compiler's search path -print-libgcc-file-name Display the name of the compiler's companion library -print-file-name= Display the full path to library -print-prog-name= Display the full path to compiler component -print-multiarch Display the target's normalized GNU triplet, used as a component in the library path -print-multi-directory Display the root directory for versions of libgcc -print-multi-lib Display the mapping between command line options and multiple library search directories -print-multi-os-directory Display the relative path to OS libraries -print-sysroot Display the target libraries directory -print-sysroot-headers-suffix Display the sysroot suffix used to find headers -Wa, Pass comma-separated on to the assembler -Wp, Pass comma-separated on to the preprocessor -Wl, Pass comma-separated on to the linker -Xassembler Pass on to the assembler -Xpreprocessor Pass on to the preprocessor -Xlinker Pass on to the linker -save-temps Do not delete intermediate files -save-temps= Do not delete intermediate files -no-canonical-prefixes Do not canonicalize paths when building relative prefixes to other gcc components -pipe Use pipes rather than intermediate files -time Time the execution of each subprocess -specs= Override built-in specs with the contents of -std= Assume that the input sources are for --sysroot= Use as the root directory for headers and libraries -B Add to the compiler's search paths -v Display the programs invoked by the compiler -### Like -v but options quoted and commands not executed -E Preprocess only; do not compile, assemble or link -S Compile only; do not assemble or link -c Compile and assemble, but do not link -o Place the output into -pie Create a position independent executable -shared Create a shared library -x Specify the language of the following input files Permissible languages include: c c++ assembler none 'none' means revert to the default behavior of guessing the language based on the file's extension Options starting with -g, -f, -m, -O, -W, or --param are automatically passed on to the various sub-processes invoked by gcc49. In order to pass other options on to these processes the -W options must be used. Target: x86_64-portbld-freebsd9.3 Configured with: ./../gcc-4.9-20151028/configure --with-build-config=bootstrap-debug --disable-nls --enable-gnu-indirect-function --libdir=/usr/local/lib/gcc49 --libexecdir=/usr/local/libexec/gcc49 --program-suffix=49 --with-as=/usr/local/bin/as --with-gmp=/usr/local --with-gxx-include-dir=/usr/local/lib/gcc49/include/c++/ --with-ld=/usr/local/bin/ld --with-ppl=/usr/local/lib --with-cloog=/usr/local/lib --with-libiconv-prefix=/usr/local --with-pkgversion='FreeBSD Ports Collection' --with-system-zlib --disable-libgcj --enable-languages=c,c++,objc,fortran --prefix=/usr/local --localstatedir=/var --mandir=/usr/local/man --infodir=/usr/local/info/gcc49 --build=x86_64-portbld-freebsd9.3 Thread model: posix gcc version 4.9.4 20151028 (prerelease) (FreeBSD Ports Collection) COLLECT_GCC_OPTIONS='-v' '--help' '-mtune=generic' '-march=x86-64' /usr/local/libexec/gcc49/gcc/x86_64-portbld-freebsd9.3/4.9.4/cc1 -quiet -v help-dummy -quiet -dumpbase help-dummy -mtune=generic -march=x86-64 -auxbase help-dummy -version --help -o /tmp//cc0bsC4i.s The following options are specific to just the language Ada: None found. Use --help=Ada to show *all* the options supported by the Ada front-end .... & many more lines snipped. Observe that the config shows --with-ppl & --with-cloog, req'd for Graphite (auto-loop-parallelization), yet my compiles still fail out w/ the following: Beginning background make WAMGCC=49 all Initiated at 06:30:01 PM MCST on Saturday, November 14, 2015 MakeMPI: both --- MakeMPI: ../lib/R4/opteron/libmpi.a --- gcc49 -DNDEBUG -DUNDER_SCORE_SYS -DLOSE_GAMMAL -I../include -I~/inc -I../Properties -I../TEST -I../pre -march=opteron -mtune=opteron -O3 -fprefetch-loop-arrays -floo p-parallelize-all -ftree-parallelize-loops=4 -fopt-info -c mpi.c mpprime.c mpi.c:1:0: sorry, unimplemented: Graphite loop optimizations cannot be used (-fgraphite, -fgraphite-identity, -floop-block, -floop-interchange, -floop-strip-mine, -fl oop-parallelize-all, and -ftree-loop-linear) /* ^ mpprime.c:1:0: sorry, unimplemented: Graphite loop optimizations cannot be used (-fgraphite, -fgraphite-identity, -floop-block, -floop-interchange, -floop-strip-mine, -floop-parallelize-all, and -ftree-loop-linear) /* ^ *** [../lib/R4/opteron/libmpi.a] Error code 1 1 error `usual' not remade because of errors. i.e. no Graphite support. A few questions: 1. Is this list the proper forum for these questions :-) ? 2. Are ppl & cloog (both pkg-installed last wqeekend & ready to go) in fact all that is req'd for Graphite support to work ? 3. Did the port of gcc4.9 wind up removing the req'd code internally for Graphite support, so that even w/ the config properly setup, I still get no Graphite support ? This identical code (accessed via VPATH macro from Makefile over there) compiles elsewhere on my LAN under Intel icc/ifort & parallelizes where expected AOK. *Any* clues much appreciated. TIA & have a good one. -- William A. Mahaffey III ---------------------------------------------------------------------- "The M1 Garand is without doubt the finest implement of war ever devised by man." -- Gen. George S. Patton Jr. From owner-freebsd-toolchain@freebsd.org Sun Nov 15 16:45:54 2015 Return-Path: Delivered-To: freebsd-toolchain@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 84433A302F7 for ; Sun, 15 Nov 2015 16:45:54 +0000 (UTC) (envelope-from wam@hiwaay.net) Received: from fly.hiwaay.net (fly.hiwaay.net [216.180.54.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 522AE1306 for ; Sun, 15 Nov 2015 16:45:53 +0000 (UTC) (envelope-from wam@hiwaay.net) Received: from kabini1.local (dynamic-216-186-213-32.knology.net [216.186.213.32] (may be forged)) (authenticated bits=0) by fly.hiwaay.net (8.13.8/8.13.8/fly) with ESMTP id tAFGjp0v007598 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Sun, 15 Nov 2015 10:45:52 -0600 Subject: Re: amd64-gcc question To: FreeBSD toolchain mailing list !!!! References: <56449EF8.7070806@hiwaay.net> <5647D267.4070808@hiwaay.net> From: "William A. Mahaffey III" Message-ID: <5648B6BF.3090002@hiwaay.net> Date: Sun, 15 Nov 2015 10:51:21 -0553.75 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: <5647D267.4070808@hiwaay.net> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Nov 2015 16:45:54 -0000 On 11/14/15 18:36, William A. Mahaffey III wrote: > On 11/12/15 08:20, William A. Mahaffey III wrote: >> >> >> Howdy, new to this list. I posted this to FreeBSD-users & was advised >> to try this list or the GNU GCC list, so here goes: >> >> >> I pkg-installed amd64-gcc over the weekend hoping for Graphite >> (auto-loop parallelization) support, but no go. I looked around over >> the weekend & found that there was no port for that package, only the >> pkg. I just did a 'portsnap fetch upgrade' & there is now a port for >> amd64-gcc, but it includes no files & no pkg-descr file. I determined >> over the weekend that the gcc's from about V4.3 on can indeed be >> built w/ Graphite support, but you need to do it manually. I found a >> post dated 2010 from someone who did it under linux: >> http://openwall.info/wiki/internal/gcc-local-build. I see no >> configure files for any of the gcc ports (I have the entire ports >> tree downloaded & local, & freshly updated as of a few min. ago). >> What is the canonical/BPP (FreeBSD 9.3R) way of recompiling a port >> with different config flags ? >> >> >> I did find ports/pkgs for the 2 main components apparently needed for >> Graphite support (cloog & ppl) & pkg-installed them over the weekend, >> so I am ready to go on that front. >> >> >> I have gotten as far as running 'make showconfig' in the various gcc* >> & amd64-gcc directories to see what info I could get on default >> config options. In all cases they gave options & said to run 'make >> config' to change options. I didn't even see a 'config:' entry in the >> Makefiles (probably included from elsewhere, but I didn't chase it). >> I only want to make the minimum # of config mods necessary (trusting >> that pkg/port maintainers probably know more than I about their >> various pkg's & ports) to add the cloog & ppl support & recompile. >> >> >> I have been using pkg almost exclusively to maintain my (now 3) >> FreeBSD 9.3R boxen, except for recompiling the linux-c6 flash plugin >> for this box whenever it get upgraded, so I have *no* experience with >> getting more nitty-gritty w/ FreeBSD ports than that :-/. TIA & have >> a good one. >> >> >> BTW: >> >> [wam@devbox, pre, 8:19:58am] 676 % uname -a >> FreeBSD devbox 9.3-RELEASE-p24 FreeBSD 9.3-RELEASE-p24 #0: Sat Aug 22 >> 01:54:44 UTC 2015 >> root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 >> [wam@devbox, pre, 8:20:00am] 677 % sysctl -A | grep -A1 -B1 model >> hw.machine: amd64 >> hw.model: AMD A8-6500 APU with Radeon(tm) HD Graphics >> hw.ncpu: 4 >> -- >> dev.rgephy.0.%location: phyno=1 >> dev.rgephy.0.%pnpinfo: oui=0xe04c model=0x0 rev=0x0 >> dev.rgephy.0.%parent: miibus0 >> [wam@devbox, pre, 8:20:12am] 678 % >> >> > > > Updated info & a question or 2: > > [wam@devbox, pre, 1:07:58pm] 876 % ^8^9^ > gcc49 -v --help > Using built-in specs. > COLLECT_GCC=gcc49 > COLLECT_LTO_WRAPPER=/usr/local/libexec/gcc49/gcc/x86_64-portbld-freebsd9.3/4.9.4/lto-wrapper > > Usage: gcc49 [options] file... > Options: > -pass-exit-codes Exit with highest error code from a phase > --help Display this information > --target-help Display target specific command line options > --help={common|optimizers|params|target|warnings|[^]{joined|separate|undocumented}}[,...] > > Display specific types of command line options > --version Display compiler version information > -dumpspecs Display all of the built in spec strings > -dumpversion Display the version of the compiler > -dumpmachine Display the compiler's target processor > -print-search-dirs Display the directories in the compiler's > search path > -print-libgcc-file-name Display the name of the compiler's > companion library > -print-file-name= Display the full path to library > -print-prog-name= Display the full path to compiler component > > -print-multiarch Display the target's normalized GNU > triplet, used as > a component in the library path > -print-multi-directory Display the root directory for versions of > libgcc > -print-multi-lib Display the mapping between command line > options and > multiple library search directories > -print-multi-os-directory Display the relative path to OS libraries > -print-sysroot Display the target libraries directory > -print-sysroot-headers-suffix Display the sysroot suffix used to > find headers > -Wa, Pass comma-separated on to the > assembler > -Wp, Pass comma-separated on to the > preprocessor > -Wl, Pass comma-separated on to the > linker > -Xassembler Pass on to the assembler > -Xpreprocessor Pass on to the preprocessor > -Xlinker Pass on to the linker > -save-temps Do not delete intermediate files > -save-temps= Do not delete intermediate files > -no-canonical-prefixes Do not canonicalize paths when building > relative > prefixes to other gcc components > -pipe Use pipes rather than intermediate files > -time Time the execution of each subprocess > -specs= Override built-in specs with the contents > of > -std= Assume that the input sources are for > > --sysroot= Use as the root directory for > headers > and libraries > -B Add to the compiler's search paths > -v Display the programs invoked by the compiler > -### Like -v but options quoted and commands not > executed > -E Preprocess only; do not compile, assemble > or link > -S Compile only; do not assemble or link > -c Compile and assemble, but do not link > -o Place the output into > -pie Create a position independent executable > -shared Create a shared library > -x Specify the language of the following input > files > Permissible languages include: c c++ > assembler none > 'none' means revert to the default behavior of > guessing the language based on the file's > extension > > Options starting with -g, -f, -m, -O, -W, or --param are automatically > passed on to the various sub-processes invoked by gcc49. In order to > pass > other options on to these processes the -W options must be used. > > Target: x86_64-portbld-freebsd9.3 > Configured with: ./../gcc-4.9-20151028/configure > --with-build-config=bootstrap-debug --disable-nls > --enable-gnu-indirect-function --libdir=/usr/local/lib/gcc49 > --libexecdir=/usr/local/libexec/gcc49 --program-suffix=49 > --with-as=/usr/local/bin/as --with-gmp=/usr/local > --with-gxx-include-dir=/usr/local/lib/gcc49/include/c++/ > --with-ld=/usr/local/bin/ld --with-ppl=/usr/local/lib > --with-cloog=/usr/local/lib --with-libiconv-prefix=/usr/local > --with-pkgversion='FreeBSD Ports Collection' --with-system-zlib > --disable-libgcj --enable-languages=c,c++,objc,fortran > --prefix=/usr/local --localstatedir=/var --mandir=/usr/local/man > --infodir=/usr/local/info/gcc49 --build=x86_64-portbld-freebsd9.3 > Thread model: posix > gcc version 4.9.4 20151028 (prerelease) (FreeBSD Ports Collection) > COLLECT_GCC_OPTIONS='-v' '--help' '-mtune=generic' '-march=x86-64' > > /usr/local/libexec/gcc49/gcc/x86_64-portbld-freebsd9.3/4.9.4/cc1 > -quiet -v help-dummy -quiet -dumpbase help-dummy -mtune=generic > -march=x86-64 -auxbase help-dummy -version --help -o /tmp//cc0bsC4i.s > The following options are specific to just the language Ada: > None found. Use --help=Ada to show *all* the options supported by > the Ada front-end > > > .... & many more lines snipped. Observe that the config shows > --with-ppl & --with-cloog, req'd for Graphite > (auto-loop-parallelization), yet my compiles still fail out w/ the > following: > > > Beginning background make WAMGCC=49 all > Initiated at 06:30:01 PM MCST on Saturday, November 14, 2015 > > MakeMPI: both --- > MakeMPI: ../lib/R4/opteron/libmpi.a --- > gcc49 -DNDEBUG -DUNDER_SCORE_SYS -DLOSE_GAMMAL -I../include -I~/inc > -I../Properties -I../TEST -I../pre -march=opteron -mtune=opteron -O3 > -fprefetch-loop-arrays -floo > p-parallelize-all -ftree-parallelize-loops=4 -fopt-info -c mpi.c > mpprime.c > mpi.c:1:0: sorry, unimplemented: Graphite loop optimizations cannot be > used (-fgraphite, -fgraphite-identity, -floop-block, > -floop-interchange, -floop-strip-mine, -fl > oop-parallelize-all, and -ftree-loop-linear) > /* > ^ > mpprime.c:1:0: sorry, unimplemented: Graphite loop optimizations > cannot be used (-fgraphite, -fgraphite-identity, -floop-block, > -floop-interchange, -floop-strip-mine, > -floop-parallelize-all, and -ftree-loop-linear) > /* > ^ > *** [../lib/R4/opteron/libmpi.a] Error code 1 > 1 error > `usual' not remade because of errors. > > > i.e. no Graphite support. A few questions: > > 1. Is this list the proper forum for these questions :-) ? > 2. Are ppl & cloog (both pkg-installed last wqeekend & ready to go) in > fact all that is req'd for Graphite support to work ? > 3. Did the port of gcc4.9 wind up removing the req'd code internally > for Graphite support, so that even w/ the config properly setup, I > still get no Graphite support ? > > > This identical code (accessed via VPATH macro from Makefile over > there) compiles elsewhere on my LAN under Intel icc/ifort & > parallelizes where expected AOK. *Any* clues much appreciated. TIA & > have a good one. more new info: I pkg-upgraded to gcc49-4.9.4.s20151111 this A.M. & retried my compile, still nogo, same messages as above :-/ .... [wam@devbox, pre, 10:48:19am] 463 % which gcc49 /usr/local/bin/gcc49 [wam@devbox, pre, 10:48:25am] 464 % ll `!!` ll `which gcc49` -r-xr-xr-x 3 root wheel 846360 Nov 14 03:50 /usr/local/bin/gcc49* [wam@devbox, pre, 10:48:29am] 465 % uname -a FreeBSD devbox 9.3-RELEASE-p24 FreeBSD 9.3-RELEASE-p24 #0: Sat Aug 22 01:54:44 UTC 2015 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 [wam@devbox, pre, 10:48:37am] 466 % sysctl -a | grep -A8 -B1 hw.model hw.machine: amd64 hw.model: AMD A8-6500 APU with Radeon(tm) HD Graphics hw.ncpu: 4 hw.byteorder: 1234 hw.physmem: 33464279040 hw.usermem: 32952082432 hw.pagesize: 4096 hw.floatingpoint: 1 hw.machine_arch: amd64 hw.realmem: 35416702976 [wam@devbox, pre, 10:50:00am] 467 % *Any* clues appreciated :-). TIA & have a good one. -- William A. Mahaffey III ---------------------------------------------------------------------- "The M1 Garand is without doubt the finest implement of war ever devised by man." -- Gen. George S. Patton Jr. From owner-freebsd-toolchain@freebsd.org Sun Nov 15 19:52:04 2015 Return-Path: Delivered-To: freebsd-toolchain@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 B40C7A30F6B for ; Sun, 15 Nov 2015 19:52:04 +0000 (UTC) (envelope-from gerald@pfeifer.com) Received: from ainaz.pair.com (ainaz.pair.com [209.68.2.66]) (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 8DA821932 for ; Sun, 15 Nov 2015 19:52:04 +0000 (UTC) (envelope-from gerald@pfeifer.com) Received: from [192.168.0.130] (vie-188-118-240-003.dsl.sil.at [188.118.240.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ainaz.pair.com (Postfix) with ESMTPSA id E2BBE3F428; Sun, 15 Nov 2015 14:52:02 -0500 (EST) Date: Sun, 15 Nov 2015 20:52:00 +0100 (CET) From: Gerald Pfeifer To: "William A. Mahaffey III" cc: freebsd-toolchain@freebsd.org Subject: Re: [toolchain] amd64-gcc question In-Reply-To: <56449EF8.7070806@hiwaay.net> Message-ID: References: <56449EF8.7070806@hiwaay.net> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Nov 2015 19:52:04 -0000 On Thu, 12 Nov 2015, William A. Mahaffey III wrote: > I pkg-installed amd64-gcc over the weekend hoping for Graphite > (auto-loop parallelization) support, but no go. When you say "amd64-gcc" where did you obtain that from? As a FreeBSD port/package, or somewhere else? > just did a 'portsnap fetch upgrade' & there is now a port > for amd64-gcc, but it includes no files & no pkg-descr file. This is a little weird. I have packaged GCC 4.6 (lang/gcc46), GCC 4.7 (lang/gcc47), GCC 4.8 (lang/gcc48), GCC 4.9 (lang/gcc49), GCC 5 (lang/gcc5 and lang/gcc5-devel) and GCC 6 snapshot (lang/gcc6-devel) as well as the "canonical" version of GCC (lang/gcc, currently GCC 4.8 and in the process of being moved to GCC 4.9). All of these build and package on amd64, feature pkg-descr, etc. And as a FreeBSD user leveraging the official FreeBSD Ports Collection is the recommended approach. None of them would be called amd64-gcc or similar, though. > I have gotten as far as running 'make showconfig' in the various gcc* & > amd64-gcc directories to see what info I could get on default config > options. In all cases they gave options & said to run 'make config' to > change options. I didn't even see a 'config:' entry in the Makefiles > (probably included from elsewhere, but I didn't chase it). Let's focus on lang/gcc5-devel, which is the most reasonable version to enable Graphite for right now since GCC 5 is the current release series and hence most stable, but also advanced, and the -devel port is more suitable for making changes like this than the "production" variant. And indeed lang/gcc5-devel/Makefile already had the following lines, which is how options handling actually works: OPTIONS_DEFINE= BOOTSTRAP OPTIONS_DEFINE_i386= JAVA OPTIONS_DEFINE_amd64= JAVA OPTIONS_DEFAULT= BOOTSTRAP OPTIONS_DEFAULT_i386= JAVA OPTIONS_DEFAULT_amd64= JAVA > I see no configure files for any of the gcc ports (I have the entire > ports tree downloaded & local, & freshly updated as of a few min. ago). > What is the canonical/BPP (FreeBSD 9.3R) way of recompiling a port with > different config flags ? > > I did find ports/pkgs for the 2 main components apparently needed for > Graphite support (cloog & ppl) & pkg-installed them over the weekend, > so I am ready to go on that front. If you check out the GCC release notes at https://gcc.gnu.org/gcc-5/changes.html you will find that "The Graphite framework for loop optimizations no longer requires the CLooG library, only ISL version 0.14 (recommended) or 0.12.2." I just committed changes to lang/gcc6-devel and lang/gcc5-devel to add support for Graphite with a new option GRAPHITE. This is off by default, but you can enable it, rebuild the port, and then have what you've been looking for. Gerald From owner-freebsd-toolchain@freebsd.org Sun Nov 15 20:03:47 2015 Return-Path: Delivered-To: freebsd-toolchain@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 CF918A3016B for ; Sun, 15 Nov 2015 20:03:47 +0000 (UTC) (envelope-from baptiste.daroussin@gmail.com) Received: from mail-wm0-x235.google.com (mail-wm0-x235.google.com [IPv6:2a00:1450:400c:c09::235]) (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 706401F79 for ; Sun, 15 Nov 2015 20:03:47 +0000 (UTC) (envelope-from baptiste.daroussin@gmail.com) Received: by wmww144 with SMTP id w144so86164056wmw.1 for ; Sun, 15 Nov 2015 12:03:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=otzcnN/KzbM81m13apZKF2SdFetl/7qToszFZ0eysj8=; b=Z1z0a0t80rvE/zEFmpWJKOfB029Geh/5WOeQC/s7qq1QvT7ZNp2x4nFpMsrqB8yHQp engWRVBTBDLRs+bHeYrK14rMsZqEJyvQ8kXdH+u9tyWOqdSXSgfdOrD4jO4uJyJJirT0 TDTkpo9vccn/V1SUAuFqeXNiU2mMhEpgUbXowPo9hJyJ51Hw/rPOsMwIsJ5tEQk77R91 CsQrCP1d/eZhustsPO8ZknGiMw2sPFuIJSGbtYr8AGg3kGJFu4t9XKK00L5VX6ovysUF A++UWvusH9Wi6qtvMVHoK1tDmhrFYk+gU2gILxlSu8qOHftKm8FMyHk3QAlPx7Th7Cai XQIQ== X-Received: by 10.28.52.213 with SMTP id b204mr5736369wma.32.1447617825918; Sun, 15 Nov 2015 12:03:45 -0800 (PST) Received: from ivaldir.etoilebsd.net ([2001:41d0:8:db4c::1]) by smtp.gmail.com with ESMTPSA id e79sm14932961wmd.16.2015.11.15.12.03.44 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 15 Nov 2015 12:03:45 -0800 (PST) Sender: Baptiste Daroussin Date: Sun, 15 Nov 2015 21:03:43 +0100 From: Baptiste Daroussin To: Gerald Pfeifer Cc: "William A. Mahaffey III" , freebsd-toolchain@freebsd.org Subject: Re: [toolchain] amd64-gcc question Message-ID: <20151115200342.GI93991@ivaldir.etoilebsd.net> References: <56449EF8.7070806@hiwaay.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="+PbGPm1eXpwOoWkI" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Nov 2015 20:03:47 -0000 --+PbGPm1eXpwOoWkI Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Nov 15, 2015 at 08:52:00PM +0100, Gerald Pfeifer wrote: > On Thu, 12 Nov 2015, William A. Mahaffey III wrote: > > I pkg-installed amd64-gcc over the weekend hoping for Graphite=20 > > (auto-loop parallelization) support, but no go. >=20 > When you say "amd64-gcc" where did you obtain that from? As a=20 > FreeBSD port/package, or somewhere else? This is a port which is only intended to be used for cross building base wi= th a modern gcc, it is a "bastardized gcc" that should only be used as an extern= al toolchain for building base. >=20 > > just did a 'portsnap fetch upgrade' & there is now a port=20 > > for amd64-gcc, but it includes no files & no pkg-descr file. >=20 > This is a little weird. I have packaged GCC 4.6 (lang/gcc46),=20 > GCC 4.7 (lang/gcc47), GCC 4.8 (lang/gcc48), GCC 4.9 (lang/gcc49),=20 > GCC 5 (lang/gcc5 and lang/gcc5-devel) and GCC 6 snapshot (lang/gcc6-devel) > as well as the "canonical" version of GCC (lang/gcc, currently=20 > GCC 4.8 and in the process of being moved to GCC 4.9). >=20 > All of these build and package on amd64, feature pkg-descr, etc. > And as a FreeBSD user leveraging the official FreeBSD Ports Collection > is the recommended approach. >=20 > None of them would be called amd64-gcc or similar, though. >=20 > > I have gotten as far as running 'make showconfig' in the various gcc* & > > amd64-gcc directories to see what info I could get on default config > > options. In all cases they gave options & said to run 'make config' to > > change options. I didn't even see a 'config:' entry in the Makefiles > > (probably included from elsewhere, but I didn't chase it).=20 >=20 > Let's focus on lang/gcc5-devel, which is the most reasonable version > to enable Graphite for right now since GCC 5 is the current release > series and hence most stable, but also advanced, and the -devel port > is more suitable for making changes like this than the "production" > variant. >=20 > And indeed lang/gcc5-devel/Makefile already had the following lines,=20 > which is how options handling actually works: >=20 > OPTIONS_DEFINE=3D BOOTSTRAP > OPTIONS_DEFINE_i386=3D JAVA > OPTIONS_DEFINE_amd64=3D JAVA > OPTIONS_DEFAULT=3D BOOTSTRAP > OPTIONS_DEFAULT_i386=3D JAVA > OPTIONS_DEFAULT_amd64=3D JAVA >=20 > > I see no configure files for any of the gcc ports (I have the entire=20 > > ports tree downloaded & local, & freshly updated as of a few min. ago).= =20 > > What is the canonical/BPP (FreeBSD 9.3R) way of recompiling a port with= =20 > > different config flags ? > >=20 > > I did find ports/pkgs for the 2 main components apparently needed for= =20 > > Graphite support (cloog & ppl) & pkg-installed them over the weekend,= =20 > > so I am ready to go on that front. >=20 > If you check out the GCC release notes at=20 > https://gcc.gnu.org/gcc-5/changes.html > you will find that "The Graphite framework for loop optimizations no=20 > longer requires the CLooG library, only ISL version 0.14 (recommended)=20 > or 0.12.2." >=20 > I just committed changes to lang/gcc6-devel and lang/gcc5-devel to > add support for Graphite with a new option GRAPHITE. This is off > by default, but you can enable it, rebuild the port, and then have > what you've been looking for. >=20 > Gerald > _______________________________________________ > freebsd-toolchain@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-toolchain > To unsubscribe, send any mail to "freebsd-toolchain-unsubscribe@freebsd.o= rg" --+PbGPm1eXpwOoWkI Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlZI5R4ACgkQ8kTtMUmk6EzmxACggT7dJGDDbxmuKjttIrAfH7sf 47UAnA+rjtuaST2K8Xb9/8s0A2opiocR =lq/0 -----END PGP SIGNATURE----- --+PbGPm1eXpwOoWkI-- From owner-freebsd-toolchain@freebsd.org Sun Nov 15 21:58:40 2015 Return-Path: Delivered-To: freebsd-toolchain@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 72A2BA2FDC0 for ; Sun, 15 Nov 2015 21:58:40 +0000 (UTC) (envelope-from wam@hiwaay.net) Received: from fly.hiwaay.net (fly.hiwaay.net [216.180.54.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3FE9C1C80 for ; Sun, 15 Nov 2015 21:58:40 +0000 (UTC) (envelope-from wam@hiwaay.net) Received: from kabini1.local (dynamic-216-186-213-32.knology.net [216.186.213.32] (may be forged)) (authenticated bits=0) by fly.hiwaay.net (8.13.8/8.13.8/fly) with ESMTP id tAFLwbnJ014271 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Sun, 15 Nov 2015 15:58:38 -0600 Subject: Re: [toolchain] amd64-gcc question References: <56449EF8.7070806@hiwaay.net> To: freebsd-toolchain@freebsd.org From: "William A. Mahaffey III" Message-ID: <5649000D.70704@hiwaay.net> Date: Sun, 15 Nov 2015 16:04:07 -0553.75 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Nov 2015 21:58:40 -0000 On 11/15/15 13:58, Gerald Pfeifer wrote: > On Thu, 12 Nov 2015, William A. Mahaffey III wrote: >> I pkg-installed amd64-gcc over the weekend hoping for Graphite >> (auto-loop parallelization) support, but no go. > When you say "amd64-gcc" where did you obtain that from? As a > FreeBSD port/package, or somewhere else? I pkg-installed it originally, but as of last Monday, there was a port as well, I did a 'portsnap fetch update' (all box-stock ports configs) & there it was .... > >> just did a 'portsnap fetch upgrade' & there is now a port >> for amd64-gcc, but it includes no files & no pkg-descr file. > This is a little weird. I have packaged GCC 4.6 (lang/gcc46), > GCC 4.7 (lang/gcc47), GCC 4.8 (lang/gcc48), GCC 4.9 (lang/gcc49), > GCC 5 (lang/gcc5 and lang/gcc5-devel) and GCC 6 snapshot (lang/gcc6-devel) > as well as the "canonical" version of GCC (lang/gcc, currently > GCC 4.8 and in the process of being moved to GCC 4.9). > > All of these build and package on amd64, feature pkg-descr, etc. > And as a FreeBSD user leveraging the official FreeBSD Ports Collection > is the recommended approach. > > None of them would be called amd64-gcc or similar, though. amd64-gcc-5.2.0 amd64-xtoolchain-gcc-0.1 is what pkg calls them .... > >> I have gotten as far as running 'make showconfig' in the various gcc* & >> amd64-gcc directories to see what info I could get on default config >> options. In all cases they gave options & said to run 'make config' to >> change options. I didn't even see a 'config:' entry in the Makefiles >> (probably included from elsewhere, but I didn't chase it). > Let's focus on lang/gcc5-devel, which is the most reasonable version > to enable Graphite for right now since GCC 5 is the current release > series and hence most stable, but also advanced, and the -devel port > is more suitable for making changes like this than the "production" > variant. > > And indeed lang/gcc5-devel/Makefile already had the following lines, > which is how options handling actually works: > > OPTIONS_DEFINE= BOOTSTRAP > OPTIONS_DEFINE_i386= JAVA > OPTIONS_DEFINE_amd64= JAVA > OPTIONS_DEFAULT= BOOTSTRAP > OPTIONS_DEFAULT_i386= JAVA > OPTIONS_DEFAULT_amd64= JAVA > >> I see no configure files for any of the gcc ports (I have the entire >> ports tree downloaded & local, & freshly updated as of a few min. ago). >> What is the canonical/BPP (FreeBSD 9.3R) way of recompiling a port with >> different config flags ? >> >> I did find ports/pkgs for the 2 main components apparently needed for >> Graphite support (cloog & ppl) & pkg-installed them over the weekend, >> so I am ready to go on that front. > If you check out the GCC release notes at > https://gcc.gnu.org/gcc-5/changes.html > you will find that "The Graphite framework for loop optimizations no > longer requires the CLooG library, only ISL version 0.14 (recommended) > or 0.12.2." > > I just committed changes to lang/gcc6-devel and lang/gcc5-devel to > add support for Graphite with a new option GRAPHITE. This is off > by default, but you can enable it, rebuild the port, and then have > what you've been looking for. > > Gerald *Excellent*, thanks muchly :-). I'll buy you a beer next time we meet ;-) .... -- William A. Mahaffey III ---------------------------------------------------------------------- "The M1 Garand is without doubt the finest implement of war ever devised by man." -- Gen. George S. Patton Jr. From owner-freebsd-toolchain@freebsd.org Sun Nov 15 22:07:05 2015 Return-Path: Delivered-To: freebsd-toolchain@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 9B396A2FF55 for ; Sun, 15 Nov 2015 22:07:05 +0000 (UTC) (envelope-from baptiste.daroussin@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 20CF81F11 for ; Sun, 15 Nov 2015 22:07:05 +0000 (UTC) (envelope-from baptiste.daroussin@gmail.com) Received: by wmvv187 with SMTP id v187so150484784wmv.1 for ; Sun, 15 Nov 2015 14:07:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=6BBIZzLGhZb0rOxUIjR7xrCNVl16Ome0ovGGjQn98h0=; b=qA7alSTgsi4oLxDD4ZwD4Q1b+3S5tTpfSjvpFNiUH4RAoUCbzuC7D9Y48REsoynST7 xVhnBQyBsSVbgpycXkxXVXx9saW53k7JGfn15QIHmrzMKJ4smc2RcphtOyPuy9wYY1rx n/ofnRccbddBgDBsvZ4YFKq8V2XGcGJLpsuVHejhPGyn+2r0zkvp8ztqptfu7IU9i20n uSQ9Pwt1++f5NKvjRmAlbdd08Seqm25ZGRZIXR6dwcU6OJ60UPHOBbPMvG/E+PS9D9a4 YOhvtfx100tjqlwSk7g1L9a6qXB+1MOYJ+9m/JZ2pfxL6pe0qrgQfbrYn9MT45efG5lt dKlg== X-Received: by 10.28.23.211 with SMTP id 202mr14641719wmx.81.1447625222874; Sun, 15 Nov 2015 14:07:02 -0800 (PST) Received: from ivaldir.etoilebsd.net ([2001:41d0:8:db4c::1]) by smtp.gmail.com with ESMTPSA id da10sm8251254wjb.22.2015.11.15.14.07.01 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 15 Nov 2015 14:07:02 -0800 (PST) Sender: Baptiste Daroussin Date: Sun, 15 Nov 2015 23:07:00 +0100 From: Baptiste Daroussin To: "William A. Mahaffey III" Cc: freebsd-toolchain@freebsd.org Subject: Re: [toolchain] amd64-gcc question Message-ID: <20151115220658.GK93991@ivaldir.etoilebsd.net> References: <56449EF8.7070806@hiwaay.net> <5649000D.70704@hiwaay.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="IA03tywDYuoVKXrw" Content-Disposition: inline In-Reply-To: <5649000D.70704@hiwaay.net> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Nov 2015 22:07:05 -0000 --IA03tywDYuoVKXrw Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Nov 15, 2015 at 04:04:07PM -0553, William A. Mahaffey III wrote: > On 11/15/15 13:58, Gerald Pfeifer wrote: > > On Thu, 12 Nov 2015, William A. Mahaffey III wrote: > >> I pkg-installed amd64-gcc over the weekend hoping for Graphite > >> (auto-loop parallelization) support, but no go. > > When you say "amd64-gcc" where did you obtain that from? As a > > FreeBSD port/package, or somewhere else? >=20 > I pkg-installed it originally, but as of last Monday, there was a port=20 > as well, I did a 'portsnap fetch update' (all box-stock ports configs) &= =20 > there it was .... >=20 > > > >> just did a 'portsnap fetch upgrade' & there is now a port > >> for amd64-gcc, but it includes no files & no pkg-descr file. > > This is a little weird. I have packaged GCC 4.6 (lang/gcc46), > > GCC 4.7 (lang/gcc47), GCC 4.8 (lang/gcc48), GCC 4.9 (lang/gcc49), > > GCC 5 (lang/gcc5 and lang/gcc5-devel) and GCC 6 snapshot (lang/gcc6-dev= el) > > as well as the "canonical" version of GCC (lang/gcc, currently > > GCC 4.8 and in the process of being moved to GCC 4.9). > > > > All of these build and package on amd64, feature pkg-descr, etc. > > And as a FreeBSD user leveraging the official FreeBSD Ports Collection > > is the recommended approach. > > > > None of them would be called amd64-gcc or similar, though. >=20 > amd64-gcc-5.2.0 > amd64-xtoolchain-gcc-0.1 >=20 > is what pkg calls them .... Those are cross toolchain packages to cross build base with modern gcc Bapt --IA03tywDYuoVKXrw Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlZJAgIACgkQ8kTtMUmk6EwaNwCeNXOSKgUySj/kaFG0kDvNQXux /M8AmwU6A6kISxibkAEJ9iK7UmOn/4ro =1Zps -----END PGP SIGNATURE----- --IA03tywDYuoVKXrw-- From owner-freebsd-toolchain@freebsd.org Tue Nov 17 15:27:30 2015 Return-Path: Delivered-To: freebsd-toolchain@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 CD451A30635 for ; Tue, 17 Nov 2015 15:27:30 +0000 (UTC) (envelope-from wam@hiwaay.net) Received: from fly.hiwaay.net (fly.hiwaay.net [216.180.54.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9BA801827 for ; Tue, 17 Nov 2015 15:27:30 +0000 (UTC) (envelope-from wam@hiwaay.net) Received: from kabini1.local (dynamic-216-186-213-32.knology.net [216.186.213.32] (may be forged)) (authenticated bits=0) by fly.hiwaay.net (8.13.8/8.13.8/fly) with ESMTP id tAHFRMIh005021 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Tue, 17 Nov 2015 09:27:22 -0600 To: FreeBSD toolchain mailing list !!!! From: "William A. Mahaffey III" Subject: GCC 4.8.5 compiler bug Message-ID: <564B4759.5050001@hiwaay.net> Date: Tue, 17 Nov 2015 09:32:51 -0553.75 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="------------090109030806060200020909" X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Nov 2015 15:27:30 -0000 This is a multi-part message in MIME format. --------------090109030806060200020909 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit I have found & apparently isolated what looks like a compiler bug in (pkg-installed, box-stock) gcc48 under FreeBSD 9.3R, see attached. I also prepped a tarball w/ the files that produced the problem for me. Do I post that here or to GNU ? TIA & have a good one .... -- William A. Mahaffey III ---------------------------------------------------------------------- "The M1 Garand is without doubt the finest implement of war ever devised by man." -- Gen. George S. Patton Jr. --------------090109030806060200020909 Content-Type: text/plain; charset=UTF-8; name="LIST.testGCC.txt" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="LIST.testGCC.txt" W3dhbUBkZXZib3gsIHV0aWxzLCA5OjI0OjE3YW1dIDc3MCAlIG1ha2UKZ2NjNDggLUROREVC VUcgLURVTkRFUl9TQ09SRV9TWVMgLURMT1NFX0dBTU1BTCAtSS4uL2luY2x1ZGUgLUkuLi9Q cm9wZXJ0aWVzIC1JLi4vVEVTVCAtSS4uL3ByZSAtSS91c3IvbG9jYWwvaW5jbHVkZSAgLW1h cmNoPW9wdGVyb24gLW10dW5lPW9wdGVyb24gLU8zIC1mcHJlZmV0Y2gtbG9vcC1hcnJheXMg LWZvcHQtaW5mby1sb29wLW9wdGltaXplZCAtbWFyY2g9b3B0ZXJvbiAtbXR1bmU9b3B0ZXJv biAtRFA2NF9CSVQgLWMgZ2F1c3MuY3BwCmdhdXNzLmNwcDogSW4gZnVuY3Rpb24gJ2ludCB0 ZXN0R2F1c3MoY2hhciosIGludCwgdWludCknOgpnYXVzcy5jcHA6MzMyOjQzOiBlcnJvcjog J1ByaW50ZEdNJyB3YXMgbm90IGRlY2xhcmVkIGluIHRoaXMgc2NvcGUKICBQcmludGRHTSAo c3RkZXJyLCAiQSIsIEEsIEZBTFNFLCAxMCwgTiwgTiksIFByaW50ZEEgKHN0ZGVyciwgIkIi LCBCLCAxMCwgTiksIGZwcmludGYgKHN0ZGVyciwgIlxuIiksIGZmbHVzaCAoTlVMTCk7CiAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBeCmdhdXNzLmNwcDoz MzI6NzY6IGVycm9yOiAnUHJpbnRkQScgd2FzIG5vdCBkZWNsYXJlZCBpbiB0aGlzIHNjb3Bl CiAgUHJpbnRkR00gKHN0ZGVyciwgIkEiLCBBLCBGQUxTRSwgMTAsIE4sIE4pLCBQcmludGRB IChzdGRlcnIsICJCIiwgQiwgMTAsIE4pLCBmcHJpbnRmIChzdGRlcnIsICJcbiIpLCBmZmx1 c2ggKE5VTEwpOwogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgXgpnYXVzcy5jcHA6IEluIGZ1bmN0 aW9uICdpbnQgVGVzdEdhdXNzQ1BQKGNoYXIqLCBmbG9hdCwgaW50LCB1aW50KSc6CmdhdXNz LmNwcDozNDI6Mzg6IHdhcm5pbmc6IGRlcHJlY2F0ZWQgY29udmVyc2lvbiBmcm9tIHN0cmlu ZyBjb25zdGFudCB0byAnY2hhcionIFstV3dyaXRlLXN0cmluZ3NdCiAgICAgdGVzdEdhdXNz ICgiVGVzdEdhdXNzKEMrKykiLCAyLCAyKTsKICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICBeCmdhdXNzLmNwcDozNDM6Mzg6IHdhcm5pbmc6IGRlcHJlY2F0ZWQgY29u dmVyc2lvbiBmcm9tIHN0cmluZyBjb25zdGFudCB0byAnY2hhcionIFstV3dyaXRlLXN0cmlu Z3NdCiAgICAgdGVzdEdhdXNzICgiVGVzdEdhdXNzKEMrKykiLCAyLCAzKTsKICAgICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICBeCmdhdXNzLmNwcDozNDQ6Mzg6IHdhcm5p bmc6IGRlcHJlY2F0ZWQgY29udmVyc2lvbiBmcm9tIHN0cmluZyBjb25zdGFudCB0byAnY2hh cionIFstV3dyaXRlLXN0cmluZ3NdCiAgICAgdGVzdEdhdXNzICgiVGVzdEdhdXNzKEMrKyki LCAyLCA0KTsKICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBeCmdhdXNz LmNwcDozNDU6Mzg6IHdhcm5pbmc6IGRlcHJlY2F0ZWQgY29udmVyc2lvbiBmcm9tIHN0cmlu ZyBjb25zdGFudCB0byAnY2hhcionIFstV3dyaXRlLXN0cmluZ3NdCiAgICAgdGVzdEdhdXNz ICgiVGVzdEdhdXNzKEMrKykiLCAyLCA5KTsKICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICBeCmdhdXNzLmNwcDozNDY6NDU6IHdhcm5pbmc6IGRlcHJlY2F0ZWQgY29u dmVyc2lvbiBmcm9tIHN0cmluZyBjb25zdGFudCB0byAnY2hhcionIFstV3dyaXRlLXN0cmlu Z3NdCiAgICAgdGVzdEdhdXNzICgiVGVzdEdhdXNzKEMrKykiLCBjaGF0dHksIDEwMCk7CiAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIF4KZ2F1c3MuY3Bw OjM0Nzo0NTogd2FybmluZzogZGVwcmVjYXRlZCBjb252ZXJzaW9uIGZyb20gc3RyaW5nIGNv bnN0YW50IHRvICdjaGFyKicgWy1Xd3JpdGUtc3RyaW5nc10KICAgICB0ZXN0R2F1c3MgKCJU ZXN0R2F1c3MoQysrKSIsIGNoYXR0eSwgMjAwKTsKICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgICAgXgpnYXVzcy5jcHA6MzQ4OjQ1OiB3YXJuaW5nOiBkZXBy ZWNhdGVkIGNvbnZlcnNpb24gZnJvbSBzdHJpbmcgY29uc3RhbnQgdG8gJ2NoYXIqJyBbLVd3 cml0ZS1zdHJpbmdzXQogICAgIHRlc3RHYXVzcyAoIlRlc3RHYXVzcyhDKyspIiwgY2hhdHR5 LCA1MDApOwogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBe CmdhdXNzLmNwcDozNDk6NDY6IHdhcm5pbmc6IGRlcHJlY2F0ZWQgY29udmVyc2lvbiBmcm9t IHN0cmluZyBjb25zdGFudCB0byAnY2hhcionIFstV3dyaXRlLXN0cmluZ3NdCiAgICAgdGVz dEdhdXNzICgiVGVzdEdhdXNzKEMrKykiLCBjaGF0dHksIDEwMDApOwogICAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgXgpnYXVzcy5jcHA6MzUwOjQ2OiB3 YXJuaW5nOiBkZXByZWNhdGVkIGNvbnZlcnNpb24gZnJvbSBzdHJpbmcgY29uc3RhbnQgdG8g J2NoYXIqJyBbLVd3cml0ZS1zdHJpbmdzXQogICAgIHRlc3RHYXVzcyAoIlRlc3RHYXVzcyhD KyspIiwgY2hhdHR5LCAyMDAwKTsKICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgIF4KKioqIFsuLi9saWIvb3B0ZXJvbi9saWJ1dGlscy5hXSBFcnJvciBj b2RlIDEgKGNvbnRpbnVpbmcpCmB1c3VhbCcgbm90IHJlbWFkZSBiZWNhdXNlIG9mIGVycm9y cy4KMSBlcnJvcgpbd2FtQGRldmJveCwgdXRpbHMsIDk6MjQ6MjJhbV0gNzcxICUgdW5hbWUg LWEKRnJlZUJTRCBkZXZib3ggOS4zLVJFTEVBU0UtcDI0IEZyZWVCU0QgOS4zLVJFTEVBU0Ut cDI0ICMwOiBTYXQgQXVnIDIyIDAxOjU0OjQ0IFVUQyAyMDE1ICAgICByb290QGFtZDY0LWJ1 aWxkZXIuZGFlbW9ub2xvZ3kubmV0Oi91c3Ivb2JqL3Vzci9zcmMvc3lzL0dFTkVSSUMgIGFt ZDY0Clt3YW1AZGV2Ym94LCB1dGlscywgOToyNDoyNWFtXSA3NzIgJSBnY2M0OCAtLXZlcnNp b24KZ2NjNDggKEZyZWVCU0QgUG9ydHMgQ29sbGVjdGlvbikgNC44LjUKQ29weXJpZ2h0IChD KSAyMDE1IEZyZWUgU29mdHdhcmUgRm91bmRhdGlvbiwgSW5jLgpUaGlzIGlzIGZyZWUgc29m dHdhcmU7IHNlZSB0aGUgc291cmNlIGZvciBjb3B5aW5nIGNvbmRpdGlvbnMuICBUaGVyZSBp cyBOTwp3YXJyYW50eTsgbm90IGV2ZW4gZm9yIE1FUkNIQU5UQUJJTElUWSBvciBGSVRORVNT IEZPUiBBIFBBUlRJQ1VMQVIgUFVSUE9TRS4KClt3YW1AZGV2Ym94LCB1dGlscywgOToyNDoy N2FtXSA3NzMgJQo= --------------090109030806060200020909-- From owner-freebsd-toolchain@freebsd.org Tue Nov 17 23:50:05 2015 Return-Path: Delivered-To: freebsd-toolchain@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 9EF6DA31D7C for ; Tue, 17 Nov 2015 23:50:05 +0000 (UTC) (envelope-from gerald@pfeifer.com) Received: from ainaz.pair.com (ainaz.pair.com [209.68.2.66]) (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 8044F1FC8 for ; Tue, 17 Nov 2015 23:50:04 +0000 (UTC) (envelope-from gerald@pfeifer.com) Received: from anthias (unknown [87.213.41.176]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ainaz.pair.com (Postfix) with ESMTPSA id 15DD03F42C; Tue, 17 Nov 2015 18:49:56 -0500 (EST) Date: Wed, 18 Nov 2015 00:49:55 +0100 (CET) From: Gerald Pfeifer To: "William A. Mahaffey III" cc: freebsd-toolchain@freebsd.org Subject: Re: [toolchain] GCC 4.8.5 compiler bug In-Reply-To: <564B4759.5050001@hiwaay.net> Message-ID: References: <564B4759.5050001@hiwaay.net> MIME-Version: 1.0 Content-Type: text/plain; CHARSET=US-ASCII; FORMAT=flowed X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Nov 2015 23:50:05 -0000 Hi William, On Tue, 17 Nov 2015, William A. Mahaffey III wrote: > I have found & apparently isolated what looks like a compiler bug in > (pkg-installed, box-stock) gcc48 under FreeBSD 9.3R, see attached. I > also prepped a tarball w/ the files that produced the problem for me. > Do I post that here or to GNU ? TIA & have a good one .... GCC 4.8 is a little old, and most likely won't attract attention by upstream developers. Does this reproduce with newer version such as GCC 5? If so, that would make a report with higher chances of getting addressed. If not, can you use such a newer version? Gerald From owner-freebsd-toolchain@freebsd.org Wed Nov 18 04:55:42 2015 Return-Path: Delivered-To: freebsd-toolchain@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 EDB10A31198 for ; Wed, 18 Nov 2015 04:55:42 +0000 (UTC) (envelope-from wam@hiwaay.net) Received: from fly.hiwaay.net (fly.hiwaay.net [216.180.54.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9E0EF122F for ; Wed, 18 Nov 2015 04:55:42 +0000 (UTC) (envelope-from wam@hiwaay.net) Received: from kabini1.local (dynamic-216-186-213-32.knology.net [216.186.213.32] (may be forged)) (authenticated bits=0) by fly.hiwaay.net (8.13.8/8.13.8/fly) with ESMTP id tAI4tdc5000610 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Tue, 17 Nov 2015 22:55:40 -0600 Subject: Re: [toolchain] GCC 4.8.5 compiler bug References: <564B4759.5050001@hiwaay.net> Cc: freebsd-toolchain@freebsd.org From: "William A. Mahaffey III" Message-ID: <564C04CB.6010903@hiwaay.net> Date: Tue, 17 Nov 2015 23:01:09 -0553.75 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Nov 2015 04:55:43 -0000 On 11/17/15 17:56, Gerald Pfeifer wrote: > Hi William, > > On Tue, 17 Nov 2015, William A. Mahaffey III wrote: >> I have found & apparently isolated what looks like a compiler bug in >> (pkg-installed, box-stock) gcc48 under FreeBSD 9.3R, see attached. I >> also prepped a tarball w/ the files that produced the problem for me. >> Do I post that here or to GNU ? TIA & have a good one .... > > GCC 4.8 is a little old, and most likely won't attract attention > by upstream developers. > > Does this reproduce with newer version such as GCC 5? If so, that > would make a report with higher chances of getting addressed. If > not, can you use such a newer version? > > Gerald Yes (occurred on 5.2.1 originally), that's why I bumped back to 4.8.5, I thought the newer development version might have some new 'features' that were acting up .... -- William A. Mahaffey III ---------------------------------------------------------------------- "The M1 Garand is without doubt the finest implement of war ever devised by man." -- Gen. George S. Patton Jr. From owner-freebsd-toolchain@freebsd.org Fri Nov 20 16:54:53 2015 Return-Path: Delivered-To: freebsd-toolchain@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 F0662A33034; Fri, 20 Nov 2015 16:54:53 +0000 (UTC) (envelope-from mmoll@darkthrone.kvedulv.de) Received: from darkthrone.kvedulv.de (darkthrone.kvedulv.de [IPv6:2001:1578:400:101::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "darkthrone.kvedulv.de", Issuer "StartCom Class 1 Primary Intermediate Server CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 8C5011576; Fri, 20 Nov 2015 16:54:50 +0000 (UTC) (envelope-from mmoll@darkthrone.kvedulv.de) Received: by darkthrone.kvedulv.de (Postfix, from userid 666) id 9228ADB5; Fri, 20 Nov 2015 17:54:46 +0100 (CET) Date: Fri, 20 Nov 2015 17:54:46 +0100 From: Michael Moll To: freebsd-arm@FreeBSD.org, freebsd-toolchain@FreeBSD.org Subject: lang/ruby2* build failure on arm Message-ID: <20151120165446.GB48644@darkthrone.kvedulv.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="zhXaljGHf11kAtnf" Content-Disposition: inline User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Nov 2015 16:54:54 -0000 --zhXaljGHf11kAtnf Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hello, first, sorry for cross-posting this to arm and toolchain, but I'm unsure in which direction this will go... please CC me, as I'm not subscribed to any of the both lists. In r384323 (ports) swills@ fixed the build of the lang/ruby2* ports, however, on a recent CURRENT on armv6hf I'm getting: checking for setjmp type... configure: error: _setjmp is not available Reverting that change leads to a working Ruby, so the question here is: Which OSVERSION did bring in that change? I'm suspecting the LLVM 3.7 import, but have no further data to back this claim. Any hints? --=20 Michael Moll --zhXaljGHf11kAtnf Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCgAGBQJWT1BVAAoJEHSbfGivsRbHM8IQAIPkoKtIyW7FOH9CAyNsSGL8 dhWQxgtXDeAaKEj+MXeS8fP9vngVGvsKaPpVnfly7EcoZLxAYssJAWDw0DHeZaq8 9AbAeDXdueB317XctlugidOL5hsF8b08imKsiR0dFMuX/i0+XY646sdVwLMKkMMh REPtoB2YWcbXoc/wyg1+igNa9bbK2JJ3qun4DUKqOepAZ5oG9ToJX/X6idZBW1TV AfBdPnPncewLXeXtWI2IPVR2KcFd3mINRTAbGg0ugLejQwoDIoi/8r2LGBzNsw7n yn2AoytgB7LKDR2KFpFrvEhP55+N7u8ddJCMWZnIzDv9fUukdWgKJQu2l201z3xH JkCFAF2NfXa1LKNT3dFh6fPvtF4OQb0LRlhxQVsqVtNZM7b/HcUbGiuztwPnh6SV HkKiv2hl1SdrAYYyomSUCq2LO89rvKzBrdSZNHNqORKS+DdvZQxG5psRycU6GbBJ Xazly71rS3OjykBJHkauG6clUsjmLXNWYEj9ulCCqPgeFRHxoC69qH2iNxhBKFs+ aowyBHuhDJ/N2FhZqnnTb0m3EnxEBeaDQJcemjYoy6QVBe40TmjoQ7mfShEHBHY9 Qmx74kk/m9b+Lb+zosK+xPIPxVY9D0UJx+CfPp2Isz+8hqGjg1xdqkjsOGajCjVK Q38KTsr7JZJAy/dtXdk3 =bBdv -----END PGP SIGNATURE----- --zhXaljGHf11kAtnf-- From owner-freebsd-toolchain@freebsd.org Fri Nov 20 17:05:06 2015 Return-Path: Delivered-To: freebsd-toolchain@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 E8315A33298; Fri, 20 Nov 2015 17:05:06 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from tensor.andric.com (tensor.andric.com [87.251.56.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "tensor.andric.com", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A8B5B1A17; Fri, 20 Nov 2015 17:05:06 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from [IPv6:2001:7b8:3a7::454a:18fd:5b4d:d49] (unknown [IPv6:2001:7b8:3a7:0:454a:18fd:5b4d:d49]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 19A331CBF0; Fri, 20 Nov 2015 18:04:58 +0100 (CET) Subject: Re: lang/ruby2* build failure on arm Mime-Version: 1.0 (Mac OS X Mail 9.1 \(3096.5\)) Content-Type: multipart/signed; boundary="Apple-Mail=_CEC89FE4-DAFF-45B8-8024-9F0723F4C4F7"; protocol="application/pgp-signature"; micalg=pgp-sha1 X-Pgp-Agent: GPGMail 2.6b2 From: Dimitry Andric In-Reply-To: <20151120165446.GB48644@darkthrone.kvedulv.de> Date: Fri, 20 Nov 2015 18:04:53 +0100 Cc: freebsd-arm@FreeBSD.org, freebsd-toolchain@FreeBSD.org Message-Id: <963F064D-2B30-40E4-9F09-31C9121CE80A@FreeBSD.org> References: <20151120165446.GB48644@darkthrone.kvedulv.de> To: Michael Moll X-Mailer: Apple Mail (2.3096.5) X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Nov 2015 17:05:07 -0000 --Apple-Mail=_CEC89FE4-DAFF-45B8-8024-9F0723F4C4F7 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii On 20 Nov 2015, at 17:54, Michael Moll wrote: > > first, sorry for cross-posting this to arm and toolchain, but I'm unsure > in which direction this will go... please CC me, as I'm not subscribed > to any of the both lists. > > In r384323 (ports) swills@ fixed the build of the lang/ruby2* ports, > however, on a recent CURRENT on armv6hf I'm getting: > checking for setjmp type... configure: error: _setjmp is not available Check the config.log file for further details. Why does the configure script conclude that _setjmp is not available? -Dimitry --Apple-Mail=_CEC89FE4-DAFF-45B8-8024-9F0723F4C4F7 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.28 iEYEARECAAYFAlZPUrkACgkQsF6jCi4glqMIbgCdG5Y9JUZVGBGm5y52f3uVcqRm hecAn15pujR9IixSqStcILwWpnp2seMf =auXx -----END PGP SIGNATURE----- --Apple-Mail=_CEC89FE4-DAFF-45B8-8024-9F0723F4C4F7-- From owner-freebsd-toolchain@freebsd.org Fri Nov 20 19:35:06 2015 Return-Path: Delivered-To: freebsd-toolchain@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 37964A32610; Fri, 20 Nov 2015 19:35:06 +0000 (UTC) (envelope-from freebsd-lists@gromit.dlib.vt.edu) Received: from gromit.dlib.vt.edu (gromit.dlib.vt.edu [128.173.126.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gromit.dlib.vt.edu", Issuer "Chumby Certificate Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 13BA61C97; Fri, 20 Nov 2015 19:35:05 +0000 (UTC) (envelope-from freebsd-lists@gromit.dlib.vt.edu) Received: from pmather.lib.vt.edu (pmather.lib.vt.edu [128.173.126.193]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by gromit.dlib.vt.edu (Postfix) with ESMTPSA id B24D0459; Fri, 20 Nov 2015 14:29:29 -0500 (EST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) Subject: Re: lang/ruby2* build failure on arm From: Paul Mather In-Reply-To: <20151120165446.GB48644@darkthrone.kvedulv.de> Date: Fri, 20 Nov 2015 14:29:24 -0500 Cc: freebsd-arm@FreeBSD.org, freebsd-toolchain@FreeBSD.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <20151120165446.GB48644@darkthrone.kvedulv.de> To: Michael Moll X-Mailer: Apple Mail (2.2104) X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Nov 2015 19:35:06 -0000 On Nov 20, 2015, at 11:54 AM, Michael Moll wrote: > Hello, >=20 > first, sorry for cross-posting this to arm and toolchain, but I'm = unsure > in which direction this will go... please CC me, as I'm not subscribed > to any of the both lists. >=20 > In r384323 (ports) swills@ fixed the build of the lang/ruby2* ports, > however, on a recent CURRENT on armv6hf I'm getting: > checking for setjmp type... configure: error: _setjmp is not available >=20 > Reverting that change leads to a working Ruby, so the question here = is: > Which OSVERSION did bring in that change? I'm suspecting the LLVM 3.7 > import, but have no further data to back this claim. >=20 > Any hints? According to my Poudriere build logs, the last successful build I was = able to do of ruby21 for FreeBSD/arm 11-CURRENT was on 2015-08-07 = (ruby21-2.1.6,1). That was using FreeBSD clang version 3.6.1 = (tags/RELEASE_361/final 237755) 20150525. I have no successful builds since the update to FreeBSD clang version = 3.7.0 (tags/RELEASE_370/final 246257) 20150906. It fails with the same = error you report above. Cheers, Paul. From owner-freebsd-toolchain@freebsd.org Fri Nov 20 22:02:14 2015 Return-Path: Delivered-To: freebsd-toolchain@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 F22E5A34523; Fri, 20 Nov 2015 22:02:14 +0000 (UTC) (envelope-from mmoll@darkthrone.kvedulv.de) Received: from darkthrone.kvedulv.de (darkthrone.kvedulv.de [IPv6:2001:1578:400:101::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "darkthrone.kvedulv.de", Issuer "StartCom Class 1 Primary Intermediate Server CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id B49E11B0A; Fri, 20 Nov 2015 22:02:14 +0000 (UTC) (envelope-from mmoll@darkthrone.kvedulv.de) Received: by darkthrone.kvedulv.de (Postfix, from userid 666) id B03BBEDA; Fri, 20 Nov 2015 23:02:10 +0100 (CET) Date: Fri, 20 Nov 2015 23:02:10 +0100 From: Michael Moll To: Dimitry Andric Cc: freebsd-arm@FreeBSD.org, freebsd-toolchain@FreeBSD.org Subject: Re: lang/ruby2* build failure on arm Message-ID: <20151120220210.GC48644@darkthrone.kvedulv.de> References: <20151120165446.GB48644@darkthrone.kvedulv.de> <963F064D-2B30-40E4-9F09-31C9121CE80A@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="IiVenqGWf+H9Y6IX" Content-Disposition: inline In-Reply-To: <963F064D-2B30-40E4-9F09-31C9121CE80A@FreeBSD.org> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Nov 2015 22:02:15 -0000 --IiVenqGWf+H9Y6IX Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, On Fri, Nov 20, 2015 at 06:04:53PM +0100, Dimitry Andric wrote: > > In r384323 (ports) swills@ fixed the build of the lang/ruby2* ports, > > however, on a recent CURRENT on armv6hf I'm getting: > > checking for setjmp type... configure: error: _setjmp is not available >=20 > Check the config.log file for further details. Why does the configure > script conclude that _setjmp is not available? The whole file is available as http://space.kvedulv.de/ruby_arm_config.log,= the output =66rom the specific test is: conftest.c:340:20: error: __builtin_longjmp is not supported for the curren= t target void t(void) {__builtin_longjmp((void **) jb, 1);} ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ conftest.c:341:29: error: __builtin_setjmp is not supported for the current= target int jump(void) {(void)(__builtin_setjmp((void **) jb) ? 1 : 0);= return 0;} ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Regards --=20 Michael Moll --IiVenqGWf+H9Y6IX Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCgAGBQJWT5hhAAoJEHSbfGivsRbHUUYP/A6Mt+oeHSEamnj6qVAGB3hD 0+i4P8z13h6UZAL1Sk6OSri7PsV92V2XOq2zY3z5xRTQaeBnqfxkHlUhlwGcAiT2 k7hu/lllf9TzKn8UxwXvXLkGMnutKw4tIK926OpMr/WEHiYHjBZkkuMPM0dGe/yT zGB7Bzoyz5c3SZSfrmM7afBgWUzQJcaQBJllTwWDlgqwByNLb58azgohdA7GlPMA ZMU5mdbvjzvEpqee1zp3qntlir8uHe6Od+GIee8XuaQyxmJFR2Hjhkul8mAM8aHi yuILqur4kfQCBovQX5O7t+pMLutpziAGLqsZFM5E7EOlVoH0mase9K+Iosldwp1w cKOv7yX1lUCdK+2QT0/qTn/DSq02jiXfTqf7mJSsPnqMVplNsUxFJWDw7DwlTnR7 AFd3mT5QL9dcE1oBv8uBEMe+S0WIsEYtZgdaHtGubfNK67hGBwdcAEP4F5ErY5cL lFxDfFWVUMZFZd4evYR1QJrUnbgIMptpsRg/M/q73gffTA+MPEl8mNz++NY4wlt6 qVDAgQTZTkEKE8tzFFpv9g4CzVmYpvQOq8gPTNT2z1qlt4ziIwm5Qup1CSZR1+i0 8Eah8AFDwDK7aLU0DiPPBGgGqvdZL1vtaEOivT7inVXEjiYe3c1+eWzIl3wLGIzC lGyhiqFaSRl20vlJQ1hy =6lJ0 -----END PGP SIGNATURE----- --IiVenqGWf+H9Y6IX-- From owner-freebsd-toolchain@freebsd.org Fri Nov 20 22:18:12 2015 Return-Path: Delivered-To: freebsd-toolchain@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 335F7A347CE; Fri, 20 Nov 2015 22:18:12 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from tensor.andric.com (tensor.andric.com [IPv6:2001:7b8:3a7:1:2d0:b7ff:fea0:8c26]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "tensor.andric.com", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D97D815C8; Fri, 20 Nov 2015 22:18:11 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from [IPv6:2001:7b8:3a7::454a:18fd:5b4d:d49] (unknown [IPv6:2001:7b8:3a7:0:454a:18fd:5b4d:d49]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id AB2271CC27; Fri, 20 Nov 2015 23:18:09 +0100 (CET) Subject: Re: lang/ruby2* build failure on arm Mime-Version: 1.0 (Mac OS X Mail 9.1 \(3096.5\)) Content-Type: multipart/signed; boundary="Apple-Mail=_708D8047-CBEA-48C1-BAB2-B34E0AD72A98"; protocol="application/pgp-signature"; micalg=pgp-sha1 X-Pgp-Agent: GPGMail 2.6b2 From: Dimitry Andric In-Reply-To: <20151120220210.GC48644@darkthrone.kvedulv.de> Date: Fri, 20 Nov 2015 23:18:09 +0100 Cc: freebsd-arm@FreeBSD.org, freebsd-toolchain@FreeBSD.org Message-Id: <903D1E22-D3E4-4DDA-BBF3-F8DDFAE91B56@FreeBSD.org> References: <20151120165446.GB48644@darkthrone.kvedulv.de> <963F064D-2B30-40E4-9F09-31C9121CE80A@FreeBSD.org> <20151120220210.GC48644@darkthrone.kvedulv.de> To: Michael Moll X-Mailer: Apple Mail (2.3096.5) X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Nov 2015 22:18:12 -0000 --Apple-Mail=_708D8047-CBEA-48C1-BAB2-B34E0AD72A98 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 20 Nov 2015, at 23:02, Michael Moll wrote: >=20 > On Fri, Nov 20, 2015 at 06:04:53PM +0100, Dimitry Andric wrote: >>> In r384323 (ports) swills@ fixed the build of the lang/ruby2* ports, >>> however, on a recent CURRENT on armv6hf I'm getting: >>> checking for setjmp type... configure: error: _setjmp is not = available >>=20 >> Check the config.log file for further details. Why does the = configure >> script conclude that _setjmp is not available? >=20 > The whole file is available as = http://space.kvedulv.de/ruby_arm_config.log, the output > from the specific test is: >=20 > conftest.c:340:20: error: __builtin_longjmp is not supported for the = current target > void t(void) {__builtin_longjmp((void **) jb, 1);} > ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > conftest.c:341:29: error: __builtin_setjmp is not supported for the = current target > int jump(void) {(void)(__builtin_setjmp((void **) jb) ? 1 : = 0); return 0;} > ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Right, but that is not the real problem. Earlier on, the configure script is checking for the regular _setjmp(): configure:16921: checking for _setjmp configure:16921: cc -o conftest -O -pipe -fno-strict-aliasing = -I/usr/local/include -fstack-protector conftest.c -lcrypt -lm = -lpthread -L/usr/local/lib >&5 conftest.c:228:6: warning: declaration of built-in function '_setjmp' = requires inclusion of the header [-Wbuiltin-requires-header] char _setjmp (); ^ conftest.c:239:17: error: too few arguments to function call, expected = 1, have 0 return _setjmp (); ~~~~~~~~~^ 1 warning and 1 error generated. configure:16921: $? =3D 1 configure: failed program was: As to why GNU configure tries to call this without arguments, is beyond me. To work around its brokenness, I would set ac_cv_func__setjmp to yes before calling configure. Or attempt to unbreak autoconf, but that is a truly Herculean task. :-) -Dimitry --Apple-Mail=_708D8047-CBEA-48C1-BAB2-B34E0AD72A98 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.28 iEYEARECAAYFAlZPnCEACgkQsF6jCi4glqOOpwCeLdlgHZmDgIi9XZtNgnUIsQ20 LwYAoPqY3kVpscCXS1HDJ8JQcSDEXDmS =pAtY -----END PGP SIGNATURE----- --Apple-Mail=_708D8047-CBEA-48C1-BAB2-B34E0AD72A98-- From owner-freebsd-toolchain@freebsd.org Fri Nov 20 22:23:04 2015 Return-Path: Delivered-To: freebsd-toolchain@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 59519A349C5 for ; Fri, 20 Nov 2015 22:23:04 +0000 (UTC) (envelope-from gerald@pfeifer.com) Received: from ainaz.pair.com (ainaz.pair.com [209.68.2.66]) (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 3B00B1C0A for ; Fri, 20 Nov 2015 22:23:03 +0000 (UTC) (envelope-from gerald@pfeifer.com) Received: from anthias.dhcp.nue.suse.com (charybdis-ext.suse.de [195.135.221.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ainaz.pair.com (Postfix) with ESMTPSA id 1802B3F462; Fri, 20 Nov 2015 17:22:55 -0500 (EST) Date: Fri, 20 Nov 2015 23:22:54 +0100 (CET) From: Gerald Pfeifer To: "William A. Mahaffey III" cc: freebsd-toolchain@freebsd.org Subject: Re: [toolchain] amd64-gcc question In-Reply-To: Message-ID: References: <56449EF8.7070806@hiwaay.net> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Nov 2015 22:23:04 -0000 On Sun, 15 Nov 2015, Gerald Pfeifer wrote: > I just committed changes to lang/gcc6-devel and lang/gcc5-devel to > add support for Graphite with a new option GRAPHITE. This is off > by default, but you can enable it, rebuild the port, and then have > what you've been looking for. lang/gcc5, which tracks upstream releases, now also has this. I am not planning to push this into older releases of GCC since Graphite support there is sufficiently different (and less mature). Gerald From owner-freebsd-toolchain@freebsd.org Fri Nov 20 22:56:18 2015 Return-Path: Delivered-To: freebsd-toolchain@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 8602FA330BF; Fri, 20 Nov 2015 22:56:18 +0000 (UTC) (envelope-from mmoll@darkthrone.kvedulv.de) Received: from darkthrone.kvedulv.de (darkthrone.kvedulv.de [IPv6:2001:1578:400:101::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "darkthrone.kvedulv.de", Issuer "StartCom Class 1 Primary Intermediate Server CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 481891066; Fri, 20 Nov 2015 22:56:18 +0000 (UTC) (envelope-from mmoll@darkthrone.kvedulv.de) Received: by darkthrone.kvedulv.de (Postfix, from userid 666) id E7356F23; Fri, 20 Nov 2015 23:56:15 +0100 (CET) Date: Fri, 20 Nov 2015 23:56:15 +0100 From: Michael Moll To: Dimitry Andric Cc: freebsd-arm@FreeBSD.org, freebsd-toolchain@FreeBSD.org Subject: Re: lang/ruby2* build failure on arm Message-ID: <20151120225615.GD48644@darkthrone.kvedulv.de> References: <20151120165446.GB48644@darkthrone.kvedulv.de> <963F064D-2B30-40E4-9F09-31C9121CE80A@FreeBSD.org> <20151120220210.GC48644@darkthrone.kvedulv.de> <903D1E22-D3E4-4DDA-BBF3-F8DDFAE91B56@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="ABTtc+pdwF7KHXCz" Content-Disposition: inline In-Reply-To: <903D1E22-D3E4-4DDA-BBF3-F8DDFAE91B56@FreeBSD.org> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Nov 2015 22:56:18 -0000 --ABTtc+pdwF7KHXCz Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Nov 20, 2015 at 11:18:09PM +0100, Dimitry Andric wrote: > As to why GNU configure tries to call this without arguments, is beyond > me. To work around its brokenness, I would set ac_cv_func__setjmp to > yes before calling configure. Or attempt to unbreak autoconf, but that > is a truly Herculean task. :-) Tested and committed as r402110, thank you very much! --=20 Michael Moll --ABTtc+pdwF7KHXCz Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCgAGBQJWT6UOAAoJEHSbfGivsRbHrGwP/36e6Yif0q47ImOWfWsrJxSD sWrtKfbQiAMRZgTg/nPQFjbOuUPTygx6VCIfJeOhu6Sk9GD+Vc95EwfmmcZa3efn Ye/9/0BwUnoOwOiKsAPaXxwCICV5OZZZOrgiikGjfis8Kf9OizAjL67UoNzmQHmi /iIqWvTedVugXIe9d/RWlvj0nr3ivUqs9oPYhwAaRUnkZ4lUWDyrq8YTTSGgJkSG j6C2IEvQDEJ35dUzW0Dx5LEUpuFxJNQAF9jy0zvgUl/x/2LEhKiC6oT/n5aZ6BRB s97LhnazycPZfIHftQ03uVqPS4mnj4hAJCRVzXuEPrqQ0NxTxvw0qGZqf1iCp4BI Kk0VXuQnYPMUfpmzUHc/Zrwn3pXwcjcHEUncI1UjAJVBtVs7HIFAuw5B+Z+Z/mEt saePETpbE1ebVgN7196FNSRKaQTiM9XrwjuRpO12j2sWHBvp/gx00PZZOoPix4NI YWRprMeC0Zc9XLFk5aB3t220tDpmf9ShxBDgOCX9Nbk2TOUhfPdFxX/vL3Ui4LuZ p6zvbLnR1xb48A1ujEKnj5nF7P5RPJ92pqpvMxhJ9G7SCx9ku0r1nyVsofrU/DH/ AzPT3uT67Hq6kgstD+SKiOZLZD4PcSfgH9rQu0EBpvfXtOwWk4smgPzA8bTP/lwe onzxdNmPw1XpQ27DI7Hv =J0bT -----END PGP SIGNATURE----- --ABTtc+pdwF7KHXCz-- From owner-freebsd-toolchain@freebsd.org Fri Nov 20 23:59:53 2015 Return-Path: Delivered-To: freebsd-toolchain@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 90A82A33F98 for ; Fri, 20 Nov 2015 23:59:53 +0000 (UTC) (envelope-from wam@hiwaay.net) Received: from fly.hiwaay.net (fly.hiwaay.net [216.180.54.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 47C571F91 for ; Fri, 20 Nov 2015 23:59:53 +0000 (UTC) (envelope-from wam@hiwaay.net) Received: from kabini1.local (dynamic-216-186-213-32.knology.net [216.186.213.32] (may be forged)) (authenticated bits=0) by fly.hiwaay.net (8.13.8/8.13.8/fly) with ESMTP id tAKNxiYb008764 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Fri, 20 Nov 2015 17:59:45 -0600 Subject: Re: [toolchain] amd64-gcc question References: <56449EF8.7070806@hiwaay.net> Cc: freebsd-toolchain@freebsd.org From: "William A. Mahaffey III" Message-ID: <564FB3F0.4060802@hiwaay.net> Date: Fri, 20 Nov 2015 18:05:14 -0553.75 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Nov 2015 23:59:53 -0000 On 11/20/15 16:29, Gerald Pfeifer wrote: > On Sun, 15 Nov 2015, Gerald Pfeifer wrote: >> I just committed changes to lang/gcc6-devel and lang/gcc5-devel to >> add support for Graphite with a new option GRAPHITE. This is off >> by default, but you can enable it, rebuild the port, and then have >> what you've been looking for. > lang/gcc5, which tracks upstream releases, now also has this. > > I am not planning to push this into older releases of GCC since > Graphite support there is sufficiently different (and less mature). > > Gerald Roger that, thanks :-). I am having other problems which I am taking up w/ GNU, so we'll see what happens. Thanks again. -- William A. Mahaffey III ---------------------------------------------------------------------- "The M1 Garand is without doubt the finest implement of war ever devised by man." -- Gen. George S. Patton Jr.