On 2/2/06, Shantonu Sen <[EMAIL PROTECTED]> wrote:
> Awesome.
>
> With trunk, your 3 previous patches, my config/darwin.h patch for the
> link line, and your further patch for visibility:
>
> [EMAIL PROTECTED] /opt/gccmath/bin/gcc -o test test.c -msselibm
> [EMAIL PROTECTED] otool -Lv test
> test:
Awesome.
With trunk, your 3 previous patches, my config/darwin.h patch for the
link line, and your further patch for visibility:
[EMAIL PROTECTED] /opt/gccmath/bin/gcc -o test test.c -msselibm
[EMAIL PROTECTED] otool -Lv test
test:
/opt/gccmath/lib/libgcc-math.0.dylib (compatibility v
On 2/1/06, Richard Guenther <[EMAIL PROTECTED]> wrote:
> On 2/1/06, Paolo Bonzini <[EMAIL PROTECTED]> wrote:
> >
> > > Is it intentional that these functions have global visibility and
> > > interfere with functions declared and implemented by the system
> > > libraries? If not, can they be compili
On 2/1/06, Paolo Bonzini <[EMAIL PROTECTED]> wrote:
>
> > Is it intentional that these functions have global visibility and
> > interfere with functions declared and implemented by the system
> > libraries? If not, can they be compilied with hidden visibility?
>
> Yes (I originally tried to "see wh
Is it intentional that these functions have global visibility and
interfere with functions declared and implemented by the system
libraries? If not, can they be compilied with hidden visibility?
Yes (I originally tried to "see what happens if we use the glibc
routines", then I shared the c
