delorie.com/archives/browse.cgi | search |
This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --0-533472748-1452139744=:9035 Content-Type: TEXT/PLAIN; charset=UTF-8; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE On Wed, 6 Jan 2016, Britton Kerin (britton DOT kerin AT gmail DOT com) [via geda-user@= delorie.com] wrote: >On my old system the default build still seems to be 32 bit long int.=C2= =A0 I >guess things like the zoom bug Igor mentioned are due to most devels being >on 64 now. >Britton Just tried pcb-rnd on a 64 bit box, with a 2.5x2.5 meter board. I can confirm that the behaviour is different, but I can't confirm it's=20 working. I think you are right that some of the bugs are gone on 64=20 bits so I can zoom and pan, but with the gtk hid the crosshair simply=20 overflows (and jumps back to 0) at 2.1 meter. Btw, I am not against setting hard limits on board size, even as a=20 permanent solution (given the limits are large enough). E.g. if it turns=20 out you have just enough bits with double or long long int or whatever=20 type to represent a board of ~10x10 meters, but things would get very=20 complicated above, I'd just limit the board size to 10x10. I'd probably provide a disabled-by-default option for using long doubles=20 and/or gcc's builtin 128 bit ints (should work on x86_64). I think it'd be= =20 a good compromise to say that pcb is portable up to that specific board=20 size limit and if someone wants a larger board, he needs to use a 64 bit=20 system with gcc (or a compiler that supports long doubles). On the other hand, I think I will have an attempt with fixed point=20 integers in my projects. Already did some research and it doesn't look as= =20 impossible as I thought. --0-533472748-1452139744=:9035--
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |