On Wed, Feb 01, 2023 at 12:29:02PM +0100, Florian Weimer via Gcc wrote:
> >> This impacts most (all?) Fortran code on GNU/Linux because libgfortran
> >> depends on libquadmath.
> >
> > Not anymore.
> > If GCC is configured against new enough glibc (with _Float128 support)
> > libgfortran.so.5 is no
* Jakub Jelinek:
> On Wed, Feb 01, 2023 at 11:56:42AM +0100, Florian Weimer via Gcc wrote:
>> I recently discovered that libquadmath registers custom printf callbacks
>> on load. As far as I can tell, this is done so that the Q format flag
>> can be used to print floating point numbers, using for
On Wed, Feb 01, 2023 at 11:56:42AM +0100, Florian Weimer via Gcc wrote:
> I recently discovered that libquadmath registers custom printf callbacks
> on load. As far as I can tell, this is done so that the Q format flag
> can be used to print floating point numbers, using format strings such
> as "
>> The following works for me:
>>
>> __float128 *x = calloc(sizeof(__float128), 8);
>
> Well, this does not work for me. The code compiles, but during execution
> the program crashes in this place.
You will need to investigate the crash in detail, then. Maybe it is due to
memory alignment, and
Hello Bienisaz,
> I have managed to compile the program using the quadmath, but the
> program works only if the libquadmath-0.dll is supplied in a working
> directory. I notice that there were some controversies on the internet,
> concerning the issue of static linking of the quadmath library, and
On 12/21/2010 03:44 PM, Tobias Burnus wrote:
Joel Sherrill wrote:
I was experimenting with adding microblaze-rtems*
and got this error:
>
checking for sqrtl in -lm... configure: error: Link tests are not
allowed after GCC_NO_EXECUTABLES.
make[1]: *** [configure-target-libquadmath] Error 1
I
Joel Sherrill wrote:
I was experimenting with adding microblaze-rtems*
and got this error:
>
checking for sqrtl in -lm... configure: error: Link tests are not
allowed after GCC_NO_EXECUTABLES.
make[1]: *** [configure-target-libquadmath] Error 1
I am puzzled: While this issue existed, it shoul
On 21/12/2010 14:51, Joel Sherrill wrote:
> checking how to run the C preprocessor...
> /users/joel/test-gcc/b-gcc1-microblaze/./gcc/xgcc
> -B/users/joel/test-gcc/b-gcc1-microblaze/./gcc/ -nostdinc
> -B/users/joel/test-gcc/b-gcc1-microblaze/microblaze-rtems4.11/newlib/
> -isystem
> /users/joel/tes