Re: Use of C99 extra long double math functions after r236148

On Fri, Jul 13, 2012, Warner Losh wrote: > Just to jump back into the fray a bit, since this point hasn't been > articulated well. > > On Jul 10, 2012, at 6:55 PM, Peter Jeremy wrote: > > > On 2012-Jul-08 19:01:07 -0700, Steve Kargl > > wrote: > >> Well, on the most popular hardware (that bein

Re: Use of C99 extra long double math functions after r236148

On Fri, Jul 13, 2012, David Chisnall wrote: > As do I. I'd also point out that the ONLY requirement for long > double according to the standard is that it has at least the same > precision as double. Therefore, any implementation of these > functions that is no worse that the double version is co

Re: Use of C99 extra long double math functions after r236148

On Tue, Jul 10, 2012, Rainer Hurling wrote: > On 10.07.2012 17:11 (UTC+2), David Schultz wrote: > >On Tue, Jul 10, 2012, Rainer Hurling wrote: > >>On 10.07.2012 16:02 (UTC+2), Warner Losh wrote: > >>> > >>>On Jul 10, 2012, at 3:10 AM, Rainer Hurlin

Re: Use of C99 extra long double math functions after r236148

On Tue, Jul 10, 2012, Rainer Hurling wrote: > On 10.07.2012 16:02 (UTC+2), Warner Losh wrote: > > > >On Jul 10, 2012, at 3:10 AM, Rainer Hurling wrote: > >>As far as I understand from discussions on R mailing list > >>(r-de...@r-project.org), they plan to reduce the emulation and/or > >>workaroun

Re: Use of C99 extra long double math functions after r236148

On Sun, Jul 08, 2012, Steve Kargl wrote: > > > The question remains of what to do about the missing functions. Bruce > > > and Steve have been working on expl and logl for years. If those ever > > > get in the tree, the remaining long double functions are easy. Those > > > functions are basicall

Re: Use of C99 extra long double math functions after r236148

On Tue, May 29, 2012, Peter Jeremy wrote: > On 2012-May-28 15:54:06 -0700, Steve Kargl > wrote: > >Given that cephes was written years before C99 was even > >conceived, I suspect all functions are sub-standard. > > Well, most of cephes was written before C99. The C99 parts of > cephes were writ

Re: r227487 breaks C++ programs that use __isthreaded

On Thu, Dec 01, 2011, George Liaskos wrote: > Hello > > One example is Google's tcmalloc [1], is this behaviour intended? > > [1] > http://code.google.com/p/google-perftools/source/browse/trunk/src/maybe_threads.cc This code uses an unportable workaround for a bug that I believe was fixed in r2

Re: Is fork() hook ever possible?

On Tue, Nov 15, 2011, Andrey Chernov wrote: > In case you mean passing later whole structure like: > > arc4_addrandom((u_char *)&rdat, sizeof(rdat)); > > it will be incorrect because it change known algorithm parameters, which > defines exact 128 bytes and not anything else. No, RC4 keys are an

Re: Is fork() hook ever possible?

On Tue, Nov 15, 2011, Andrey Chernov wrote: > On Mon, Nov 14, 2011 at 03:58:55PM -0500, David Schultz wrote: > > On Mon, Nov 14, 2011, Andrey Chernov wrote: > > > 1) We should use > > > mib[0] = CTL_KERN; > > > mib[1] = KERN_ARND; > > > > >

Re: Is fork() hook ever possible?

On Mon, Nov 14, 2011, Andrey Chernov wrote: > 1) We should use > mib[0] = CTL_KERN; > mib[1] = KERN_ARND; > > len = sizeof(rnd); > sysctl(mib, 2, rnd, &len, NULL, 0); > here instead of /dev/random, like OpenBSD did. It helps jails, and > re-stearing not happens too often

Re: Is fork() hook ever possible?

On Sat, Nov 12, 2011, Andrey Chernov wrote: > On Sat, Nov 12, 2011 at 10:41:35AM -0500, David Schultz wrote: > > On Sat, Nov 12, 2011, Andrey Chernov wrote: > > > On Tue, Sep 16, 2008 at 04:19:32PM -0400, David Schultz wrote: > > > > secteam@ already agreed to the id

Re: Is fork() hook ever possible?

On Sat, Nov 12, 2011, Andrey Chernov wrote: > On Tue, Sep 16, 2008 at 04:19:32PM -0400, David Schultz wrote: > > secteam@ already agreed to the idea of solving the fork problem as > > in OpenBSD over a month ago. > > On Wed, Sep 17, 2008 at 12:50:25PM +0400, Andrey Chern

Re: Clang buildworld failure due to multiple definitions of __isnanf

On Sun, Jun 26, 2011, Eric McCorkle wrote: > I've both seen reports and experienced make buildworld with clang > failing in usr.bin/xlint/lint1 (really, make kernel-toolchain is what > fails), because lint1 is statically linked, and there is a definition of > __isnanf in both libc and libm. GCC

Re: warning: 'inline' is not at beginning of declaration ?

On Thu, Jun 02, 2011, Arnaud Lacombe wrote: > > On a related topic, do we have any mechanism to provide > > per-subdir or per-file CFLAGS during kernel builds ? > > > I'd say no as the kernel per-se makes no use of , ooth, > some modules do. > > > I tried to put a Makefile.inc in a subdirectory bu

Re: CFT: msk(4) 64bit DMA support

85;95;0cOn Thu, May 26, 2011, YongHyeon PYUN wrote: > Here is a patch that implements 64bit DMA on msk(4). If you use > msk(4) on a system that has more than 4GB memory, please try the > patch at the following URL and let me know whether it works or not. > You need latest msk(4) in HEAD to apply th

Re: Removal of ICC (intel compiler) bits from mk

On Wed, Aug 18, 2010, Rui Paulo wrote: > Hi, > I've been chatting with the ICC ex-users and they seem to be ok with the > removal of the ICC bits from share/mk and other places. > The reason is that it doesn't work and no one has volunteered to fix it for > many years. This seems to indicate tha

Re: [TESTING] ssse3 backport from gcc 4.3

On Wed, Mar 09, 2011, Martin Matuska wrote: > I have prepared a patch that finishes the "core2" support part and > backports from gcc-4.3 > the SSSE3 instruction set (-mssse3, -mno-ssse3). > It is enabled for -march=core2 by default. > > Testing and comments are welcome. > > Patch: > http://peopl

Re: ieee denormal on ia64?

On Fri, Feb 25, 2011, Anton Shterenlikht wrote: > Can somebody please confirm that denormal > are not available on ia64, see below. [...] > The FreeBSD manpage for fpsetmask() at http://tinyurl.com/64oo7zh says: > > > #define FP_X_DNML 0x02/* denormal */ The FreeBSD manpage for

Re: Port of Niels Provos's file descriptor allocation code

On Thu, Nov 27, 2003, Tim Robbins wrote: > I've ported Niels Provos's file descriptor allocation code to FreeBSD > in case anyone wants to try it out & run some benchmarks. If the performance > boost turns out to be worth the added complexity, I might clean it up a > bit and commit it. I've used a

Re: Unfortunate dynamic linking for everything

On Tue, Nov 18, 2003, Robert Watson wrote: > On systems like Mac OS X, use of a "shared > region" permits not only use of prebinding, but assumptions of common load > addresses for common libraries. In addition, the "shared region" approach > allows the reuse of page table and VM meta-data across

Re: Unfortunate dynamic linking for everything

On Tue, Nov 18, 2003, Scott Long wrote: > > The additional hole of exploiting the system through the shared libs > > is a negative tradeoff. > > Exploits in libraries happen though. The LD_LIBRARY_PATH attack is an old > one that most Unixes are hopefully hardened against. FreeBSD had a lingerin

Re: Unfortunate dynamic linking for everything

On Tue, Nov 18, 2003, Robert Watson wrote: > (2) Shells again, because they will be fork()d and exec()d frequently > during heavily scripted activities, such as system boot, periodic > events, large make jobs, etc. And presumably the only shell of > interest is sh, although some of the

Re: __fpclassifyd problem

On Fri, Oct 31, 2003, John Angelmo wrote: > But still after importing e_scalb.c or e_scalbf.c and rebuilding gives > me this: > > > cc -fpic -DPIC -O -pipe -march=pentium3 -D_IEEE_LIBM > -D_ARCH_INDIRECT=i387_ -c i387_s_tan.S -o i387_s_tan.So > building shared library libm.so.2 > e_scalb.So:

Re: __fpclassifyd problem

I'm just catching up on -CURRENT, but I wanted to point out that this was fixed last night in: src/lib/msun/src/e_scalbf.c,v1.8 src/lib/msun/src/e_scalb.c,v1.10 The fix was to use the old versions of isnan() and isinf() specifically in the two places in libm where they are needed.

Re: ata_dmasetup: transfer active on this device!

On Mon, Oct 27, 2003, Robert Watson wrote: > > Bumped into this panic on a kernel from Oct 4 running on my notebook. > Unfortunately, I don't have a good trace because I didn't have access to a > serial console, or a debugging kernel :-(. It might well already be > fixed, but I figured I'd post

Re: vm_map.c LOR

On Sat, Sep 27, 2003, Florian C. Smeets wrote: > Hey guys, > > got this one with today's current: > > lock order reversal > 1st 0xc28008ac vm object (vm object) @ /space/src/sys/vm/vm_map.c:2195 > 2nd 0xc082f110 system map (system map) @ /space/src/sys/vm/vm_kern.c:328 > Stack backtrace: > back

ATAng panic: ata_dmasetup: transfer active on this device!

I have a machine that panics reliably within ten minutes of operation with ATAng. It subsequently locks up, so I can't obtain a dump, and I get a small amount of random filesystem corruption upon rebooting. Everything was fine with ATAog. I don't have a serial cable handy at the moment, but the

Re: __fpclassifyd

On Fri, Aug 29, 2003, Christoph Kukulies wrote: > > I did a cvsup and rebuild of world and ports, portupgrade, > reinstalled mod_php4, apache and still get this > sh apache.sh start > Syntax error on line 237 of /usr/local/etc/apache/httpd.conf: > Cannot load /usr/local/libexec/apache/libphp4.so i

Re: 64 bit quantities in statfs ?

On Mon, Aug 25, 2003, Garrett Wollman wrote: > < said: > > > Yep, looks broken. In the POSIX standard, the functionality of > > statfs() is provided by statvfs(), so implementing the latter may > > be a way out that doesn't involve breaking any ABIs. > > statfs() is a lot more useful interface t

Re: 64 bit quantities in statfs ?

On Mon, Aug 18, 2003, Matthew Dillon wrote: > As part of the DragonFly effort we are going to increase the > mount path limit from 80 chars to 1024. > > This will change the statfs structure. I thought I would adopt the > 64 bit changes that 5.x has made to keep things synchroniz

Re: warnpassword and warnexpire in 5.1 login.conf

On Tue, Aug 05, 2003, Mats Larsson wrote: > Sure, run cap_mkdb on every edit on login.conf > > The values im trying to use there are the following: > :warnexpire=28d:\ > :warnpassword=14d:\ > > And with pw i use the following to test with: (also with -e option) > pw usermod user -

Re: warnpassword and warnexpire in 5.1 login.conf

On Sat, Aug 02, 2003, Mats Larsson wrote: > > Hello! > > Tried this question to the questions list with no response, perhaps > current is the correct list for questions related to 5.1-RELEASE?? > > I am trying to use warnexpire and warnpassword in login.conf but with no > result, are the warnexp

Re: vfprintf() has a 4096-byte memory leak?

On Sat, Aug 02, 2003, Ryan T. Dean wrote: > "Poul-Henning Kamp" wrote: > >In message <3F2B9C59.3060209 at cytherianage.net > >>, "Ryan T. > >Dean" writes: > >>/Hey all- > /> >/I was doing some app debugging tonight, and noticed what a

Re: maildir with softupdates

On Wed, Jul 23, 2003, Attila Nagy wrote: > Hello, > > Is this statement still valid? > > "ext3 is unsafe for maildir, and with softupdates, so is ffs." > http://www.irbs.net/internet/postfix/0202/0358.html The statement is FUD; this is a topic that mailer people love to complain about. It's onl

Re: possible unionfs bug

On Sun, Jul 20, 2003, Divacky Roman wrote: > Hi, > > I might be wrong but this: > > free(mp->mnt_data, M_UNIONFSMNT); /* XXX */ > mp->mnt_data = 0; > > seems to me wrong and might cause crashes etc. > am I correct or wrong? > > its from union_vfsops.c:384 What's w

Re: [-CURRENT tinderbox] failure on sparc64/sparc64

On Thu, Jul 17, 2003, Dag-Erling Smorgrav wrote: > On Thu, Jul 17, 2003 at 09:58:10AM +0200, Harti Brandt wrote: > > I have no idea how a program can core in vfork(). Probably a vm problem? > > Most likely a KSE-related problem in vfork(). Try replacing vfork() with > fork() in make(1) and see if

Re: SMP page update

On Tue, Jul 15, 2003, Alp ATICI wrote: > I was wondering whether the SMPng page at http://www.freebsd.org/smp is > updated as those features are added. Because it seems like no feature > update for long. > > For instance is the preemptible kernel going to be a part of 5.x series or > going > to

Re: HEADS UP: new KSE signal code

On Sat, Jun 28, 2003, David Leimbach wrote: > Because we aren't working on anything and need something to do... so we > find > ways to think about how we can enforce quality without understanding > how stuff > works first maybe? Umm...no, but thanks for the insult. How about: Because we are wor

Re: HEADS UP: new KSE signal code

On Sat, Jun 28, 2003, Julian Elischer wrote: > he means that between the time the commits start and finish there may be > an inconsistant period.. Why is everyone so eager to jump down everyone > else's throat these days? The statement that ``libkse will be broken for a while'' gave me the impress

Re: HEADS UP: new KSE signal code

On Sat, Jun 28, 2003, David Xu wrote: > I begin to commit KSE signal code, libkse will > be broken for a while. Umm...if it's known to be broken, then why did you commit it? If you want people to test KSE and report bugs, the version in the tree needs to be of consistently good quality. __

Re: Hyperthreading

On Fri, Jun 27, 2003, Brooks Davis wrote: > On Fri, Jun 27, 2003 at 06:39:12PM -0500, Glenn Johnson wrote: > > Thanks. I had read the smp manual page. I know _how_ to enable HTT; I > > was wondering whether I _should_ enable it. It seems the answer is that > > it is not beneficial in its current

Re: questions about VM_KMEM_SIZE_SCALE

On Tue, Jun 24, 2003, Jay Kuri wrote: > > Hi there, > > Can anyone shed some light on the implications of adjusting > VM_KMEM_SIZE_SCALE? In particular I'm wondering if I increase this to, > say, 2, what happens? I must admit I don't know how KVA is different from > KVM or total RAM... so the n

Re: write access to dos partition hangs system completely

On Sun, Jun 15, 2003, Andreas Klemm wrote: > FreeBSD titan.klemm.apsfilter.org 5.1-RC FreeBSD 5.1-RC #0: Sun Jun 1 14:21:32 CEST > 2003 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/TITAN5 i386 > > When I mount my dos partition read write and copy > some data to it it immediately freezes the

Re: Problems tuning kmem_map on 5.1-REL box.

On Thu, Jun 19, 2003, Peter Losher wrote: > On Wed, 18 Jun 2003, David Schultz wrote: > > > To allow the kmem_map to exceed 200 MB, you'll also need to tweak > > VM_KMEM_SIZE_MAX to (for example) '(1024 * 1024 * 1024)'. BTW, > > the formula, which I st

Re: Problems tuning kmem_map on 5.1-REL box.

On Tue, Jun 17, 2003, Peter Losher wrote: > Hi - > > If this sort of question is better asked on a more specialized list > @freebsd.org, please let me know. (Since 5.1 is still considered a > developmental release, one doesn't know if either -current or -stable > would be more appropriate. So I a

Re: CSTD=c99 breaks package creation

On Thu, Jun 12, 2003, Tim Robbins wrote: > On Wed, Jun 11, 2003 at 07:37:01PM -0700, Kris Kennaway wrote: > > > It's possible that there's either a bug in gcc or there is C code in > > the system that has a different meaning when interpreted to C99 > > standards. > > I think I may have found the

Re: MIDI

Thus spake Thanjee Neefam <[EMAIL PROTECTED]>: > I was very happy when compiling my 5.0 kernel. For the first time "device > midi" compiled without giving any errors. This abnormal excitement only > led to misery when I discovered after rebooting that there still was no > MIDI. > Is MIDI going to

Re: [Re: several background fsck panics

Thus spake Terry Lambert <[EMAIL PROTECTED]>: > o Put a counter in the first superblock; it would be > incremented when the BG fsck is started, and reset > to zero when it completes. If the counter reaches > 3 (or some command line specified number), then the > BG flagg

Re: several background fsck panics

Thus spake Alexander Langer <[EMAIL PROTECTED]>: > I had several panics related to background fsck now. Once I disabled > background fsck, all went ok. > > It began when I pressed the reset buttons on several boots while the > system was still doing fscks. [...] > Mar 24 21:48:59 fump kernel: pan

Re: Unclean sync in current

Thus spake Kevin Oberman <[EMAIL PROTECTED]>: > I've been seeing this for a couple of weeks since I updated my laptop to > CURRENT. I do a normal shutdown (-p or -r) and reboot. The shutdown > looked normal, with no problems reported with the sync, but, when the > system is rebooted, the partitions

Re: "Just" building the lib part of world

Thus spake David Leimbach <[EMAIL PROTECTED]>: > Or even better would be just building libc. I have been working on my > getpwnam_r assignment... > examining implementations in both Darwin and NetBSD and started trying > to implement some of > this code for FreeBSD... Its not anywhere even near

Re: libm problem

Thus spake Anti <[EMAIL PROTECTED]>: > On Sat, 22 Mar 2003 10:28:46 -0800 > Steve Kargl <[EMAIL PROTECTED]> wrote: > > > Pentium 4 is definitely broken on 5.x. Perhaps, we should remove > > the footshooting. > > > > --- bsd.cpu.mk.orig Sat Mar 22 10:23:42 2003 > > +++ bsd.cpu.mk Sat Mar 22

Re: libm problem

Thus spake Till Riedel <[EMAIL PROTECTED]>: > I now know the thing that makes it break. > > cc -O2 -pipe -mcpu=pentiumpro -c /usr/src/lib/msun/src/e_pow.c > works fine! > cc -O0 -pipe -march=pentium4 -c /usr/src/lib/msun/src/e_pow.c > ... works > but... > cc -O -pipe -march=pentium4 -c /usr/src/li

Re: Port breakage (isnan undeclared)

Thus spake Tim Robbins <[EMAIL PROTECTED]>: > On Thu, Mar 20, 2003 at 12:55:22AM -0800, Kris Kennaway wrote: > > > Several ports have become broken recently with the following error: > > > > ../../../include/osg/Math:149: `isnan' undeclared (first use this function) > > > > http://bento.freebsd.

Re: libm problem

Thus spake Till Riedel <[EMAIL PROTECTED]>: > [EMAIL PROTECTED] $ cat test.c > #include "math.h" > > int main() > { > int base=8; > int dim=2; > float res; > res=pow((float)base,(float)dim); > printf("%f\n",res); > return 0; > } > [EMAIL PROTECTED] $ gcc -lm test.c > [EMAIL PROTECTED]

Re: HEADS UP: Don't upgrade your Alphas!

Thus spake Terry Lambert <[EMAIL PROTECTED]>: > David Schultz wrote: > > This is because floating point > > support on Alpha is broken unless you specifically tell gcc to > > unbreak it by specifying -mieee. > > Sounds like the ability to turn "-mieee&

Re: HEADS UP: Don't upgrade your Alphas!

Thus spake Ruslan Ermilov <[EMAIL PROTECTED]>: > Yes, as I have suspected, the gdtoa change is responsible > for a breakage. libc corresponding to this lib/libc works: > > cvs -q up -P -d -D'2003/03/12 20:20:00' > > : Using /home/ru/w/f/usr.bin/awk/nawk nawk... > > This version, together

Re: HEADS UP: Don't upgrade your Alphas!

Thus spake Ruslan Ermilov <[EMAIL PROTECTED]>: > Hold off upgrading your Alphas for a moment. > Something broke libc recently that results in > (at least) floating point exceptions from > awk(1) (this is not related to today's awk > upgrade). > > I've been able to reproduce this on beast.freebsd.o

Re: .2 isn't a valid double and other problems

Thus spake Franz Klammer <[EMAIL PROTECTED]>: > cvsup and build (kernel + userland, empty /usr/obj): > FreeBSD ds9.webonaut.com 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Sun Mar 16 > 17:53:22 CET 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/DS9 i386 > > > since my update from yesterday (above), fontco

Re: OSS SBLive driver causes kernel panic with 5.0 current

Thus spake Andre Guibert de Bruet <[EMAIL PROTECTED]>: > > On Fri, 7 Mar 2003, Jody Franklin wrote: > > > I'd been keeping up with current (world/kernel) every other week or so, > > and until this week I had no real problems. But after the build I did on > > March 3rd my soundcard driver (4Front'

Re: cvs commit: src/sys/vm vm_map.c vm_map.h vm_pageout.c

Thus spake Garrett Wollman <[EMAIL PROTECTED]>: > < said: > > > A real problem is that a swapped out process' uarea has to be > > paged back in, even when no memory is available. I don't think > > there's an easy way around that, given that you need the uarea and > > kernel stack to handle the si

Re: KSE test code?

Thus spake Ivan Voras <[EMAIL PROTECTED]>: > Is there any example code available that just tests (a "proof of > concept"-like) the KSE system on FreeBSD 5-current? See src/tools/KSE/ksetest. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the messa

Re: 4.8-PRE upgrade to FreeBSD 5 errors

Thus spake Axel Gruner <[EMAIL PROTECTED]>: > > > link_elf: symbol lminor undefined > > > link_elf: symbol splhigh undefined > > You seem to be trying to load outdated modules. > > Hmm, well, so what to do here? I switched of any module in loader.conf. THe location of modules moved between 4.x an

Re: 4.8-PRE upgrade to FreeBSD 5 errors

Thus spake Axel Gruner <[EMAIL PROTECTED]>: > Checking to see if your booted Kernel is fresh enough.. > /usr/obj/usr/src/bin/sh/sh -c 'echo "Testing installed kernel fpr new > sigaction(2) syscall"' pid 60424/sh),uid0: exited on signal 12 (core > dumped) Bad system call (core dumped) > ***Error cod

Re: Plea for base system trim

Thus spake Subscriber <[EMAIL PROTECTED]>: > Would the powers that be please consider removing sendmail, > bind and openssl from the base system, as was done for perl > with 5.0? Please don't restart this flamewar. When we have a better installer, then it may be possible in the future to select b

Re: Any ideas why we can't even boot a i386 ?

Thus spake Terry Lambert <[EMAIL PROTECTED]>: > John Baldwin wrote: > > I doubt the usefulness of this. i386 kernels were just accidentally > > broken for almost a month and a half without anyone noticing. > > People who build embedded devices that need to be supported in > the field, and want to

Re: sparc64 tinderbox failure

Thus spake Doug Barton <[EMAIL PROTECTED]>: > I made the suggestion in another forum that we create subscription lists > for these tinderbox messages so that those interested could see them, and > those not interested would not need to filter them out. > > Is anyone else interested in doing it tha

Re: Any ideas why we can't even boot a i386 ?

Just out of curiosity, is your agenda to convince everyone to nix 386 support altogether or to fix 386 support? I'm not against either, although I consider the latter goal to be a bit silly. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the messa

Re: background fsck deadlocks with ufs2 and big disk

Thus spake Martin Blapp <[EMAIL PROTECTED]>: > I just wanted to tell that I can deadlock one of my current boxes > with a ufs2 filesystem on a 120GB ATA disk. I can reproduce > the problem. The background fsck process hangs some time at the > same place always at the same place, sometimes the box f

Re: Posix testsuites?

Thus spake David Leimbach <[EMAIL PROTECTED]>: > I have been looking into helping with the C99 conformance stuff and I wondered if >the > following would be helpful? > > http://posixtest.sourceforge.net/ > > I am sure some of you knew about this... I guess I wonder if a link on the C99 web >pa

Re: -fno-builtin world breaks in gperf

Thus spake Dag-Erling Smorgrav <[EMAIL PROTECTED]>: > /usr/obj/usr/src/i386/usr/lib/libstdc++.so: undefined reference to `fabsl' > *** Error code 1 > > Our libm doesn't seem to support long double at all, yet our libstdc++ > requires long double support. It seems to correctly detect the > absence

Re: cvs commit: src/lib/libc/stdlib rand.c

Thus spake Jacques A. Vidrine <[EMAIL PROTECTED]>: > On Mon, Feb 17, 2003 at 04:40:48PM +1100, Tim Robbins wrote: > > I disagree. It's safe to use rand() in games and in certain kinds of > > simulations when you don't care that the distribution isn't quite > > uniform, > > Safe, maybe. But I thin

Re: devastating 5.0R crash

Thus spake Paul A. Mayer <[EMAIL PROTECTED]>: > I'm presently running fsck_ffs from a live cd. It fsck'ed / with some > complaints about an unreadable sector. It's now on /var and reporting > vast, vast numbers of sectors as unreadable, with "UNEXPECTED SOFT > UPDATE INCONSISTENCY". I've not

Re: cvs commit: src/lib/libc/stdlib rand.c

Thus spake Kris Kennaway <[EMAIL PROTECTED]>: > On Mon, Feb 17, 2003 at 04:40:48PM +1100, Tim Robbins wrote: > > > I disagree. It's safe to use rand() in games and in certain kinds of > > simulations when you don't care that the distribution isn't quite > > uniform, or when you prefer speed over q

Re: cvs commit: src/lib/libc/stdlib rand.c

Thus spake Kris Kennaway <[EMAIL PROTECTED]>: > I think we should commit this patch (to -current) and fix all the > problems that pop up. For example, it's used in awk (which started > this set of changes), and in some of the XFree86 libraries. ... > +__warn_references(rand_r, > + "warning: ra

Re: PLEASE TEST - ATA driver patch (ATANG)...

Thus spake Soeren Schmidt <[EMAIL PROTECTED]>: > I've prepared a patch that brings the ATA driver to the next level. > > This is mainly to prepare for other platforms which demanded > some changes to the driver infrastructure. > > It also fixes lots of outstanding problems and adds support severa

Re: Best method to produce patches?

Thus spake David Leimbach <[EMAIL PROTECTED]>: > I am about to try to make some changes to FreeBSD current... > > Should I begin to use read-only CVS instead of CVSup for this work or > is it possible to generate diffs based on CVSup'd sources? > > What is the recommend method to use for playing

Re: MSDOSFS wastes 256k when nothing is mounted!

Thus spake Poul-Henning Kamp <[EMAIL PROTECTED]>: > Somebody: please fix so this doesn't suck. Does msdosfs even have an active maintainer? There seem to be about half a dozen PRs open against it, one of which is a semi-obvious 4-line patch I submitted last April. To Unsubscribe: send mail to [E

Re: Compiling with high optimization?

Thus spake Marcin Dalecki <[EMAIL PROTECTED]>: > David Schultz wrote: > > >Strangely, gcc in FreeBSD 5.0 actually generates *slower* code > >when compiling for more recent architectures than when compiling > >for a 386. I don't know whether that is a bug in

Re: Compiling with high optimization?

Thus spake Adrian Chadd <[EMAIL PROTECTED]>: > On Sat, Feb 08, 2003, David Schultz wrote: > > > Yes, the possibility of being bitten by compiler bugs is certainly > > higher with higher optimization levels. Alpha with -O2 seems to > > have been broken for years,

Re: Compiling with high optimization?

Thus spake Terry Lambert <[EMAIL PROTECTED]>: > David Schultz wrote: > > Thus spake Terry Lambert <[EMAIL PROTECTED]>: > > > Actually, failure to use optimization suppresses some compilation > > > warnings, particularly those which normally print

Re: Compiling with high optimization?

Thus spake Terry Lambert <[EMAIL PROTECTED]>: > David Schultz wrote: > > Thus spake Ray Kohler <[EMAIL PROTECTED]>: > > > Has anyone tried building world/kernel with high optimizations (-O2, > > > -O3) recently? What breaks? (Booby prize to whoever says

Re: Compiling with high optimization?

Thus spake Ray Kohler <[EMAIL PROTECTED]>: > Has anyone tried building world/kernel with high optimizations (-O2, > -O3) recently? What breaks? (Booby prize to whoever says "common sense" > ;) I last tried it quite a few months ago and the resolver died on me, > don't know what else. I'm not really

Re: rand() is broken

Thus spake Andrey A. Chernov <[EMAIL PROTECTED]>: > On Mon, Feb 03, 2003 at 21:40:20 -0800, David Schultz wrote: > I don't try to make rand() good for high-quality pseudo-randomness, > because it can be done by price of speed and, more important, big state > size. Due to ran

Re: rand() is broken

Thus spake Eric Hodel <[EMAIL PROTECTED]>: > David Schultz ([EMAIL PROTECTED]) wrote: > > > Rather than me showing you more semi-meaningful numbers from > > Marsaglia's tests, why don't you look at the following sequence, > > which I get by taking the

Re: rand() is broken

Thus spake Andrey A. Chernov <[EMAIL PROTECTED]>: > On Sun, Feb 02, 2003 at 16:26:39 -0800, David Schultz wrote: > > > > The correlation is still present with your patch and NSHUFF set to > > 10. For instance, try seeding rand() with contiguous monotonically > >

Re: Final fix for correlation problem (was Re: rand() is broken)

Thus spake Thomas David Rivers <[EMAIL PROTECTED]>: > I'm afraid I don't understand the fix... and how it > seems to affect the historical behaviour of srand()/rand(). > > How does it address the understanding that if I use > srand(28), I will get exactly the same sequence of > numbers srand(28) p

Re: rand() is broken

Thus spake Andrey A. Chernov <[EMAIL PROTECTED]>: > On Sat, Feb 01, 2003 at 23:06:50 -0800, Kris Kennaway wrote: > > FreeBSD's rand() implementation has been broken for the past 23 > > months, since the following commit: > > > i.e. the first value returned from rand() is correlated with the seed >

Re: rand() is broken

Thus spake Bakul Shah <[EMAIL PROTECTED]>: > > As I said, I don't know how big a concern this is. But last time > > it was enough of a concern to make us keep rand() as it was. > > [I know you are talking about rand() but Mark Murray's > earlier email about wanting to re-implement random() really

Re: rand() is broken

Thus spake Andrey A. Chernov <[EMAIL PROTECTED]>: > Yes, first value correlation is there, but old formulae have even worse > effect "The random sequences do not vary much with the seed", as source > file comments and whole discussion about old RNG bad effects shown. I.e. > for different time+PID

Re: Seat-belt for source upgrades from stable to current

Thus spake Juli Mallett <[EMAIL PROTECTED]>: > * De: Giorgos Keramidas <[EMAIL PROTECTED]> [ Data: 2003-01-31 ] > [ Subjecte: Re: Seat-belt for source upgrades from stable to current ] > > On 2003-01-30 21:38, David Schultz <[EMAIL PROTECTED]> wrote: > >

Re: State of the Union Report (backout request department)

Thus spake Wesley Morgan <[EMAIL PROTECTED]>: > On Fri, 31 Jan 2003, Mike Barcroft wrote: > > > The archives might not be telling the whole story. A lot of times > > these things get handled behind closed doors, whether private e-mail > > or developer-only lists. Thankfully though, most conflict

Re: Seat-belt for source upgrades from stable to current

Thus spake Giorgos Keramidas <[EMAIL PROTECTED]>: > On 2003-01-30 21:38, David Schultz <[EMAIL PROTECTED]> wrote: > > Thus spake Mike Makonnen <[EMAIL PROTECTED]>: > > > Use the r version of the cvs commands (like cvs rlog and rdiff). They operate on > &g

Re: Seat-belt for source upgrades from stable to current

Thus spake Ruslan Ermilov <[EMAIL PROTECTED]>: > On Thu, Jan 30, 2003 at 09:58:15PM -0800, David Schultz wrote: > > I don't know about Steve, but cvsup is the wrong answer for me > > because it's a mirroring tool and not a version control tool. > > Am

Re: Seat-belt for source upgrades from stable to current

Thus spake Christopher Vance <[EMAIL PROTECTED]>: > On Thu, Jan 30, 2003 at 09:07:11PM -0800, Steve Kargl wrote: > : On Thu, Jan 30, 2003 at 08:05:06PM -0800, David Schultz wrote: > : > Thus spake Steve Kargl <[EMAIL PROTECTED]>: > : > > On Thu, Jan 30, 2003 a

Re: Seat-belt for source upgrades from stable to current

Thus spake Mike Makonnen <[EMAIL PROTECTED]>: > Use the r version of the cvs commands (like cvs rlog and rdiff). They operate on > the repository remotely, so you don't need to have the files checked out localy. That's a pretty good solution, and I use those occasionally. It would be a perfect so

Re: Seat-belt for source upgrades from stable to current

Thus spake Steve Kargl <[EMAIL PROTECTED]>: > On Thu, Jan 30, 2003 at 07:09:16PM -0800, David Schultz wrote: > > OT: Is there a good way to get the CVS metadata in /usr/src and > > /usr/ports without transferring the entire source tree over the > > network? On some ma

Re: Seat-belt for source upgrades from stable to current

Thus spake Christopher Vance <[EMAIL PROTECTED]>: > On Wed, Jan 29, 2003 at 10:35:40PM -0500, Garance A Drosihn wrote: > : How about requiring the user to touch some file in / or /boot which > : indicates the branch-tag that's acceptable for installworlds? Then > : you just need to propagate the t

Re: add ext2fs to the module list in modules/Makefile

Thus spake Juli Mallett <[EMAIL PROTECTED]>: > * De: Max Khon <[EMAIL PROTECTED]> [ Data: 2003-01-27 ] > [ Subjecte: Re: add ext2fs to the module list in modules/Makefile ] > > hi, there! > > > > On Tue, Jan 28, 2003 at 12:40:12AM +0200, Enache Adrian wrote: > > > > > On Mon, Jan 27, 2003 a

Re: boot delay when testing for ata devices

Thus spake Enache Adrian <[EMAIL PROTECTED]>: > FreeBSD used to have an irritating boot delay in 4.4. It was gone in > ~4.6, never reappeared in -STABLE, but is there in -CURRENT. > (I've seen it also mentioned in some vmware documentation). > > Applying this patch fixes it: > > --- /arc/freebsd/

  1   2   >