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: "bonzini at gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 9 Mar 2004 19:11:20 -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 bonzini at gnu dot org 2004-03-09 19:11 -------
Subject: Re: [3.5 Regression] a-calend.adb:396:33: warning: value not in range of type "Ada.Calendar.Day_Duration"
First, the important part: stage2/gnatbind is miscompiled by the stage1 Ada
compiler. Which of gnatbind's object files (or RTL dumps, even better) are
different? It should be fairly easy to obtain this information by passing an
appropriate -d option to stage2's make gnattools (both in the tree with my
patch, and without).
Now, more on regression hunting.
> Do you mean that the binary regression hunter is not smart enough to
> do that ? How does it work ?
It works temporally, by doing a binary search on the commits. It does not
look at each modified file separately because it does not make sense: if I
commit two changes together, most likely separating them will screw up
everything; and if I commit two independent changes, it is supposed that I do
two CVS commits.
What I meant, is that for example I could not understand if the Ada changes
are related; I would have liked to see which of them caused the warning to
appear instead of a SIGSEGV, to help debugging, but the regression tester
treats your Ada update as an unicum, so it cannot help.
Paolo
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14462