Re: Oddities with the new binutils
Repost of old mail now that I've made my ISP register their mail relays (which took three months for them to understand!). I know this is ancient but being in the archives may help someone. It was a kernel problem. I made a new kernel from sources of about 8 hours ago and the problem has dissappeared from my home machine (have to wait until after the long weekend [- in Oz] to test the work machine). It seems that something in the May 29th kernel was causing problems for X. Matthew Thyer wrote: It may not be FP itself. In fact I have seen some other strange graphic corruption at home when running xplanet in the background and xanim. When the planet turns, the top 20 or so rows of the root window get corrupted with some of the image of the currently playing animation in xanim. I haven't mentioned this yet because I've only been running xplanet since post-binutils so I cant compare it with previous behaviour. It would appear to be an Xserver problem. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Oddities with the new binutils
In [EMAIL PROTECTED], Martin Cracauer wrote: In [EMAIL PROTECTED], David O'Brien wrote: On Fri, Jun 02, 2000 at 04:42:29PM +0930, Matthew Thyer wrote: Three issues: - floating point math doesn't seem to work properly: I don't have a -current machine I want to delete all ports from, but I have a -current from yesterday, I compiled xaos on it and libpng, which is the only dependency of xaos. That leave XFree as the only non-recompiled thing in the chain. Works fine. OK, now I am pissed. I also recompiled and restarted X11 to trace this down, only to find that some stupid error in Xwrapper breaks xinit and I had to roll my own xinit. Anyway, now I am running everything in the pipe compiled within the last 24 hours on a fresh -current and xaos work just fine. It could also be poorly written ASM code in the things you were running. The old Binutils let people write inconsistent and illegal ASM. xoas and png themself do not have assembler files. Xfree servers have some, but not in floating point related things. Where is the information that this is a floating-point problem from? Matthew, do you possibly use a custom gcc from /usr/local/bin and the native assembler or vice versa? Also, what level of optimization do you use? Martin -- % Martin Cracauer [EMAIL PROTECTED] http://www.cons.org/cracauer/ BSD User Group Hamburg, Germany http://www.bsdhh.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Oddities with the new binutils
"-O -pipe" is all I use for kernel and world builds. The kernel config file from my work box is attached. I have never built gcc from ports. I always use "config -r" when building kernels. I dont use modules as I have everything I need in my kernel including COMPAT_LINUX. And as I said before I removed all ports so that my testing is with XFree86, xaos and any supporting libraries all compiled after my world and kernel build. Did you do something similar ? I am using XFree86 3.3.6 on both machines. If it comes down to particular video cards, My work machine has: VESA: v1.2, 2048k memory, flags:0x0, mode table:0xc00c09da (c9da) VESA: S3 Incorporated. Trio64V+ My home machine has a "3dfx Velocity 100 AGP with 8MB SGRAM" which is detected as a Voodoo 3 by the VESA code. Martin Cracauer wrote: In [EMAIL PROTECTED], Martin Cracauer wrote: In [EMAIL PROTECTED], David O'Brien wrote: On Fri, Jun 02, 2000 at 04:42:29PM +0930, Matthew Thyer wrote: Three issues: - floating point math doesn't seem to work properly: I don't have a -current machine I want to delete all ports from, but I have a -current from yesterday, I compiled xaos on it and libpng, which is the only dependency of xaos. That leave XFree as the only non-recompiled thing in the chain. Works fine. OK, now I am pissed. I also recompiled and restarted X11 to trace this down, only to find that some stupid error in Xwrapper breaks xinit and I had to roll my own xinit. Anyway, now I am running everything in the pipe compiled within the last 24 hours on a fresh -current and xaos work just fine. It could also be poorly written ASM code in the things you were running. The old Binutils let people write inconsistent and illegal ASM. xoas and png themself do not have assembler files. Xfree servers have some, but not in floating point related things. Where is the information that this is a floating-point problem from? Matthew, do you possibly use a custom gcc from /usr/local/bin and the native assembler or vice versa? Also, what level of optimization do you use? Martin -- % Martin Cracauer [EMAIL PROTECTED] http://www.cons.org/cracauer/ BSD User Group Hamburg, Germany http://www.bsdhh.org/ -- Matthew Thyer Phone: +61 8 8259 7249 Corporate Information Systems Fax:+61 8 8259 5537 Defence Science and Technology Organisation, Salisbury PO Box 1500 Salisbury South Australia 5108 # $FreeBSD: FUZZ,v 5.5 2000/05/30 10:59:00 +09:30 thyerm Exp $ # based on $FreeBSD: src/sys/i386/conf/LINT,v 1.775 2000/05/22 15:00:40 dan Exp $ machine i386 ident "FUZZ" maxusers64 options INCLUDE_CONFIG_FILE # Include this file in kernel cpu I686_CPU options CPU_FASTER_5X86_FPU options NO_F00F_HACK # COMPATIBILITY OPTIONS options COMPAT_43 # Compatible with BSD 4.3 [KEEP THIS!] options USER_LDT# Let processes manipulate their local descriptor table (needed for WINE) options SYSVSHM # Enable SYSV style shared memory options SYSVSEM # Enable SYSV style semaphores options SYSVMSG # Enable SYSV style message queues options SHM_PHYS_BACKED options SHMALL=16384 options SHMMAXPGS=4096 options SHMMAX="(SHMMAXPGS*PAGE_SIZE+1)" options SHMSEG=50 options SHMMNI=64 options SEMMNI=32 options SEMMNS=128 # DEBUGGING OPTIONS #optionsDDB # Enable the kernel debugger options KTRACE # kernel tracing (SVR4 emul needs this) options UCONSOLE# Allow users to grab the console options USERCONFIG # boot -c editor options VISUAL_USERCONFIG # visual boot -c editor # NETWORKING OPTIONS options INET# Internet communications protocols # Network interfaces: pseudo-device ether # Generic Ethernet pseudo-device loop# Network loopback device #pseudo-device tun # Tunnel driver (user ppp requirement) # FILESYSTEM OPTIONS options FFS # Berkeley Fast Filesystem options FFS_ROOT# FFS usable as root device options NFS # Network Filesystem options MFS # Memory Filesystem options CD9660 # ISO 9660 Filesystem options PROCFS # Process Filesystem options MSDOSFS # MSDOS Filesystem options NSWAPDEV=4 # Allow this many swap-devices options SOFTUPDATES # Allow FFS to use Softupdates tech options NCP # NetWare Core protocol
Re: Oddities with the new binutils
David, I emailed my details on what I have done on two machines that are exhibiting this problem. Because these machines are different in their hardware and have not expressed the problem in the past, I dont think its a hardware issue. Before the new binutils both machines did not have this problem. I dont know if it is the binutils change that has caused this problem as I do not have the time to exhaustively test. My email was to try to get others to reproduce the problem hence I gave details on what I did. So, has anyone done the procedure I have and seen or not seen the problem where xaos version 3.0 draws garbage when renderring. (run xaos and press the 'a' key). I haven't given kernel config files or hardware details because I dont think its relevant until someone can say "I have done the steps you have outlined and I dont see you problem". I do not have time to debug this myself (I would also need to learn a few things) however, I have been running -CURRENT for more than 5 years and know that I have upgraded my software correctly and am fairly convinced that hardware is not an issue so I am reporting this problem to see if others can reproduce it as a service to the FreeBSD community (I wont even charge for it!). I also do not intend to report this to the binutils maintainers because it may be a FreeBSD issue, not a binutils issue. David O'Brien wrote: On Mon, Jun 05, 2000 at 10:24:24AM +0930, Matthew Thyer wrote: Has anyone tried the specific instructions I gave to reproduce the problem ? These instructions do things at too high a level. i.e.: - make world - making and installing a new kernel - mergemaster - reboot All fine. - deletion of ALL installed ports - recompile of every essential port (inc XFree 3.3.6) This doesn't give me anything to debug. I need to know a specific source file. Sending this bug report plus instructions to reproduce to the Binutils maintainers will get no where. -- -- David ([EMAIL PROTECTED]) -- Matthew Thyer Phone: +61 8 8259 7249 Corporate Information Systems Fax:+61 8 8259 5537 Defence Science and Technology Organisation, Salisbury PO Box 1500 Salisbury South Australia 5108 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Oddities with the new binutils
On Fri, Jun 02, 2000 at 04:42:29PM +0930, Matthew Thyer wrote: Three issues: - floating point math doesn't seem to work properly: - backward compatibility: - stability: Are others seeing these issues? These issues make me think that the new binutils is not yet ready for -STABLE. It could also be poorly written ASM code in the things you were running. The old Binutils let people write inconsistent and illegal ASM. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Oddities with the new binutils
Has anyone tried the specific instructions I gave to reproduce the problem ? i.e.: - make world - making and installing a new kernel - mergemaster - reboot - deletion of ALL installed ports - recompile of every essential port (inc XFree 3.3.6) Then: Build xaos from ports (/usr/ports/graphics/xaos) Run xaos and press 'a' David O'Brien wrote: On Fri, Jun 02, 2000 at 04:42:29PM +0930, Matthew Thyer wrote: Three issues: - floating point math doesn't seem to work properly: - backward compatibility: - stability: Are others seeing these issues? These issues make me think that the new binutils is not yet ready for -STABLE. It could also be poorly written ASM code in the things you were running. The old Binutils let people write inconsistent and illegal ASM. -- -- David ([EMAIL PROTECTED]) -- Matthew Thyer Phone: +61 8 8259 7249 Corporate Information Systems Fax:+61 8 8259 5537 Defence Science and Technology Organisation, Salisbury PO Box 1500 Salisbury South Australia 5108 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Oddities with the new binutils
On Mon, Jun 05, 2000 at 10:24:24AM +0930, Matthew Thyer wrote: Has anyone tried the specific instructions I gave to reproduce the problem ? These instructions do things at too high a level. i.e.: - make world - making and installing a new kernel - mergemaster - reboot All fine. - deletion of ALL installed ports - recompile of every essential port (inc XFree 3.3.6) This doesn't give me anything to debug. I need to know a specific source file. Sending this bug report plus instructions to reproduce to the Binutils maintainers will get no where. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Oddities with the new binutils
Three issues: - floating point math doesn't seem to work properly: To reproduce: Build xaos from ports (/usr/ports/graphics/xaos) Run xaos and press 'a' - enjoy the show but I dont think its what the author intended. I have reproduced this on two machines which are running -CURRENT as of around May 29th - 30th with the new binutils. Both machines were upgraded by: - make world - making and installing a new kernel - mergemaster - reboot - deletion of ALL installed ports - recompile of every essential port (inc XFree 3.3.6) One machine has its source populated by cvsup from cvsup4, the other by cvsup from my own cvsup server whos repository is populated by ctm-cvs-cur delta so I dont think there are any problems with my source tree. - backward compatibility: Before I deleted all ported software on my home machine (cvsup's from cvsup4) I ran wdm and Window maker and saw lots of problems with font rendering into wrong locations, menus not being displayed properly and icons being placed in incorrect locations (not actually icons but the launching thingies!). I'm not complaining but rather reporting so that people can bump appropriate FreeBSD version numbers..., update UPDATING etc if required or if there are not meant to be any issues then work out why there are. - stability: Windowmaker at home dumps core whenever I log out (it never used to do this before the new binutils with the exact same version of Windowmaker). I haven't noticed other stability problems yet. These issues make me think that the new binutils is not yet ready for -STABLE. -- Matthew Thyer Phone: +61 8 8259 7249 Corporate Information Systems Fax:+61 8 8259 5537 Defence Science and Technology Organisation, Salisbury PO Box 1500 Salisbury South Australia 5108 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
