GNAT 3.15p

2003-02-19 Thread Jérôme Marant
Hi, GNAT 3.15p has been released last November and it is still not packaged in Debian. Since, the GNAT from GCC tree is still not stable enough, I'd suggest that we keep on updating the ACT public release. Jon Ward told he was packaging it but nothing seemed to happen. Is anyone st

Re: c/9762: Address of 'char' is incorrect.

2003-02-19 Thread Neil Booth
[EMAIL PROTECTED] wrote:- > In the example below, '&a' is the address of a local copy of 'a' not of > 'a'. > if the type of 'a' is changed to int, it works as expected. Works as who expected? Where is the bug? Please quote which part of the C standard is violated. You got an addre

Bug#181679: gnat-3.2: Preelaborate, exceptions, and -gnatN

2003-02-19 Thread Victor Porton
Package: gnat-3.2 Version: 1:3.2.3-0pre1 3.2.3 20030210 (prerelease) (i386-pc-linux-gnu) Compiler gives a wrong error message: pts/7:x,1$ gcc-3.2 -c -gnatN p.ads p.ads:5:08: instantiation error at s-exctab.adb:169 p.ads:5:08: non-static call not allowed in preelaborated unit package P is p

Address of 'char' is incorrect.

2003-02-19 Thread stephen . kennedy
>Submitter-Id: net >Originator:Stephen Kennedy >Organization: Telekinesys Research >Confidential: no >Synopsis: Address of 'char' is incorrect. >Severity: serious >Priority: medium >Category: c >Class: wrong-code >Release: 3.2.3 20030210 (Debian prerelease)

Bug#181660: gnat-3.2: internal compiler error

2003-02-19 Thread Florian Weimer
Victor Porton <[EMAIL PROTECTED]> writes: > | Error detected at > /usr/lib/gcc-lib/i386-linux/3.2.3/adainclude/i-cpoint.adb:4 > 1:1 [/usr/include/gtkada/gdk-even This is a well-known GNAT bug, GCC PR 5679.

Bug#181660: gnat-3.2: internal compiler error

2003-02-19 Thread Victor Porton
Package: gnat-3.2 Version: 1:3.2.3-0pre1 3.2.3 20030210 (prerelease) (i386-pc-linux-gnu) libgtkada1-dev version 1.2.12-7 (note that installed libgtkada1-dev version is inconsistent with the version of Gnat, no other package version inconsistencies on my Debian), backstore_area.ad[bs] attached.

Bug#178790: gcc sig11 - no longer reproduced, hardware problem?

2003-02-19 Thread Vassilii Khachaturov
Today (2 reboots down the road), the very same cmdline in the very same place (although untarred again into a different directory) goes flawlessly. I am sorry to not have applied the sig11 FAQ techniques on the spot during the original submission. (I'm talking about http://www.tldp.org/FAQ/sig11/h