Re: What to do about tgammal?
Le 21.12.2021 08:47, Steve Kargl a écrit : > Not at the moment. tlibm only handles math functions with > a single real agrument [1]. I've been thinking about adding > the 2 argument functions such as atan2 and complex argument > function, but lack the time. I also need to improve the man > page to decoment the default domain for each function and its > complete domain. > > [1] acos, acosh, asin, asinh, atan, atanh, cbrt, cos, cosh, erf, > erfc, exp, exp2, expm1, j0, j1, lgamma, log, log10, log1p, > log2, sin, sinh, sqrt, tan, tanh, tgamma, y0, y1. > No problem. It's a great project. Keep up posting about your progress. -- Marc
Re: What to do about tgammal?
Le 20.12.2021 16:48, Steve Kargl a écrit : > On Mon, Dec 20, 2021 at 11:15:53AM +0100, Marc Fonvieille wrote: > > > > I assume what Steve is talking about is the corresponding value in > > decimal of the number of ULP. > > > > Bad assumption. Please read Goldberg's paper. I am talking > about ULP in the underlying floating point format. > Thanks, it's more clear now: it's the ULP value. Is your tlibm_libm program available for testing ? If I find time I'd like to do some tests. -- Marc
Re: Arduino IDF -> make/automake based environment
Le 19.12.2021 21:03, Andrew Stevenson a écrit : > > > > On 19. Dec 2021, at 12:18, FreeBSD User wrote: > > > > environment. Since I'm interested in coding for some smaller AMTEL MCUs and > > ESP32 and > > like to digg a bit deeper than simply clicking a host base from a menu, I'm > > not afraid of > > doing some larger basic setup if needed. > > If by small AMTEL MCUs you mean AVRs then avr-gcc and avrdude are in ports. > For ESP32, you should look at: https://wiki.freebsd.org/electronics/arduino/esp32 and https://forums.freebsd.org/threads/a-guide-for-installing-esp32-board-for-arduino-on-freebsd12-update-2021-08-17.78408/ -- Marc
Re: What to do about tgammal?
Le 18.12.2021 17:59, Mark Murray a écrit : > > > > On 18 Dec 2021, at 17:51, Steve Kargl > > wrote: > > > > On Sat, Dec 18, 2021 at 10:41:14AM +, Mark Murray wrote: > >> > >> Hmm. I think my understanding of ULP is missing something? > >> > >> I thought that ULP could not be greater than the mantissa size > >> in bits? > >> > >> I.e., I thought it represents average rounding error (compared with > >> "perfect rounding"), not truncation error, as the above very large > >> ULPs suggest. > >> > > > > The definition of ULP differs according which expert you > > choose to follow. :-) For me (a non-expert), ULP is measured > > in the system of the "accurate answer", which is assumed to > > have many more bits of precision than the "approximate answer". > > From a very old das@ email and for long double I have > > > > Thank you! > > I checked the definition that I was used to, and it is roughly > "how many bits of the mantissa are inaccurate (because of > rounding error)". > Hi, ULP (Unit in the last place) is at first the weight of the least significant bit of the mantissa. E.g., in IEEE 754 single precision = 2^-23. It can also be seen as the distance between 2 consecutive significands (which is not the distance between 2 consecutive floating numbers). Some people, use ULP (or number of ULP) as Units (plural) in the Last Place to show the number of bits in error in the least significant bits of the significand. I assume what Steve is talking about is the corresponding value in decimal of the number of ULP. This thread is really interesting (even if I'm loosely following it). > I can see how both work. For utterly massive numbers like > from Gamma(), I can see how accounting for a much larger > range works. > > It still feels slightly tricky, as e.g. how many digits after the > floating point do you account for? > > > I don't print out the hex representation in ld128, but you see > > the number of correct decimal digits is 33 digits compared to > > 36. > > Looking good! > > M > -- > Mark R V Murray > -- Marc signature.asc Description: PGP signature
Re: 9.0-BETA1 installer issues
On Tue, Aug 02, 2011 at 08:36:01AM -0500, Nathan Whitehorn wrote: On 08/02/11 04:41, Bruce Cran wrote: I've been trying out 9.0-BETA1: it's a lot easier to install than previous releases with bsdinstall, but I spotted a few issues: Good! Thanks for checking. Typo - Resovler Configuration. If I leave the resolver window for a while it gets corrupted with: Aug 2 10:31:23 dhclient[973]: Bogus domain search list 15: lan, . Interesting. It looks like DHCP doesn't like your local setup... In the documentation installation screen, it should say At a minimum... - the 'a' is missing. Also, there should perhaps be a semi-colon between English version and this is the original. The menu also doesn't appear to do anything once you select OK. The spelling fixes are easy to fix. The documentation issue is more confusing. It should begin running pkg_add, after you press OK, assuming you selected something. Do you have the installer log handy? It will be in /tmp. [...] Hmm I think it's default PACKAGESITE env variable pointing on non-existing ftp://ftp.freebsd.org/pub/FreeBSD/ports/arch/packages-9-beta1/Latest/ -- Marc ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: 9.0-BETA1 installer issues
On Wed, Aug 03, 2011 at 08:28:34PM +0200, Marc Fonvieille wrote: On Tue, Aug 02, 2011 at 08:36:01AM -0500, Nathan Whitehorn wrote: On 08/02/11 04:41, Bruce Cran wrote: I've been trying out 9.0-BETA1: it's a lot easier to install than previous releases with bsdinstall, but I spotted a few issues: Good! Thanks for checking. Typo - Resovler Configuration. If I leave the resolver window for a while it gets corrupted with: Aug 2 10:31:23 dhclient[973]: Bogus domain search list 15: lan, . Interesting. It looks like DHCP doesn't like your local setup... In the documentation installation screen, it should say At a minimum... - the 'a' is missing. Also, there should perhaps be a semi-colon between English version and this is the original. The menu also doesn't appear to do anything once you select OK. The spelling fixes are easy to fix. The documentation issue is more confusing. It should begin running pkg_add, after you press OK, assuming you selected something. Do you have the installer log handy? It will be in /tmp. [...] Hmm I think it's default PACKAGESITE env variable pointing on non-existing ftp://ftp.freebsd.org/pub/FreeBSD/ports/arch/packages-9-beta1/Latest/ I'm wrong, I did an install and same behavior as Bruce. I looked in /tmp/bsdinstall_log: Running installation step: docsintall pkg_add: unable to fetch 'ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-9-current/Latest/en-freebsd-doc.tbz' by URL Any idea? -- Marc ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Anyone use WINE at all anywhere?
On Fri, Aug 01, 2003 at 05:38:33PM -0700, Julian Elischer wrote: Is the re ANYONE that uses wine on -current...? for that matter, a -current user that uses wine on 4.x? I sometimes uses wine to run Kazaa, I had issues with -CURRENT and wine, so I just stick on 4.X for that purpose. Marc ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: putting /dev/lpt in polling mode in boot time.
On Sun, Jul 20, 2003 at 03:29:02PM -0600, Andrew Lankford wrote: [...] ppc0 port 0x778-0x77f,0x378-0x37f irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/9 bytes threshold ppbus0: Parallel port bus on ppc0 lpt0: Printer on ppbus0 lpt0: Interrupt-driven port Try to disable ACPI. Marc ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mdconfig problems
On Thu, Feb 13, 2003 at 02:08:30PM -0700, [EMAIL PROTECTED] wrote: -su-2.05b# mdconfig -a -t vnode -f filesys mdconfig: ioctl(/dev/mdctl): No such file or directory -su-2.05b# ls /dev/md* /dev/mdctl -su-2.05b# Are you sure the file called filesys really exists? Marc To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: [PATCH] minor spelling fix
Fixed, thanks. Marc To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: 5.0-RC1: X server crash
On Mon, Dec 16, 2002 at 03:54:27AM +0100, Harald Hanche-Olsen wrote: (This is the last of my current batch of 5.0-RC1 problems.) Yeah, I know, X server problems ought to be reported to the XFree maintainers. Is there any interest for details of it here? The synopsis: The X server crashes under 5.0-RC1 where it runs fine with the exact same configuration under 4.7-RELEASE. It says Fatal server error: Caught signal 10. Server aborting and then dmesg output says it dies with signal 6 and dumping core. But I can't find any core dump lying around anywhere. I'll forward XFree86.0.log and config files if anybody here wants them, but in the interest of keeping unwanted list traffic down, I'll lay low until anybody requests this data. I'll include this line though: (--) PCI:*(1:0:0) ATI Radeon Mobility M7 LW rev 0, Mem @ 0xe000/27, 0xfcff/16, I/O @ 0xc000/8 The machine is a Dell Inspiron 4150. I use the same machine under 5.0-CURRENT (RC etc.). I used to have hangs under X, but since I removed Load dri from /etc/X11/XF86Config, it is OK. Marc To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: 5.0-RC1: X server crash
On Mon, Dec 16, 2002 at 07:07:01PM +0100, Paolo Pisati wrote: Please, try to run the memtest program (it's in the ports tree): i had a SERIOUS problem of memory corruption with my laptop (PIII, Intel815E, ATI Radeon M6, etcetc) with STABLE when i loaded the agp module. I reported this problem to the drm maintainer but he was unable to solve it... =P Run the memtest for a bit, and then report the result, maybe there's a strange bug floating around, or maybe i'm just drunk... =) We talked about a problem between X and -CURRENT, we had no problem with -STABLE. Btw I don't see how memtest can report memory corruption, I thought it was to test hardware problem. Marc To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: 5.0-RC1: X server crash
On Mon, Dec 16, 2002 at 11:25:05PM +0100, Paolo Pisati wrote: On Mon, Dec 16, 2002 at 09:55:09PM +0100, Marc Fonvieille wrote: We talked about a problem between X and -CURRENT, we had no problem with -STABLE. A problem that MAYBE is still present even in CURRENT, don't you think? Once again, I was not talking about the same problem as yours. As i said, i don't have my laptop right now, so i couldn't test CURRENT on it ( but i'll do it ASAP ), and i was looking for someone else with the same problem... Btw I don't see how memtest can report memory corruption, I thought it was to test hardware problem. hardware problem? VERY strange, cause IF i load the agp module i got errors from memtest, system freezecrash, then if i disable the agp module, memtest reports 0 errors (even after hourshours of test), no crashfreeze, etcetc As you can it doesn't look like an hardware problem, i think it's a FreeBSD-related problem, probably toggled by the agp drm stuff You missed my point, memtest is a test for hardware. From memtest site: memtest is a utility for testing the memory subsystem in a computer to determine if it is faulty. It's to test if your ram is bad, not to see a software problem. The memtest crash may come from a totally different reason and could occur in other situation. In fact you should fill a PR with all infos about your problem. Marc To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Polled mode with device.hints
On Mon, Nov 25, 2002 at 05:37:49PM +1100, Bruce Evans wrote: For sio, polled mode is configured by not creating an irq resource. Leave the irq out of the device line in the config file for RELENG_4, and don''t configure a hint for the irq in 5.x. This might not actually work since PNP or ACPI etc may always create an irq resource. Thanks for the info. But what about ppc0 ? I have to remove the IRQ line as well? (sorry I can't test now) I also noted that lptcontrol(8) does not work under 4.X and 5.X. It seems that since lpt(4) use ppbus(4), it is not possible to use lptcontrol(8). Well maybe that question does not fit with freebsd-current mailing list :) Marc To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Polled mode with device.hints
On Mon, Nov 25, 2002 at 10:32:46PM +1100, Bruce Evans wrote: [...] lptcontrol -i and lptcontrol -p work for me under -current. They presumably work because the driver sets up the interrupt for every write(2) if interrupts are enabled. This used to cause panics because a thread was created for every write and it was possible for threads to be created faster than they could exit. But everything except the thread creation and destruction seems to be necessary because the interrupt may be switched fairly dynamically between children of ppc0. I think this means that no one should want to force polled mode at the ppc0 level, and its children should have control programs like lptcontrol that permit configuring it if necessary. Ok, I will investigate more when I will have access to my -CURRENT box. Thanks a lot for your answers. Marc To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Polled mode with device.hints
Hello, I'm currently updating some part of the Handbook for 5.X, and I need to know how to put some ports like sio0 or ppc0 in polled mode. I did a search and tried some syntax like 0 for the irq etc. but no way to put something in polled mode or to find an info on it. It's a lack of device.hints(5) and some devices manual pages :) Marc To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: hw.pci.enable_io_modes default value.
On Mon, Sep 02, 2002 at 12:32:28PM -0600, M. Warner Losh wrote: I made it 1 because I wanted to get feedback on what hardware is broken. So far only two people have complained. Hundreds complained when the default was 0. Seems like the choice was good to me still. I knew there was a good reason :) Now the problem is archived in the mailing list, it will be useful for other users. Marc To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
hw.pci.enable_io_modes default value.
Hello, I had freeze at boot problem with my laptop and -CURRENT: http://www.freebsd.org/cgi/query-pr.cgi?pr=42262 I found the solution: setting hw.pci.enable_io_modes to 0. So I have a question: that sysctl has to be =1 by default? I mean if I have that issue with it and my laptop, maybe I'll not be the only one with that problem. Well I'm sure there is a good reason for that default setting. Perhaps we could write somewhere that setting may lead to hangs with some hardware :) Marc PS: btw kern/42262 can be closed :) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
