This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug bootstrap/14462] [3.5 Regression] a-calend.adb:396:33: warning: value not in range of type "Ada.Calendar.Day_Duration"
- From: "charlet at act-europe dot fr" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 8 Mar 2004 11:40:37 -0000
- Subject: [Bug bootstrap/14462] [3.5 Regression] a-calend.adb:396:33: warning: value not in range of type "Ada.Calendar.Day_Duration"
- References: <20040306175828.14462.danglin@gcc.gnu.org>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From charlet at act-europe dot fr 2004-03-08 11:40 -------
Subject: Re: [3.5 Regression] a-calend.adb:396:33: warning: value not in range of type "Ada.Calendar.Day_Duration"
> Does it look like miscompilation?
Yes, it does. Clearly this warning should never be generated in 'normal'
conditions by the front-end, and does not on other platforms (this is a
platform independent warning), so the only explanation AFAICS is a
miscompilation.
Also, all Ada changes, including recent ones, are thorougly tested on
several configurations (about 12) using various test suites before being
submitted, so they are always pretty safe (certainly safer than most
other changes which are only tested on one or two platforms typically).
As for committing Ada changes individually, I do not understand why this would
make a difference to you, since each change comes with a separate, complete
entry in the changelog, so could you explain how it would help you to
have the commits performed separately ? Why would it encourage you to
enable Ada and look at Ada failures more than you do now ?
Arno
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14462