Re: CVS commit: src/sys/arch/sun68k/stand
christos@ wrote:
Module Name: src
Committed By: christos
Date: Thu Nov 7 00:43:16 UTC 2013
Modified Files:
src/sys/arch/sun68k/stand: Makefile.inc
src/sys/arch/sun68k/stand/libsa: Makefile
Log Message:
avoid confusion with 68010 and 68020. The sun3 always was a 68020, and
the code assumes that.
-AFLAGS= -Wa,-mc68020 -Wa,-mc68851
-CFLAGS= -mc68000 -Wa,-mc68010 -Wa,-m68851 -msoft-float
+AFLAGS= -Wa,-m68020 -Wa,-m68851
+CFLAGS= -m68020 ${AFLAGS} -msoft-float
What problem are you trying to solve?
- sun68k/stand loaders are also used by 68010 sun2
- CFLAGS needs -mc68000 (or -m68000) for sun2 binaries
- AFLAGS needs -Wa,mc68020 because SRT0.S includes 020 %cacr instructions
inside sun3 conditinal blocks
---
Izumi Tsutsui
Re: CVS commit: src/sys/arch/sun68k/stand
On Nov 7, 9:41pm, tsut...@ceres.dti.ne.jp (Izumi Tsutsui) wrote: -- Subject: Re: CVS commit: src/sys/arch/sun68k/stand | What problem are you trying to solve? | | - sun68k/stand loaders are also used by 68010 sun2 | - CFLAGS needs -mc68000 (or -m68000) for sun2 binaries | - AFLAGS needs -Wa,mc68020 because SRT0.S includes 020 %cacr instructions |inside sun3 conditinal blocks That is what I thought but: It does not compile anymore with gcc-4.8.1, and i see -Dsun3 in the Makefiles The assembler complains about unsupported instructions for the jsr and the link.w instances. If you want, I can give you access to the gcc-4.8.1 repo so you can fix it yourself, just send me an ssh public key. christos
Re: CVS commit: src/sys/arch/sun68k/stand
On Thu, Nov 07, 2013 at 08:46:01AM -0500, Christos Zoulas wrote: It does not compile anymore with gcc-4.8.1, and i see -Dsun3 in the Makefiles The assembler complains about unsupported instructions for the jsr and the link.w instances. If you want, I can give you access to the gcc-4.8.1 repo so you can fix it yourself, just send me an ssh public key. Fwiw: I noticed that the sun2 tapeboot program is broken (again) - maybe this is related? If this can wait untill the weekend, I can look at 4.8.1 and sun2/sun3 userland (now that you fixed tme for me ;-}) Martin
Re: CVS commit: src/sys/arch/sun68k/stand
On Nov 7, 2:56pm, mar...@duskware.de (Martin Husemann) wrote: -- Subject: Re: CVS commit: src/sys/arch/sun68k/stand | On Thu, Nov 07, 2013 at 08:46:01AM -0500, Christos Zoulas wrote: | It does not compile anymore with gcc-4.8.1, and i see -Dsun3 in the Makefiles | The assembler complains about unsupported instructions for the jsr and the | link.w instances. If you want, I can give you access to the gcc-4.8.1 repo | so you can fix it yourself, just send me an ssh public key. | | Fwiw: I noticed that the sun2 tapeboot program is broken (again) - maybe | this is related? | | If this can wait untill the weekend, I can look at 4.8.1 and sun2/sun3 | userland (now that you fixed tme for me ;-}) Sounds good to me :-) I'll get the rest of the stuff compiling. christos
Re: CVS commit: src/sys/arch/sun68k/stand
christos@ wrote: It does not compile anymore with gcc-4.8.1, and i see -Dsun3 in the Makefiles The assembler complains about unsupported instructions for the jsr and the link.w instances. Well, then it's better to mention it in the log, not only avoid confusion. If you want, I can give you access to the gcc-4.8.1 repo so you can fix it yourself, just send me an ssh public key. Why isn't it in the public branch? --- Izumi Tsutsui
Re: CVS commit: src/usr.sbin/cpuctl/arch
On Nov 7, 6:18pm, SAITOH Masanobu wrote: } } Module Name: src } Committed By: msaitoh } Date: Thu Nov 7 18:18:59 UTC 2013 } } Modified Files: } src/usr.sbin/cpuctl/arch: i386.c } } Log Message: } Update some processor names. } } Modified files: } } Index: src/usr.sbin/cpuctl/arch/i386.c } diff -u src/usr.sbin/cpuctl/arch/i386.c:1.47 src/usr.sbin/cpuctl/arch/i386.c:1.48 } --- src/usr.sbin/cpuctl/arch/i386.c:1.47 Wed Oct 30 08:42:16 2013 } +++ src/usr.sbin/cpuctl/arch/i386.c Thu Nov 7 18:18:59 2013 } @@ -1,4 +1,4 @@ } -/* $NetBSD: i386.c,v 1.47 2013/10/30 08:42:16 mrg Exp $*/ } +/* $NetBSD: i386.c,v 1.48 2013/11/07 18:18:59 msaitoh Exp $*/ } } /*- } * Copyright (c) 1999, 2000, 2001, 2006, 2007, 2008 The NetBSD Foundation, Inc. } @@ -57,7 +57,7 @@ } } #include sys/cdefs.h } #ifndef lint } -__RCSID($NetBSD: i386.c,v 1.47 2013/10/30 08:42:16 mrg Exp $); } +__RCSID($NetBSD: i386.c,v 1.48 2013/11/07 18:18:59 msaitoh Exp $); } #endif /* not lint */ } } #include sys/types.h } @@ -342,18 +342,19 @@ const struct cpu_cpuid_nameclass i386_cp } [0x2a] = Xeon E3-12xx, 2nd gen i7, i5, }i3 2xxx, } [0x2c] = Xeon 36xx 56xx, i7, i5 and i3, } - [0x2d] = Xeon E5 Sandy bridy family, } + [0x2d] = Xeon E5 Sandy Bridy family, Shouldn't that be Sandy Bridge? } + Core i7-39xx Extreme, } [0x2e] = Xeon 75xx 65xx, } [0x2f] = Xeon E7 family, } [0x35] = Atom Family, } [0x36] = Atom S1000, } [0x37] = Atom C2000, E3000, } [0x3a] = Xeon E3-1200v2 and 3rd gen core, } - Ivy bridge, } + Ivy Bridge, } [0x3c] = 4th gen Core, Xeon E3-12xx v3 }(Haswell), } [0x3d] = Next gen Core, } - [0x3e] = Next gen Xeon E5/E7, Ivy bridge, } + [0x3e] = Xeon E5/E7, Ivy Bridge-EP, } [0x3f] = Future gen Xeon, } [0x45] = 4th gen Core, Xeon E3-12xx v3 }(Haswell), } }-- End of excerpt from SAITOH Masanobu
Re: CVS commit: src/usr.sbin/cpuctl/arch
(2013/11/08 3:45), John Nemeth wrote: On Nov 7, 6:18pm, SAITOH Masanobu wrote: } } Module Name:src } Committed By: msaitoh } Date: Thu Nov 7 18:18:59 UTC 2013 } } Modified Files: } src/usr.sbin/cpuctl/arch: i386.c } } Log Message: } Update some processor names. } } Modified files: } } Index: src/usr.sbin/cpuctl/arch/i386.c } diff -u src/usr.sbin/cpuctl/arch/i386.c:1.47 src/usr.sbin/cpuctl/arch/i386.c:1.48 } --- src/usr.sbin/cpuctl/arch/i386.c:1.47Wed Oct 30 08:42:16 2013 } +++ src/usr.sbin/cpuctl/arch/i386.c Thu Nov 7 18:18:59 2013 } @@ -1,4 +1,4 @@ } -/* $NetBSD: i386.c,v 1.47 2013/10/30 08:42:16 mrg Exp $*/ } +/* $NetBSD: i386.c,v 1.48 2013/11/07 18:18:59 msaitoh Exp $*/ } } /*- } * Copyright (c) 1999, 2000, 2001, 2006, 2007, 2008 The NetBSD Foundation, Inc. } @@ -57,7 +57,7 @@ } } #include sys/cdefs.h } #ifndef lint } -__RCSID($NetBSD: i386.c,v 1.47 2013/10/30 08:42:16 mrg Exp $); } +__RCSID($NetBSD: i386.c,v 1.48 2013/11/07 18:18:59 msaitoh Exp $); } #endif /* not lint */ } } #include sys/types.h } @@ -342,18 +342,19 @@ const struct cpu_cpuid_nameclass i386_cp } [0x2a] = Xeon E3-12xx, 2nd gen i7, i5, } i3 2xxx, } [0x2c] = Xeon 36xx 56xx, i7, i5 and i3, } - [0x2d] = Xeon E5 Sandy bridy family, } + [0x2d] = Xeon E5 Sandy Bridy family, Shouldn't that be Sandy Bridge? Fixed. Thanks! } +Core i7-39xx Extreme, } [0x2e] = Xeon 75xx 65xx, } [0x2f] = Xeon E7 family, } [0x35] = Atom Family, } [0x36] = Atom S1000, } [0x37] = Atom C2000, E3000, } [0x3a] = Xeon E3-1200v2 and 3rd gen core, } -Ivy bridge, } +Ivy Bridge, } [0x3c] = 4th gen Core, Xeon E3-12xx v3 } (Haswell), } [0x3d] = Next gen Core, } - [0x3e] = Next gen Xeon E5/E7, Ivy bridge, } + [0x3e] = Xeon E5/E7, Ivy Bridge-EP, } [0x3f] = Future gen Xeon, } [0x45] = 4th gen Core, Xeon E3-12xx v3 } (Haswell), } }-- End of excerpt from SAITOH Masanobu -- --- SAITOH Masanobu (msai...@execsw.org msai...@netbsd.org)
Re: CVS commit: src/sys/arch/sun68k/stand
On Nov 8, 3:07am, tsut...@ceres.dti.ne.jp (Izumi Tsutsui) wrote: -- Subject: Re: CVS commit: src/sys/arch/sun68k/stand | christos@ wrote: | | It does not compile anymore with gcc-4.8.1, and i see -Dsun3 in the Makefiles | The assembler complains about unsupported instructions for the jsr and the | link.w instances. | | Well, then it's better to mention it in the log, | not only avoid confusion. I can do that. | If you want, I can give you access to the gcc-4.8.1 repo | so you can fix it yourself, just send me an ssh public key. | | Why isn't it in the public branch? We did not want to burden the tree with throway code. We'll import it once it is done. christos
Re: CVS commit: src/sys/arch/sun68k/stand
christos@ wrote: | If you want, I can give you access to the gcc-4.8.1 repo | so you can fix it yourself, just send me an ssh public key. | | Why isn't it in the public branch? We did not want to burden the tree with throway code. We'll import it once it is done. IMO it's still better to have proper announcement in that case. (even developers don't know what's ongoing) --- Izumi Tsutsui
Re: CVS commit: src/sys/arch/sun68k/stand
On Nov 8, 6:01am, tsut...@ceres.dti.ne.jp (Izumi Tsutsui) wrote: -- Subject: Re: CVS commit: src/sys/arch/sun68k/stand | We did not want to burden the tree with throway code. We'll import it once | it is done. | | IMO it's still better to have proper announcement in that case. | (even developers don't know what's ongoing) Well, it is not really a secret that we want to upgrade gcc... The in-tree gcc is getting quite old and there are things it can't build anymore. But I guess we should have made it more public (that this is being worked on). The target version is 4.8.2, so far we've made some progress with 4.8.1 Whoever wants to help, I can give access to the repo. christos
Re: CVS commit: src/sys/arch/sun68k/stand
On Nov 8, 6:01am, Izumi Tsutsui wrote: } christos@ wrote: } } | If you want, I can give you access to the gcc-4.8.1 repo } | so you can fix it yourself, just send me an ssh public key. } | } | Why isn't it in the public branch? } } We did not want to burden the tree with throway code. We'll import it once } it is done. } } IMO it's still better to have proper announcement in that case. } (even developers don't know what's ongoing) We don't need announcments every time somebody starts working on a project. Many developers work on all sorts of projects all the time. Some pan out, some don't. When the developer has something to show, we will know, either by an announcement if it is something large, or by a commit if it is something small. }-- End of excerpt from Izumi Tsutsui
Re: CVS commit: src/sys/arch/sun68k/stand
jnemeth@ wrote: On Nov 8, 6:01am, Izumi Tsutsui wrote: } christos@ wrote: } } | If you want, I can give you access to the gcc-4.8.1 repo } | so you can fix it yourself, just send me an ssh public key. } | } | Why isn't it in the public branch? } } We did not want to burden the tree with throway code. We'll import it once } it is done. } } IMO it's still better to have proper announcement in that case. } (even developers don't know what's ongoing) We don't need announcments every time somebody starts working on a project. Many developers work on all sorts of projects all the time. Some pan out, some don't. When the developer has something to show, we will know, either by an announcement if it is something large, or by a commit if it is something small. You don't need announcement, but less announcements, less feedback. If you don't need help for your project, you are right. I pointed out a problematic fix, then a person working on the project without announcement answered you can fix it yourself. I don't know what's going on so less motivated. That's all. --- Izumi Tsutsui
