On 4 March 2013 22:17, Philippe Waroquiers
philippe.waroqui...@skynet.be wrote:
On Mon, 2013-03-04 at 22:08 +0100, Roland Mainz wrote:
On Mon, Mar 4, 2013 at 9:29 PM, Philippe Waroquiers
philippe.waroqui...@skynet.be wrote:
GNAT runtime is implementing various features (e.g. float images)
On Tue, 2013-03-05 at 18:54 +0100, Lionel Cons wrote:
(1) in https://bugs.kde.org/show_bug.cgi?id=197915#c9 is a joke:
Julian Seward 2010-07-12 15:58:25 UTC
As per comment #0, adding support for 80-bit floats is low priority,
because (1) AIUI the majority of floating point code is portable
Hi,
I'm using valgrind on a small Ada program (attached).
The Ada program runs fine on the linux host, it prints 8.5.
When I run the program through valgrind, it prints 0.0.
Any ideas why this might be?
I tried this with gnatmake with gnu 4.1.2 and gnu 4.2 on,
$ uname -a
Linux maple
Hi Bob,
I'm using valgrind on a small Ada program (attached).
The Ada program runs fine on the linux host, it prints 8.5.
When I run the program through valgrind, it prints 0.0.
Any ideas why this might be?
I tried and it works fine for me: gnatmake from gcc-4.2 and gcc-4.8,
On Mon, 2013-03-04 at 22:08 +0100, Roland Mainz wrote:
On Mon, Mar 4, 2013 at 9:29 PM, Philippe Waroquiers
philippe.waroqui...@skynet.be wrote:
GNAT runtime is implementing various features (e.g. float images)
by using long_long_float, which are 80 bits floats.
As these are not properly
