--- Comment #6 from Raf_Schietekat at ieee dot org 2007-09-23 00:29 ---
I don't know, for a debug build with symbolic information a GNU linker just
might be able to make sense of it... but I accept it would not be worthwhile.
As for the documentation, it seems the "additional 32 bit zero
--- Comment #5 from bangerth at math dot tamu dot edu 2007-09-22 22:14
---
Subject: Re: -m128bit-long-double and printf don't mix
> and came up with some of it on my own, but at the same time I thought that
> each
> object file would/could be marked with how it was compiled so that
--- Comment #4 from Raf_Schietekat at ieee dot org 2007-09-22 19:47 ---
Thanks. Somehow I had managed to miss that warning in the flag's documentation
and came up with some of it on my own, but at the same time I thought that each
object file would/could be marked with how it was compile
--- Comment #3 from bangerth at dealii dot org 2007-09-22 04:10 ---
It seems rather hard to diagnose this. If you change the ABI by using
a floating point representation using a different size of builtin types,
you probably have to build all libraries that you link with with the same
fla
--- Comment #2 from Raf_Schietekat at ieee dot org 2007-09-21 21:36 ---
If anything, not to be snapped at.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33521
--- Comment #1 from pinskia at gcc dot gnu dot org 2007-09-21 19:18 ---
And -m128bit-long-double is an ABI change so what do you expect???
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
--
