Re: graphics/blender: math.h: isnan(): error: controlling expression type 'unsigned int' not compatible with any generic association type

2013-08-17 Thread David Chisnall
On 17 Aug 2013, at 10:48, O. Hartmann ohart...@zedat.fu-berlin.de wrote: port graphics/blender doesn't compiler neither in CURRENT nor 9.2-PRE for the moment. On CURRENT (FreeBSD 10.0-CURRENT #4 r254430: Fri Aug 16 23:23:08 CEST 2013 amd64), compilation fails with the belwo shown error

Re: graphics/blender: math.h: isnan(): error: controlling expression type 'unsigned int' not compatible with any generic association type

2013-08-17 Thread David Chisnall
On 17 Aug 2013, at 15:39, O. Hartmann ohart...@zedat.fu-berlin.de wrote: On Sat, 17 Aug 2013 11:24:41 +0100 David Chisnall thera...@freebsd.org wrote: On 17 Aug 2013, at 10:48, O. Hartmann ohart...@zedat.fu-berlin.de wrote: port graphics/blender doesn't compiler neither in CURRENT nor

Re: patch to add AES intrinsics to gcc

2013-08-23 Thread David Chisnall
I have a patch that I intend to commit before the 10.0 code slush that removes GCC and libstdc++ from the default build on platforms where clang is the system compiler. We definitely don't want to be supporting our 6-year-old versions of these for the lifetime of the 10.x branch. David On

Re: patch to add AES intrinsics to gcc

2013-08-23 Thread David Chisnall
On 23 Aug 2013, at 10:58, Bernhard Fröhlich de...@freebsd.org wrote: I don't know if you are aware that IF you really do that we will have serious problems to ship packages for 10. USE_GCC=any is the fallback in the portstree for all ports that are unable to build with clang which was

Re: patch to add AES intrinsics to gcc

2013-08-23 Thread David Chisnall
On 23 Aug 2013, at 11:42, Julian Elischer jul...@freebsd.org wrote: no, I believe we have said that 10 would ship with clang by default. NO mention was made about gcc being absent, and I am uncomfortable with taking that step yet. Having gcc just present, will not hurt you.. even after it

Re: patch to add AES intrinsics to gcc

2013-08-23 Thread David Chisnall
On 23 Aug 2013, at 13:26, Andriy Gapon a...@freebsd.org wrote: On the other hand these tools are perfect for building FreeBSD kernel and base. Extrapolating my experience with base GCC I am very confident in it as a FreeBSD development tool. Extrapolating my experience with Clang I am not

Re: GCC withdraw (was: Re: patch to add AES intrinsics to gcc)

2013-08-23 Thread David Chisnall
On 23 Aug 2013, at 14:52, Warner Losh i...@bsdimp.com wrote: No. That breaks non x86 architecutres. gcc must remain in base for now, or there's no bootstrap ability. Nobody has done the lifting to cleanly integrate gcc as a port into buildworld, althogh Brooks' work gets us most of the way

Re: patch to add AES intrinsics to gcc

2013-08-24 Thread David Chisnall
On 23 Aug 2013, at 13:30, Bernhard Fröhlich de...@freebsd.org wrote: lang/gcc42 is on the list of ports that have USE_GCC=any. So you would need to fix it first to be able to compile it with clang 3.3 from base. What is the issue with the gcc 4.2.1 build (aside from the fact that it has a

Re: GCC withdraw

2013-08-24 Thread David Chisnall
On 24 Aug 2013, at 02:35, Julian Elischer jul...@freebsd.org wrote: I don't know.. whatever RootBSD run, but the fact that I needed gcc for anything suggests that we should keep it around for a while. Please point to the FreeBSD PRs and clang bug reports that you have filed about this. I

Re: patch to add AES intrinsics to gcc

2013-08-24 Thread David Chisnall
On 23 Aug 2013, at 23:37, Warner Losh i...@bsdimp.com wrote: I'd dispute the 'and surely it seems like it does' part of this. Non x86 architectures will continue to use gcc because clang just isn't ready at this time for them. Some are very close (arm), some are close (powerpc64, mips*),

Re: GCC withdraw

2013-08-24 Thread David Chisnall
On 24 Aug 2013, at 11:30, Sam Fourman Jr. sfour...@gmail.com wrote: So I vote, let's not give ourselves the burden of lugging dead weight in base for another 5 years. (in 2017 do we still want to be worrying about gcc in base?) Perhaps more to the point, in 2017 do we want to be responsible

Re: GCC withdraw

2013-08-24 Thread David Chisnall
On 24 Aug 2013, at 12:51, Slawa Olhovchenkov s...@zxy.spb.ru wrote: Oh, I remember. mplayer on i386 can't be builded witch clang -- clang don't understand inlined asm. Clang supports inline asm. If there is some specific inline asm syntax that clang does not recognise, then please will you

Re: GCC withdraw

2013-08-24 Thread David Chisnall
On 24 Aug 2013, at 23:42, Slawa Olhovchenkov s...@zxy.spb.ru wrote: And i found PR about clang and mplayer: ports/176272 This PR contains log with build error log. Please file clang bugs at http://llvm.org/bugs/ David signature.asc Description: Message signed with OpenPGP using GPGMail

Re: GCC withdraw

2013-08-25 Thread David Chisnall
On 25 Aug 2013, at 00:06, Steve Kargl s...@troutmask.apl.washington.edu wrote: On Sat, Aug 24, 2013 at 11:44:38PM +0100, David Chisnall wrote: On 24 Aug 2013, at 23:42, Slawa Olhovchenkov s...@zxy.spb.ru wrote: And i found PR about clang and mplayer: ports/176272 This PR contains log

Re: GCC withdraw

2013-08-29 Thread David Chisnall
On 29 Aug 2013, at 15:57, John Baldwin j...@freebsd.org wrote: I have not seen any convincing argument as to why leaving GCC in the base for 10.x impedes anything. Because clang isn't sufficient for so many non-x86 platforms we can't really start using clang-specific features yet anyway.

Re: GCC withdraw

2013-08-30 Thread David Chisnall
On 29 Aug 2013, at 18:44, John Baldwin j...@freebsd.org wrote: How does removing GCC from base change this? I already deal with having 3 different GCC versions at work by building them from ports and building things with the right rpath, etc. so I am familiar with this, and having GCC in the

Re: GCC withdraw

2013-08-30 Thread David Chisnall
On 30 Aug 2013, at 08:18, Julian Elischer jul...@freebsd.org wrote: As far as I'm concerned we can even slate it for possible removal in 10.2-- if clang has proven up to the task I would be happy to ship gcc, as long as: - It's explicitly marked as deprecated and due for removal at some point

Re: GCC withdraw

2013-08-30 Thread David Chisnall
On 30 Aug 2013, at 08:56, Jonathan Anderson jonat...@freebsd.org wrote: Wouldn't this mean that we can't build base using the shipped-in-base g++? If we have C++ in base, we don't ship libstdc++ and g++ can't work with libc++, then people wanting to compile the base system with gcc/g++ will

Re: GCC withdraw

2013-08-30 Thread David Chisnall
On 30 Aug 2013, at 15:41, John Baldwin j...@freebsd.org wrote: So my take away from this is that you have no plans to support any platform that doesn't support clang as you just expect ia64 and sparc64 to die and not be present in 11.0. That may be the best path, but I've certainly not seen

Re: GCC withdraw

2013-08-30 Thread David Chisnall
On 30 Aug 2013, at 15:53, Nathan Whitehorn nwhiteh...@freebsd.org wrote: So the real driver here is switching to libc++. Is there really no way at all to use it with gcc? If, even with hacking, we could arrange that to work then it seems that all of our problems would go away. If we can make

Re: GCC withdraw

2013-08-31 Thread David Chisnall
On 31 Aug 2013, at 08:33, John-Mark Gurney j...@funkthat.com wrote: Why didn't this come up when John added XSAVE (a year ago) or Pedro Giffuni added amdfam10 support (3 months ago)? Plus, I've sent other patches earlier this year to -toolchain and made clear why I was adding them... Had I

Re: GCC withdraw

2013-09-01 Thread David Chisnall
On 1 Sep 2013, at 02:53, Benjamin Kaduk ka...@mit.edu wrote: I am worried about the definition of polished. I held my tongue in Ottawa in 2011 when Kirk wanted to turn SU+J on by default, since I figured he knew what was going on much better than I did. Then, we discovered the bad

Re: GCC withdraw

2013-09-01 Thread David Chisnall
, at 16:11, David Chisnall thera...@freebsd.org wrote: I am not proposing: ... - To deprecate any architectures - To break any architectures If a platform ends up without a working toolchain in a few years and there is no way (LLVM, recent GCC, heavily patched old GCC, vendor-supplied

Re: how do i cross build world/kernel with clang?

2013-09-02 Thread David Chisnall
On 2 Sep 2013, at 03:01, John-Mark Gurney j...@funkthat.com wrote: b/crtn.o: warning: linking PIC files with non-PIC files I think that this is an issue in our import of clang. I'll have to check whether I upstreamed the code, but it's basically just not setting the e_flags field in the ELF

Re: clang+libc++ using missing powl

2013-09-05 Thread David Chisnall
On 5 Sep 2013, at 08:14, Baptiste Daroussin b...@freebsd.org wrote: On Thu, Sep 05, 2013 at 09:05:45AM +0200, Dimitry Andric wrote: On Sep 5, 2013, at 00:38, Baptiste Daroussin b...@freebsd.org wrote: I'm running exp-run to build the whole ports tree with clang using libc++ by default. As

Re: clang+libc++ using missing powl

2013-09-05 Thread David Chisnall
On 4 Sep 2013, at 23:38, Baptiste Daroussin b...@freebsd.org wrote: As a result we have a lot of fallouts of ports complaining about: undefined reference to `powl' It seems like libc++ is relying on a function we don't have yet in libm, am I missing something? I've attached a diff that I'd

Re: clang+libc++ using missing powl

2013-09-06 Thread David Chisnall
On 5 Sep 2013, at 22:09, Steve Kargl s...@troutmask.apl.washington.edu wrote: On Thu, Sep 05, 2013 at 09:52:13AM +0100, David Chisnall wrote: On 4 Sep 2013, at 23:38, Baptiste Daroussin b...@freebsd.org wrote: As a result we have a lot of fallouts of ports complaining about: undefined

HEADS UP: No gcc by default in -HEAD on platforms where clang is cc

2013-09-06 Thread David Chisnall
Hi Everyone, As of r255321, we are no longer building gcc or libstdc++ as part of the default install on platforms where clang is cc. If you are using gcc, you have two options: 1) Install one of the lang/gcc* ports (Warner has been working on separating out the patches to our GCC, so these

Re: clang+libc++ using missing powl

2013-09-06 Thread David Chisnall
On 6 Sep 2013, at 16:59, Steve Kargl s...@troutmask.apl.washington.edu wrote: Well, your commit has pre-empted any discussion on whether there would have been a better kludge. Oh well. I'm very happy for it to be replaced by something better (and would be ecstatic for it to go away

Re: HEADS UP: No gcc by default in -HEAD on platforms where clang is cc

2013-09-09 Thread David Chisnall
On 9 Sep 2013, at 14:27, Ulrich Spörlein u...@freebsd.org wrote: Case in point, I only recently switched to clang in base and now the newsbeuter port crashes during startup (yeah, it builds fine). So all I'm asking for now is: how can I override a random port to be built with gcc (either from

Re: HEADS UP: No gcc by default in -HEAD on platforms where clang is cc

2013-09-12 Thread David Chisnall
On 11 Sep 2013, at 21:06, David O'Brien obr...@freebsd.org wrote: It is still very useful for folks to test changes in order to help ensure one doesn't break the build on platforms still using GCC. If you want to do this test, then you should do make universe or make tinderbox (you should do

Re: how do i cross build world/kernel with clang?

2013-09-16 Thread David Chisnall
On 15 Sep 2013, at 23:28, Joe Holden li...@rewt.org.uk wrote: Are you still playing with this? Reason I ask is that I tried to build world with clang for the crack and it bails with: /usr/obj/mips.mips64/pseudosrc/tmp/usr/bin/ld: /usr/obj/mips.mips64/pseudosrc/tmp/usr/lib/crtn.o: warning:

Re: -ffunction-sections, -fdata-sections and -Wl,--gc-sections

2013-09-16 Thread David Chisnall
On 16 Sep 2013, at 07:52, Dimitry Andric d...@freebsd.org wrote: On Sep 16, 2013, at 03:08, Adrian Chadd adr...@freebsd.org wrote: The results are interesting. On amd64: - devd suddenly becomes 500 KB in size, instead of a megabyte, - init's size drops from 900 KB to 600 KB, - clang

Re: -ffunction-sections, -fdata-sections and -Wl,--gc-sections

2013-09-18 Thread David Chisnall
On 18 Sep 2013, at 07:22, Konstantin Belousov kostik...@gmail.com wrote: I think this is a wrong direction. First, the split should be done at the source level, as it was usually done forever. Until we are all using toolchains that support LTO (which requires importing a new linker and will

Re: gnome2 build error (evolution-data-server-2.32.1_4)

2013-09-18 Thread David Chisnall
This looks like the namespace pollution that was caused by iconv.h including stdbool.h, which I have already fixed. David On 18 Sep 2013, at 14:57, Ricardo Campos Passanezi ri...@ige.unicamp.br wrote: Hello, I was trying to install gnome2 port but it ends up with an error in

Re: libreoffice build error

2013-09-18 Thread David Chisnall
On 18 Sep 2013, at 16:26, Tijl Coosemans t...@freebsd.org wrote: On Tue, 17 Sep 2013 21:04:14 -0400 Jung-uk Kim wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2013-09-17 13:24:41 -0400, Jung-uk Kim wrote: I am still working on libc++ issues but it is much more complicated. :-(

Re: libreoffice build error

2013-09-18 Thread David Chisnall
On 18 Sep 2013, at 19:31, Tijl Coosemans t...@freebsd.org wrote: There are some pointers to the start such as the caughtExceptions field in struct __cxa_eh_globals and the nextException field in struct __cxa_exception itself. These are not part of the public API. David

Re: libreoffice build error

2013-09-18 Thread David Chisnall
On 18 Sep 2013, at 19:49, David Chisnall thera...@freebsd.org wrote: These are not part of the public API. Oh. Yes it is. Ho hum... David ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current

Re: graphics/poppler-glib not build

2013-09-28 Thread David Chisnall
This looks like it's compiling C++ with clang and trying to link it with gcc. Is there a CXXLD=g++ in there somewhere? David On 28 Sep 2013, at 15:23, Alexander Panyushkin vsi...@gmail.com wrote: Hi all After upgrade ports graphics/poppler-glib not build anymore. pkg_info -R

Re: graphics/poppler-glib not build

2013-09-28 Thread David Chisnall
) gmake[3]: *** [libpoppler-glib.la] Error 1 *** Error code 1 On 28.09.2013 20:14, David Chisnall wrote: This looks like it's compiling C++ with clang and trying to link it with gcc. Is there a CXXLD=g++ in there somewhere? David On 28 Sep 2013, at 15:23, Alexander Panyushkin vsi

Re: rcs is gone?

2013-10-07 Thread David Chisnall
On 7 Oct 2013, at 22:14, Lyndon Nerenberg lyn...@orthanc.ca wrote: Install from ports is a non-starter. Our development systems will never be connected to the internet for a ports upgrade. In this environment, in-base RCS is a very useful tool. Why is install from packages any harder than

Re: gperf/src/options.cc -- quiesce clang warnings -Wlogical-op-parentheses

2013-10-22 Thread David Chisnall
On 22 Oct 2013, at 00:43, Sean Bruno sean_br...@yahoo.com wrote: Heh, Matthew suggested the obvious in private mail, it seems that this would be better spelled as isalpha :-) This looks wrong. The behaviour of isalpha() depends on the current locale. You probably want isalpha_l(), with the

Re: gperf/src/options.cc -- quiesce clang warnings -Wlogical-op-parentheses

2013-10-24 Thread David Chisnall
On 24 Oct 2013, at 21:13, Sean Bruno sean_br...@yahoo.com wrote: On Tue, 2013-10-22 at 09:47 +0100, David Chisnall wrote: On 22 Oct 2013, at 00:43, Sean Bruno sean_br...@yahoo.com wrote: Heh, Matthew suggested the obvious in private mail, it seems that this would be better spelled

Re: gperf/src/options.cc -- quiesce clang warnings -Wlogical-op-parentheses

2013-10-25 Thread David Chisnall
On 24 Oct 2013, at 21:50, Sean Bruno sean_br...@yahoo.com wrote: On Thu, 2013-10-24 at 21:24 -0400, David Chisnall wrote: Don't forget the freelocale() at the end. ah, ok. I wish that there was some kind of example that I could go off of in the man page. I'm sort of trundling my way

Re: Are clang++ and libc++ compatible?

2013-11-12 Thread David Chisnall
On 12 Nov 2013, at 16:32, Steve Kargl s...@troutmask.apl.washington.edu wrote: Trying to build news/pan with clang++ dies with gmake[3]: Entering directory `/usr/ports/news/pan/work/pan-0.139/pan/general' CXXfile-util.o In file included from file-util.cc:38: In file included from

Re: Are clang++ and libc++ compatible?

2013-11-12 Thread David Chisnall
On 12 Nov 2013, at 16:54, Steve Kargl s...@troutmask.apl.washington.edu wrote: On Tue, Nov 12, 2013 at 04:38:17PM +, David Chisnall wrote: On 12 Nov 2013, at 16:32, Steve Kargl s...@troutmask.apl.washington.edu wrote: Trying to build news/pan with clang++ dies with gmake[3

Re: Are clang++ and libc++ compatible?

2013-11-13 Thread David Chisnall
On 12 Nov 2013, at 18:21, John Baldwin j...@freebsd.org wrote: struct foo { struct foo bar; } Except it isn't. It's declaring the head of a container. This is more like: struct foo { TAILQ_HEAD(, foo) messages; }; Eitan is correct here. The definition of

Re: libc++ vs. libstdc++ usage in the ports tree

2013-11-14 Thread David Chisnall
On 13 Nov 2013, at 19:40, Dimitry Andric d...@freebsd.org wrote: On the other hand, different C++ standard libraries simply cannot be mixed. The internal implementations are usually completely different. This is not really news at all, certainly not to the ports people. :-) That said, it

Re: [RFC] how to get the size of a malloc(9) block ?

2013-11-29 Thread David Chisnall
On 28 Nov 2013, at 15:13, jb jb.1234a...@gmail.com wrote: Luigi Rizzo rizzo at iet.unipi.it writes: ... But I don't understand why you find ksize()/malloc_usable_size() dangerous. ... The original crime is commited when *usable size* (an implementation detail) is exported (leaked) to

Re: [HEADS UP] enabling LLDB debugger by default on amd64

2013-12-18 Thread David Chisnall
Hi Ed, How are you planning on building the LLVM / Clang libraries? Will they be statically linked to the compiler and the debugger, or do you intend to make them dynamic too? I found about a small slowdown with a dynamic clang, but the link times were much lower when building. Currently,

Re: RFC: less chatty system builds

2013-12-19 Thread David Chisnall
On 16 Dec 2013, at 21:35, Dimitry Andric d...@freebsd.org wrote: In any case, if anything like this is implemented, I would really prefer something like CMake does, e.g. give you a percentage counter that provides some information about how 'far' the build is progressing. I haven't seen this

Re: RFC: less chatty system builds

2013-12-19 Thread David Chisnall
On 19 Dec 2013, at 09:40, Luigi Rizzo ri...@iet.unipi.it wrote: If a command produces warning output but exits with success, then that command's output is dumped to stdout (explicitly serialised by Ninja so that it's never interleaved with another command's output). If a command exits

Re: did SVN r227753 (locale changes) break something?

2011-11-22 Thread David Chisnall
On 22 Nov 2011, at 00:21, Michael Butler wrote: #0 0x283eb243 in fprintf () from /lib/libc.so.7 This looks suspicious. uselocale() does not call fprintf(). In fact, nothing in xlocale.c does - fprintf() accesses the current locale, so calling it from anywhere in the setlocale() path is

Re: did SVN r227753 (locale changes) break something?

2011-11-22 Thread David Chisnall
It's entirely possible - please can you compile libc with debug symbols? The back trace isn't very informative... David On 22 Nov 2011, at 00:21, Michael Butler wrote: VLC (multimedia/vlc) on my -current now crashes leaving a trace like this .. imb@toshi:/home/imb gdb `which vlc` vlc.core

Re: did SVN r227753 (locale changes) break something?

2011-11-22 Thread David Chisnall
On 22 Nov 2011, at 14:00, Michael Butler wrote: On 11/22/11 08:52, David Chisnall wrote: Please can you try this patch? ... That works :-) Thanks! Fixed in head (r227818), thanks for the report! David ___ freebsd-current@freebsd.org mailing

Heads up: New C++ stack

2011-11-26 Thread David Chisnall
Hi, I've just imported libc++[1] and libcxxrt[2] to head. libc++ is UUIC licensed, libcxxrt is 2-clause BSDL. The former implements the C++ standard template library, and provides all of the programmer-visible parts. The latter provides an implementation of the ARM and Itanium ABI

Re: Heads up: New C++ stack

2011-11-27 Thread David Chisnall
On 26 Nov 2011, at 23:09, Niclas Zeising wrote: This is great news! Thank you very much for undertaking this work. Just a question, is there a wiki page with these instructions, or a wiki page related to this work where these instructions can be added? If they're not on the wiki, I can do

Re: Heads up: New C++ stack

2011-11-27 Thread David Chisnall
On 27 Nov 2011, at 15:26, O. Hartmann wrote: Why is the knob WITH_LIBCPLUSPLUS=yes located in /etc/make.conf and not in /etc/src.conf? Sorry, it is in src.conf, I was thinking about enabling clang. Or possibly not thinking at all. It's Sunday, so thinking is optional...

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

2012-07-13 Thread David Chisnall
On 13 Jul 2012, at 13:18, John Baldwin wrote: On Friday, July 13, 2012 7:41:00 am Peter Jeremy wrote: AFAIK, none of the relevant standards (POSIX, IEEE754) have any precision requirements for functions other than +-*/ and sqrt() - all of which we have correctly implemented. I therefore

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

2012-07-14 Thread David Chisnall
On 13 Jul 2012, at 17:40, Warner Losh wrote: We shouldn't be gating the new math on an issue that only affects sparc64 machines Mostly agreed, but it's worth noting that the APCS for ARMv8[1] specifies that long double should be IEEE 754- 2008 quad precision. I think ARMv8 is going to be

Re: -current build failure

2012-07-20 Thread David Chisnall
On 20 Jul 2012, at 17:33, Konstantin Belousov wrote: It is not related to dtrace at all, and indeed OFFSETOF_CURTHREAD is 0. This is a bug in clang, we compile our kernel in freestanding environment. The copies of the C spec that I have do not differentiate between freestanding and hosted

Re: -current build failure

2012-07-21 Thread David Chisnall
On 21 Jul 2012, at 00:16, Konstantin Belousov wrote: Ok, I stand corrected. But the standard does not say what you claim either. It only specifies that NULL pointer is unequal to any pointer to object or function (implicitely saying that you can create a C object or function pointer to which

Re: -current build failure

2012-07-22 Thread David Chisnall
On 21 Jul 2012, at 22:16, Konstantin Belousov wrote: On Sat, Jul 21, 2012 at 04:00:45PM -0400, Kim Culhan wrote: On Fri, Jul 20, 2012 at 11:40 AM, Dimitry Andric d...@freebsd.org wrote: On 2012-07-20 16:49, Kim Culhan wrote: Seeing this for r:238655 ... In file included from

Re: -current build failure

2012-07-23 Thread David Chisnall
On 23 Jul 2012, at 20:18, Konstantin Belousov wrote: Longer description is that pc_curthread is offset 0 if %gs-based. The dereferenced pointer point to the struct thread, which contains td_proc pointer at offset 8. Instead, clang seems to dereference td_proc from offset 8 based on %gs, or

Re: -current build failure

2012-07-24 Thread David Chisnall
On 23 Jul 2012, at 20:53, David Chisnall wrote: On 23 Jul 2012, at 20:18, Konstantin Belousov wrote: Longer description is that pc_curthread is offset 0 if %gs-based. The dereferenced pointer point to the struct thread, which contains td_proc pointer at offset 8. Instead, clang seems

Re: -current build failure

2012-07-25 Thread David Chisnall
On 24 Jul 2012, at 23:43, Konstantin Belousov wrote: As kan rightfully notes, the assumption that %fs:0 == *%fs:0 holds for userspace on amd64, and the same is true for %gs userspace on i386. The change you committed to clang/llvm/whatever it called just breaks useful optimization for

Re: RFC: libkern version of inet_ntoa_r

2012-07-29 Thread David Chisnall
On 29 Jul 2012, at 10:58, Luigi Rizzo wrote: 3. nuke inet_ntoa_r() from libc inet_ntoa_r is a public symbol and therefore part of our ABI contract with userspace applications. Even if no one that we are aware of is using it, we should officially deprecate it for one major release before

Re: On cooperative work [Was: Re: newbus' ivar's limitation..]

2012-08-02 Thread David Chisnall
On 2 Aug 2012, at 05:30, Doug Barton wrote: I used to ask the PTB to provide *some* form of remote participation for even a fraction of the events at the dev summit. I don't bother asking anymore because year after year my requests were met with any of: indifference, hostility, shrugged

Re: On cooperative work [Was: Re: newbus' ivar's limitation..]

2012-08-02 Thread David Chisnall
On 2 Aug 2012, at 17:46, Doug Barton wrote: Well that's a start. :) And where was this availability announced? If I missed it, that's on me. But providing remote access that you don't tell people about isn't really any better than not providing it at all. It's not widely advertised, because

Re: On cooperative work [Was: Re: newbus' ivar's limitation..]

2012-08-02 Thread David Chisnall
On 2 Aug 2012, at 18:28, Doug Barton wrote: Welcome to the 21st Century. :) There are widely available audio and video conferencing solutions that easily scale into the thousands of users, at minimal cost. Yes, It takes effort. I get that. I've been part of the effort to provide remote

Re: On cooperative work [Was: Re: newbus' ivar's limitation..]

2012-08-02 Thread David Chisnall
On 2 Aug 2012, at 18:47, Doug Barton wrote: Cheap copout. And quite sad, especially coming from a newly elected core team member. FreeBSD is a volunteer project. Our DevSummits are not run by a commercial organisation, they are run by volunteers. I am not being paid to organise the

Re: On cooperative work [Was: Re: newbus' ivar's limitation..]

2012-08-02 Thread David Chisnall
Thank you for your thoughtful reply, On 2 Aug 2012, at 19:33, Doug Barton wrote: However, my point is that in spite of the fact that it's non-trivial, the mindset on this topic needs to change if the dev summits are going to continue to be significant focii of both work being done and

Re: FreeBSD development audio system: KLANG

2012-08-13 Thread David Chisnall
On 13 Aug 2012, at 07:57, Volodymyr Kostyrko wrote: 1. It's targeted at fixing Linux bugs, not FreeBSD ones. FreeBSD sound system had in-kernel virtual channel mixing support for years. I found this to be the major issue. There were very few things on the list that weren't already supported

Re: Compiler performance tests on FreeBSD 10.0-CURRENT

2012-09-05 Thread David Chisnall
On 5 Sep 2012, at 10:31, Dimitry Andric wrote: These are just the default FreeBSD optimization flags for building clang, which are probably used by the majority of users out there. This is the case that I was interested in particularly. The -fno-strict-aliasing is not really my

Re: Compiler performance tests on FreeBSD 10.0-CURRENT

2012-09-06 Thread David Chisnall
On 6 Sep 2012, at 09:43, Roman Divacky wrote: Was this compiled as amd64 or i386? Also, can you send me the test case? So that we can explore the difference. The working theory now is SSE vs FPU mathematics, but it would be nice to see the testcase. There may also be a difference in whether

Re: Clang as default compiler November 4th

2012-09-11 Thread David Chisnall
I'd add one more thing that needs fixing: Clang should default to c89 mode when invoked as cc. I had a patch to do this, but I seem to have misplaced it. I'll try to find or rewrite it in the next couple of days. A lot of the ports failures I saw were due to ports using cc as the default C

Re: Clang as default compiler November 4th

2012-09-11 Thread David Chisnall
On 11 Sep 2012, at 09:18, Dimitry Andric wrote: So I am a bit reluctant to change clang's default standard to c89, unless clang upstream agrees with this. In the interest of prodding people to update their software, I would rather have the default stay c99, personally. :) I'm not proposing

Re: Clang as default compiler November 4th

2012-09-12 Thread David Chisnall
On 12 Sep 2012, at 10:09, Doug Barton wrote: Also, users who actually are helping with testing clang for ports continue to report runtime problems, even with things that build fine. I hope that you are encouraging maintainers of ports that don't work as expected with clang to submit bug

Re: November 5th is Clang-Day

2012-11-02 Thread David Chisnall
On 2 Nov 2012, at 05:24, Jan Beich wrote: Known Issues emulators/wine doesn't work with lib32 built by clang, probably due to wine bugs. Is this still the case? There was an issue preventing WINE from working because it required stricter stack alignment than clang provided by default,

Re: FORTRAN vs. Fortran (was: November 5th is Clang-Day)

2012-11-02 Thread David Chisnall
On 2 Nov 2012, at 08:18, Mehmet Erol Sanliturk wrote: Very many years ago , when 2010 was a very distant future , I do not remember the name of the writer , who wrote approximately : In 2010 , there will be Fortran , but a Fortran which may be different . I remember a talk in the mid '90s

Re: 9.1-RC3 feels okay :-)

2012-11-07 Thread David Chisnall
On 7 Nov 2012, at 08:20, Warren Block wrote: It's not saying that hald is run by default, merely that xorg-server will try to use it by default. And will fail to detect any input devices if hald is not running, but will correctly detect them if the X server is compiled without HAL support.

Re: compiler info in kernel identification string

2012-11-16 Thread David Chisnall
On 16 Nov 2012, at 07:41, Dimitry Andric wrote: And regarding clang, I don't have the time to implement this very soon, and I doubt it is very high on the bug priority list with upstream either. They just branched for the 3.2 release, and they are much busier squashing bugs now. :)

Re: new xorg segfault 11 with KMS

2012-12-13 Thread David Chisnall
On 13 Dec 2012, at 21:48, Johannes Dieterich wrote: GNU gdb 6.1.1 [FreeBSD] You might try with gdb 7.x from ports. gdb 6.1.1 from the base system doesn't do a good job of understanding the newer version of DWARF that clang emits. David ___

Re: Request import of fix for clang 3.2 bug

2012-12-14 Thread David Chisnall
Looks like it's been imported to the 3.2 branch, so we should get it when dim pulls in the latest version. David On 14 Dec 2012, at 14:14, Guido Falsi wrote: I have stumbled upon a solved bug in clang 3.2 while testing some ports: http://llvm.org/bugs/show_bug.cgi?id=14491 Fixed in this

Re: Unbreaking gdb's catch throw

2013-01-04 Thread David Chisnall
Is this on 9.1? In -CURRENT and 9.1, libstdc++ is a filter library, and libsupc++ or or libcxxrt are the filtee. This means that the __cxa_throw symbol appears to be in libstdc++ (for symbol versioning purposes), but is actually in the ABI library. If you tell gdb to put the breakpoint on

Re: Unbreaking gdb's catch throw

2013-01-04 Thread David Chisnall
On 4 Jan 2013, at 12:49, Stefan Farfeleder wrote: On Fri, Jan 04, 2013 at 12:38:44PM +, David Chisnall wrote: Is this on 9.1? In -CURRENT and 9.1, libstdc++ is a filter library, and libsupc++ or or libcxxrt are the filtee. This means that the __cxa_throw symbol appears

Re: ZFS/RAIDZ and SAMBA: abyssimal performance

2013-01-05 Thread David Chisnall
On 4 Jan 2013, at 20:39, Rick Macklem wrote: What about capturing a few examples, like this one for a system with 16Gb of Ram. Basically cases of: - this is my hardware config and here's what works well for me It's pretty easy for people to choose the example closest to their setup as a

Re: clang 3.2 RC2 miscompiles libgcc?

2013-01-06 Thread David Chisnall
On 6 Jan 2013, at 14:17, Stefan Farfeleder wrote: On Fri, Jan 04, 2013 at 04:49:41PM +0100, Stefan Farfeleder wrote: Here's a minimal test case that reproduces the bug: [...] Until someone fixes this bug, could we apply something like this as a work-around? Stefan Index:

Re: LLVM 3.2: official stable port is still LLVM 3.1. Basesystem missing important LLVM pieces!

2013-01-06 Thread David Chisnall
On 6 Jan 2013, at 12:55, O. Hartmann wrote: Having a crippled LLVM aboard AND the need having installed a port is a kind of none-sense. Why should I install port devel/llvm to have a working LLVM backend? The issue is the same as the issue for anything in the FreeBSD base system, which is:

Re: clang 3.2 RC2 miscompiles libgcc?

2013-01-06 Thread David Chisnall
On 6 Jan 2013, at 16:48, Nathan Whitehorn wrote: No. It's completely broken at all optimization levels. There do not appear to be any flags that change the behavior. Building unwind-dw2.c either with gcc or with the previous import of clang in our tree does fix it, however. Do you have an

Re: LLVM 3.2: official stable port is still LLVM 3.1. Basesystem missing important LLVM pieces!

2013-01-07 Thread David Chisnall
On 6 Jan 2013, at 20:38, Erik Cederstrand wrote: You can't seriously blame LLVM for making progress. If ports rely on a specific version of LLVM, it would be far better to create devel/llvm31, devel/llvm32 etc. Well, I can (and, even with my LLVM committer hat on, do) blame LLVM for not

Re: clang 3.2 RC2 miscompiles libgcc?

2013-01-08 Thread David Chisnall
On 7 Jan 2013, at 23:21, Dimitry Andric wrote: This is at least the direction I'm looking at. It seems that in some cases with __builtin_eh_return(), llvm does not see that registers can be clobbered, and it doesn't save and restore them. Do you mean that some registers were clobbered by a

Re: [rfc] removing/conditionalising WERROR= in Makefiles

2011-12-30 Thread David Chisnall
On 30 Dec 2011, at 13:06, Dimitry Andric wrote: sys/gnu/fs/xfs/xfs_dir2_block.c:1149:17: warning: array index of '1' indexes past the end of an array (that contains 1 element) [-Warray-bounds] I recall some discussion of this warning on the clang list a few months ago, and I believe that it

Re: [RFC] Un-staticise the toolchain

2012-04-26 Thread David Chisnall
On 26 Apr 2012, at 12:38, Bob Bishop wrote: Hi, On 26 Apr 2012, at 10:35, Konstantin Belousov wrote: I think it is time to stop building the toolchain static. I was told that original reasoning for static linking was the fear of loosing the ability to recompile if some problem appears

Re: The current libc/locale/toupper.c is mistaken

2012-05-10 Thread David Chisnall
If you have a test case, I can commit it to the libc++ test suite. David On 10 May 2012, at 21:42, Kohji Okuno wrote: Hi Eric, I'm left wondering how this was not caught by the libc++ test suite. The current toupper.c shouldn't pass

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

2012-05-28 Thread David Chisnall
On 28 May 2012, at 05:35, Rainer Hurling wrote: Yesterday r236148 (Allow inclusion of libc++ cmath to work after including math.h) was comitted to head, many thanks. Does this mean, that extra long double functions like acoshl, expm1l or log1pl are now really implemented? As far as I

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

2012-05-28 Thread David Chisnall
On 28 May 2012, at 13:30, Rainer Hurling wrote: On 28.05.2012 10:41 (UTC+1), David Chisnall wrote: On 28 May 2012, at 05:35, Rainer Hurling wrote: Ok, that's what I had supposed. Because the main difference between r236147 and r2136148 seems to be the define of _MATH_EXTRA_H_, the rest

Re: r245838: make world fails: /usr/src/usr.bin/dtc/dtc.cc:196:24: error: use of undeclared identifier 'optarg', string arg = string(optarg);

2013-01-23 Thread David Chisnall
This appears to be caused by your addition of -stdlib=libc++ -std=c++11 to your CXXFLAGS. So, first of all, thank you for testing libc++! I tested with libc++ while I was developing dtc, but then was building with libstdc++ while I was removing extraneous includes. Unfortunately, libstdc++

Re: r246057: buildworld fails with: /usr/obj/usr/src/tmp/usr/lib/libc++.so: undefined reference to `std::bad_alloc::~bad_alloc()'

2013-01-29 Thread David Chisnall
On 29 Jan 2013, at 10:48, O. Hartmann wrote: On 01/29/13 11:08, David Chisnall wrote: On 29 Jan 2013, at 10:06, O. Hartmann wrote: I receive this error since yesterday building world and it is still sticky on most recent sources (r246057) and I was wondering why the tinderboxes do not pick

Re: r246057: buildworld fails with: /usr/obj/usr/src/tmp/usr/lib/libc++.so: undefined reference to `std::bad_alloc::~bad_alloc()'

2013-01-29 Thread David Chisnall
On 29 Jan 2013, at 10:06, O. Hartmann wrote: I receive this error since yesterday building world and it is still sticky on most recent sources (r246057) and I was wondering why the tinderboxes do not pick this up on the 10.0-CURRENT builds ... just for a notice for the development folks ...

  1   2   3   >