Please add ${PREFIX}/bin/gcc44 to your PATH variable
before using this port.
WWW: http://gcc.gnu.org/
PR: ports/136359
Submitted by: M Rothwell <freebsd-ports@coreland.ath.cx> (maintainer)
2.6.
NOTE: this port is slightly evil and both depends on llvm and builds all
of it. We hope to find the correct make string to fix this, but wanted
make clang available now.
regular GCC 4.4.2 release. GCC 4.4 is in strict regression only fix
mode, so updates are quite safe, but if you want to lock on a certain
snapshot, this may be one.
is able to outperform hand-written C in a number of tests.
This is a modified version suitable to use on FreeBSD i386/amd64.
It possible to run it on other platfroms as well, but I have not
boostrapped/tested it on anything except i386/amd64 yet.
Author: Jeffrey Mark Siskind
WWW: http://cobweb.ecn.purdue.edu/~qobi/software.html
- On FreeBSD >= 7.2 allocate the new thread with adequate amount of stack
space to run the main ruby code in. This allows to mitigate problem
when too low stack space available for ruby when running with pthreads
enabled.
- Bump portrevision.
The long version. Before this change we used to link ruby against pthreads
uncoditionally on all versions of FreeBSD. This is indispensable in order
to load the threaded shared objects withing ruby. However, this causes a
dramatic decrease in the stack space available as pthreads only allows
up to several megabytes of stack space for the main application threads.
The only solution to this is to create the new thread immediately after
the program start with rigth stack size attributes set. Nonetheless this
scheme won't work for us on FreeBSD version before 7.2 as malloc implementation
in these versions was not threaded fork safe (i.e. this is impossible to
fork from the threaded program and expect malloc/free functions to work).
Thus the only solution for now can be to disable pthreads entirely on
FreeBSD <= 7.2. This won't cause any performance/usability problems for
users as Ruby 1.8 uses green threads, however it may prevent <= 7.2
users to load shared libraries linked agains pthreads.
Reported by: "François Montel" <seanmullen@gmail.com>
Tested by: Sean Mullen <seanmullen@gmail.com>
