Aren/NetBSD
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
214b89d952
NetBSD/external/gpl3/gcc/README.gcc53

104 lines
3.2 KiB
Plaintext
Raw Normal View History

update a bunch: - explain the columns - update arm status: - MKCOMPAT problems with oabi - coldfire builds as much as GCC 4.8 - sun2, m68k builds - most mips builds now (mips64 has generic build issues) - update sparc64 and ppc problems (sshd) - there is something very very odd in linking libldap.so.4.3 where using the GCC 4.8 compiler to link the GCC 5.3 compiled objects works, or using GCC 5.3 compiler to link the 4.8 compiled objects fails -- ie, the compiler output seems fine, but the interactions between GCC and ld(1) are broken. - add or1k, riscv*, ia64 and ppc64 columns: - or1k and riscv* both fail, they need to have their support ported to GCC 5.x (i understand that at least one of them has a GCC 5.x tree.) - expand the list of actually tested to complete "build.sh release" to include machines, not just cpus.
2016-03-23 10:34:37 +03:00
$NetBSD: README.gcc53,v 1.8 2016/03/23 07:34:37 mrg Exp $
document the state of gcc 5.3 in src.
2016-03-18 00:46:08 +03:00
lib:
libasan is disabled currently (haven't tried yet)
new stuff:
cc1objcplus
collect2 -- need to re-introduce?
libcc1
libcilkrts
libmpx
liboffloadmic
libquadmath
libvtv
libitm
other changes to look at:
Index: gcc/targhooks.c
vs new binutils
+ doc/gcov-tool.1
arch/feature list. anything not here has been switched already:
update a bunch: - explain the columns - update arm status: - MKCOMPAT problems with oabi - coldfire builds as much as GCC 4.8 - sun2, m68k builds - most mips builds now (mips64 has generic build issues) - update sparc64 and ppc problems (sshd) - there is something very very odd in linking libldap.so.4.3 where using the GCC 4.8 compiler to link the GCC 5.3 compiled objects works, or using GCC 5.3 compiler to link the 4.8 compiled objects fails -- ie, the compiler output seems fine, but the interactions between GCC and ld(1) are broken. - add or1k, riscv*, ia64 and ppc64 columns: - or1k and riscv* both fail, they need to have their support ported to GCC 5.x (i understand that at least one of them has a GCC 5.x tree.) - expand the list of actually tested to complete "build.sh release" to include machines, not just cpus.
2016-03-23 10:34:37 +03:00
tools: does build.sh tools work?
kernels: does a kernel run?
libgcc: does libgcc build?
native-gcc: does a full mknative-gcc complete?
make release: does build.sh release complete?
runs: does the system boot with a full world?
atf: does atf run / compare well
document the state of gcc 5.3 in src.
2016-03-18 00:46:08 +03:00
architecture tools kernels libgcc native-gcc make release runs atf
------------ ----- ------- ------ ---------- ------------ ---- ---
updates to latest -current: - sshd problem is libldap.so.4.3, at least on sparc64. placing with 4.8 one works - alpha mostly works fine, 7 new failures in atf, plus sshd problem - update release build info for many *earm*, hppa, i386, amd64, mipsel, sh3* - *mips* now at least completes mknative-gcc - sh3eb has a mknative-gcc problem
2016-03-22 11:22:04 +03:00
alpha y y y y y y[6] y - 7 new failures out of ~4000
update a bunch: - explain the columns - update arm status: - MKCOMPAT problems with oabi - coldfire builds as much as GCC 4.8 - sun2, m68k builds - most mips builds now (mips64 has generic build issues) - update sparc64 and ppc problems (sshd) - there is something very very odd in linking libldap.so.4.3 where using the GCC 4.8 compiler to link the GCC 5.3 compiled objects works, or using GCC 5.3 compiler to link the 4.8 compiled objects fails -- ie, the compiler output seems fine, but the interactions between GCC and ld(1) are broken. - add or1k, riscv*, ia64 and ppc64 columns: - or1k and riscv* both fail, they need to have their support ported to GCC 5.x (i understand that at least one of them has a GCC 5.x tree.) - expand the list of actually tested to complete "build.sh release" to include machines, not just cpus.
2016-03-23 10:34:37 +03:00
arm y ? y y n[3]
armeb y ? y y n[3]
coldfire y N/A y y ? N/A N/A
earm y ? y y y[3,13]
earmeb y ? y y y[3,13]
earmhf y ? y y y[3]
earmhfeb y ? y y y[3]
updates to latest -current: - sshd problem is libldap.so.4.3, at least on sparc64. placing with 4.8 one works - alpha mostly works fine, 7 new failures in atf, plus sshd problem - update release build info for many *earm*, hppa, i386, amd64, mipsel, sh3* - *mips* now at least completes mknative-gcc - sh3eb has a mknative-gcc problem
2016-03-22 11:22:04 +03:00
earmv4 y y y y y[3] y
update a bunch: - explain the columns - update arm status: - MKCOMPAT problems with oabi - coldfire builds as much as GCC 4.8 - sun2, m68k builds - most mips builds now (mips64 has generic build issues) - update sparc64 and ppc problems (sshd) - there is something very very odd in linking libldap.so.4.3 where using the GCC 4.8 compiler to link the GCC 5.3 compiled objects works, or using GCC 5.3 compiler to link the 4.8 compiled objects fails -- ie, the compiler output seems fine, but the interactions between GCC and ld(1) are broken. - add or1k, riscv*, ia64 and ppc64 columns: - or1k and riscv* both fail, they need to have their support ported to GCC 5.x (i understand that at least one of them has a GCC 5.x tree.) - expand the list of actually tested to complete "build.sh release" to include machines, not just cpus.
2016-03-23 10:34:37 +03:00
earmv4eb y ? y y y[3]
updates to latest -current: - sshd problem is libldap.so.4.3, at least on sparc64. placing with 4.8 one works - alpha mostly works fine, 7 new failures in atf, plus sshd problem - update release build info for many *earm*, hppa, i386, amd64, mipsel, sh3* - *mips* now at least completes mknative-gcc - sh3eb has a mknative-gcc problem
2016-03-22 11:22:04 +03:00
earmv6 y ? y y y[3]
update a bunch: - explain the columns - update arm status: - MKCOMPAT problems with oabi - coldfire builds as much as GCC 4.8 - sun2, m68k builds - most mips builds now (mips64 has generic build issues) - update sparc64 and ppc problems (sshd) - there is something very very odd in linking libldap.so.4.3 where using the GCC 4.8 compiler to link the GCC 5.3 compiled objects works, or using GCC 5.3 compiler to link the 4.8 compiled objects fails -- ie, the compiler output seems fine, but the interactions between GCC and ld(1) are broken. - add or1k, riscv*, ia64 and ppc64 columns: - or1k and riscv* both fail, they need to have their support ported to GCC 5.x (i understand that at least one of them has a GCC 5.x tree.) - expand the list of actually tested to complete "build.sh release" to include machines, not just cpus.
2016-03-23 10:34:37 +03:00
earmv6eb y ? y y y[3]
earmv6hf y ? y y y[3]
earmv6hfeb y ? y y y[3]
updates to latest -current: - sshd problem is libldap.so.4.3, at least on sparc64. placing with 4.8 one works - alpha mostly works fine, 7 new failures in atf, plus sshd problem - update release build info for many *earm*, hppa, i386, amd64, mipsel, sh3* - *mips* now at least completes mknative-gcc - sh3eb has a mknative-gcc problem
2016-03-22 11:22:04 +03:00
earmv7 y ? y y y[3]
earmv7eb y ? y y y[3]
earmv7hf y ? y y y[3]
update a bunch: - explain the columns - update arm status: - MKCOMPAT problems with oabi - coldfire builds as much as GCC 4.8 - sun2, m68k builds - most mips builds now (mips64 has generic build issues) - update sparc64 and ppc problems (sshd) - there is something very very odd in linking libldap.so.4.3 where using the GCC 4.8 compiler to link the GCC 5.3 compiled objects works, or using GCC 5.3 compiler to link the 4.8 compiled objects fails -- ie, the compiler output seems fine, but the interactions between GCC and ld(1) are broken. - add or1k, riscv*, ia64 and ppc64 columns: - or1k and riscv* both fail, they need to have their support ported to GCC 5.x (i understand that at least one of them has a GCC 5.x tree.) - expand the list of actually tested to complete "build.sh release" to include machines, not just cpus.
2016-03-23 10:34:37 +03:00
earmv7hfeb y ? y y y[3]
updates to latest -current: - sshd problem is libldap.so.4.3, at least on sparc64. placing with 4.8 one works - alpha mostly works fine, 7 new failures in atf, plus sshd problem - update release build info for many *earm*, hppa, i386, amd64, mipsel, sh3* - *mips* now at least completes mknative-gcc - sh3eb has a mknative-gcc problem
2016-03-22 11:22:04 +03:00
hppa y ? y y y
i386 y y y y y y
update a bunch: - explain the columns - update arm status: - MKCOMPAT problems with oabi - coldfire builds as much as GCC 4.8 - sun2, m68k builds - most mips builds now (mips64 has generic build issues) - update sparc64 and ppc problems (sshd) - there is something very very odd in linking libldap.so.4.3 where using the GCC 4.8 compiler to link the GCC 5.3 compiled objects works, or using GCC 5.3 compiler to link the 4.8 compiled objects fails -- ie, the compiler output seems fine, but the interactions between GCC and ld(1) are broken. - add or1k, riscv*, ia64 and ppc64 columns: - or1k and riscv* both fail, they need to have their support ported to GCC 5.x (i understand that at least one of them has a GCC 5.x tree.) - expand the list of actually tested to complete "build.sh release" to include machines, not just cpus.
2016-03-23 10:34:37 +03:00
m68000 y ? y y y
m68k y ? y y y[13]
mipseb y ? y y y
updates to latest -current: - sshd problem is libldap.so.4.3, at least on sparc64. placing with 4.8 one works - alpha mostly works fine, 7 new failures in atf, plus sshd problem - update release build info for many *earm*, hppa, i386, amd64, mipsel, sh3* - *mips* now at least completes mknative-gcc - sh3eb has a mknative-gcc problem
2016-03-22 11:22:04 +03:00
mipsel y ? y y y
update a bunch: - explain the columns - update arm status: - MKCOMPAT problems with oabi - coldfire builds as much as GCC 4.8 - sun2, m68k builds - most mips builds now (mips64 has generic build issues) - update sparc64 and ppc problems (sshd) - there is something very very odd in linking libldap.so.4.3 where using the GCC 4.8 compiler to link the GCC 5.3 compiled objects works, or using GCC 5.3 compiler to link the 4.8 compiled objects fails -- ie, the compiler output seems fine, but the interactions between GCC and ld(1) are broken. - add or1k, riscv*, ia64 and ppc64 columns: - or1k and riscv* both fail, they need to have their support ported to GCC 5.x (i understand that at least one of them has a GCC 5.x tree.) - expand the list of actually tested to complete "build.sh release" to include machines, not just cpus.
2016-03-23 10:34:37 +03:00
mips64eb y ? n y n[8]
mips64el y ? n y n?
powerpc y y y y y[4] y[6]
updates to latest -current: - sshd problem is libldap.so.4.3, at least on sparc64. placing with 4.8 one works - alpha mostly works fine, 7 new failures in atf, plus sshd problem - update release build info for many *earm*, hppa, i386, amd64, mipsel, sh3* - *mips* now at least completes mknative-gcc - sh3eb has a mknative-gcc problem
2016-03-22 11:22:04 +03:00
sh3eb y ? y y y[5]
sh3el y ? y y y
sparc y y y y y y[1]
update a bunch: - explain the columns - update arm status: - MKCOMPAT problems with oabi - coldfire builds as much as GCC 4.8 - sun2, m68k builds - most mips builds now (mips64 has generic build issues) - update sparc64 and ppc problems (sshd) - there is something very very odd in linking libldap.so.4.3 where using the GCC 4.8 compiler to link the GCC 5.3 compiled objects works, or using GCC 5.3 compiler to link the 4.8 compiled objects fails -- ie, the compiler output seems fine, but the interactions between GCC and ld(1) are broken. - add or1k, riscv*, ia64 and ppc64 columns: - or1k and riscv* both fail, they need to have their support ported to GCC 5.x (i understand that at least one of them has a GCC 5.x tree.) - expand the list of actually tested to complete "build.sh release" to include machines, not just cpus.
2016-03-23 10:34:37 +03:00
sparc64 y y y y y n[6,2] y[9]
update info for: hppa: libc build failes in fenv.c m68*: libc fails with stack protector issues mips*: libgcc fails sh*: initial stuff works sparc*: sshd is broken for both, perhaps kernels are SMP problematic vax: tools/gcc failes
2016-03-18 13:14:39 +03:00
vax n[7]
updates to latest -current: - sshd problem is libldap.so.4.3, at least on sparc64. placing with 4.8 one works - alpha mostly works fine, 7 new failures in atf, plus sshd problem - update release build info for many *earm*, hppa, i386, amd64, mipsel, sh3* - *mips* now at least completes mknative-gcc - sh3eb has a mknative-gcc problem
2016-03-22 11:22:04 +03:00
x86_64 y y y y y y y
update a bunch: - explain the columns - update arm status: - MKCOMPAT problems with oabi - coldfire builds as much as GCC 4.8 - sun2, m68k builds - most mips builds now (mips64 has generic build issues) - update sparc64 and ppc problems (sshd) - there is something very very odd in linking libldap.so.4.3 where using the GCC 4.8 compiler to link the GCC 5.3 compiled objects works, or using GCC 5.3 compiler to link the 4.8 compiled objects fails -- ie, the compiler output seems fine, but the interactions between GCC and ld(1) are broken. - add or1k, riscv*, ia64 and ppc64 columns: - or1k and riscv* both fail, they need to have their support ported to GCC 5.x (i understand that at least one of them has a GCC 5.x tree.) - expand the list of actually tested to complete "build.sh release" to include machines, not just cpus.
2016-03-23 10:34:37 +03:00
--
or1k n[11]
riscv32 n[10]
riscv64 n[10]
ia64
powerpc64
updates to latest -current: - sshd problem is libldap.so.4.3, at least on sparc64. placing with 4.8 one works - alpha mostly works fine, 7 new failures in atf, plus sshd problem - update release build info for many *earm*, hppa, i386, amd64, mipsel, sh3* - *mips* now at least completes mknative-gcc - sh3eb has a mknative-gcc problem
2016-03-22 11:22:04 +03:00
------------ ----- ------- ------ ---------- ------------ ---- ---
architecture tools kernels libgcc native-gcc make release runs atf
document the state of gcc 5.3 in src.
2016-03-18 00:46:08 +03:00
[1] - world built without -fno-delete-null-pointer-checks does not have a
working sshd
[2] - -O2 and -Os kernels hang, -O1 SIR reset
update info for: hppa: libc build failes in fenv.c m68*: libc fails with stack protector issues mips*: libgcc fails sh*: initial stuff works sparc*: sshd is broken for both, perhaps kernels are SMP problematic vax: tools/gcc failes
2016-03-18 13:14:39 +03:00
-- may be a SMP issue; ultra10 works, ultra45 SMP does not
-- try sb2000 (particularly with UP kernel. u45 UP is shitty.)
update a bunch: - explain the columns - update arm status: - MKCOMPAT problems with oabi - coldfire builds as much as GCC 4.8 - sun2, m68k builds - most mips builds now (mips64 has generic build issues) - update sparc64 and ppc problems (sshd) - there is something very very odd in linking libldap.so.4.3 where using the GCC 4.8 compiler to link the GCC 5.3 compiled objects works, or using GCC 5.3 compiler to link the 4.8 compiled objects fails -- ie, the compiler output seems fine, but the interactions between GCC and ld(1) are broken. - add or1k, riscv*, ia64 and ppc64 columns: - or1k and riscv* both fail, they need to have their support ported to GCC 5.x (i understand that at least one of them has a GCC 5.x tree.) - expand the list of actually tested to complete "build.sh release" to include machines, not just cpus.
2016-03-23 10:34:37 +03:00
[3] - MKCOMPAT=no enabled currently, infact OABI seems to be broken. the docs say it was only deprecated, but the options make broken crap.
update info for alpha, powerpc, earmv4, i386, and sparc*
2016-03-18 10:30:47 +03:00
[4] - really, this is 'distribution sets' and a kernel
updates to latest -current: - sshd problem is libldap.so.4.3, at least on sparc64. placing with 4.8 one works - alpha mostly works fine, 7 new failures in atf, plus sshd problem - update release build info for many *earm*, hppa, i386, amd64, mipsel, sh3* - *mips* now at least completes mknative-gcc - sh3eb has a mknative-gcc problem
2016-03-22 11:22:04 +03:00
[5] - sh3eb tries to use sh specific atomic config which doesn't work, has hand edited mknative output
update alpha (mostly working) and hppa (mknative-gcc works)
2016-03-21 00:27:27 +03:00
[6] - sshd is broken, regardless of compiler options
updates to latest -current: - sshd problem is libldap.so.4.3, at least on sparc64. placing with 4.8 one works - alpha mostly works fine, 7 new failures in atf, plus sshd problem - update release build info for many *earm*, hppa, i386, amd64, mipsel, sh3* - *mips* now at least completes mknative-gcc - sh3eb has a mknative-gcc problem
2016-03-22 11:22:04 +03:00
-- libldap.so.4.3 is broken on sparc64; replacing just this fixes sshd.
update a bunch: - explain the columns - update arm status: - MKCOMPAT problems with oabi - coldfire builds as much as GCC 4.8 - sun2, m68k builds - most mips builds now (mips64 has generic build issues) - update sparc64 and ppc problems (sshd) - there is something very very odd in linking libldap.so.4.3 where using the GCC 4.8 compiler to link the GCC 5.3 compiled objects works, or using GCC 5.3 compiler to link the 4.8 compiled objects fails -- ie, the compiler output seems fine, but the interactions between GCC and ld(1) are broken. - add or1k, riscv*, ia64 and ppc64 columns: - or1k and riscv* both fail, they need to have their support ported to GCC 5.x (i understand that at least one of them has a GCC 5.x tree.) - expand the list of actually tested to complete "build.sh release" to include machines, not just cpus.
2016-03-23 10:34:37 +03:00
-- very very odd -- linking the GCC 5.3 created libldap *.pico flies with the GCC 4.8 compiler works
-- it is not binutils 2.23 vs 2.26
update info for: hppa: libc build failes in fenv.c m68*: libc fails with stack protector issues mips*: libgcc fails sh*: initial stuff works sparc*: sshd is broken for both, perhaps kernels are SMP problematic vax: tools/gcc failes
2016-03-18 13:14:39 +03:00
[7] - GCC fails to build
update a bunch: - explain the columns - update arm status: - MKCOMPAT problems with oabi - coldfire builds as much as GCC 4.8 - sun2, m68k builds - most mips builds now (mips64 has generic build issues) - update sparc64 and ppc problems (sshd) - there is something very very odd in linking libldap.so.4.3 where using the GCC 4.8 compiler to link the GCC 5.3 compiled objects works, or using GCC 5.3 compiler to link the 4.8 compiled objects fails -- ie, the compiler output seems fine, but the interactions between GCC and ld(1) are broken. - add or1k, riscv*, ia64 and ppc64 columns: - or1k and riscv* both fail, they need to have their support ported to GCC 5.x (i understand that at least one of them has a GCC 5.x tree.) - expand the list of actually tested to complete "build.sh release" to include machines, not just cpus.
2016-03-23 10:34:37 +03:00
[8] - sgimips64 release build fails, mdsetimage'd gz'd kernels don't get built?
note alpha mostly works (sshd problem as well) add that sparc64 test results are about 60 additional failures
2016-03-19 23:53:46 +03:00
[9] - with a 4.8 base.tgz and 5.3 everythingelse.tgz, about 60 additional failures out of ~3800
update a bunch: - explain the columns - update arm status: - MKCOMPAT problems with oabi - coldfire builds as much as GCC 4.8 - sun2, m68k builds - most mips builds now (mips64 has generic build issues) - update sparc64 and ppc problems (sshd) - there is something very very odd in linking libldap.so.4.3 where using the GCC 4.8 compiler to link the GCC 5.3 compiled objects works, or using GCC 5.3 compiler to link the 4.8 compiled objects fails -- ie, the compiler output seems fine, but the interactions between GCC and ld(1) are broken. - add or1k, riscv*, ia64 and ppc64 columns: - or1k and riscv* both fail, they need to have their support ported to GCC 5.x (i understand that at least one of them has a GCC 5.x tree.) - expand the list of actually tested to complete "build.sh release" to include machines, not just cpus.
2016-03-23 10:34:37 +03:00
[10] - fails to build tools with:
/usr/src8/tools/gcc/../../external/gpl3/gcc/dist/gcc/config/riscv/riscv.h:1087:9: error: attempt to use poisoned "MOVE_BY_PIECES_P"
#define MOVE_BY_PIECES_P(SIZE, ALIGN) \
[11] - diagnostic.c fails to bulid -- perhaps some bad merge?
/usr/src8/tools/gcc/../../external/gpl3/gcc/dist/gcc/cp/error.c:3384:40: warning: too many arguments for format [-Wformat-extra-args]
....
[13] - m68k builds tested: mvm68k amiga atari
- earm builds tested: shark evbarm*
Reference in New Issue Copy Permalink