public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dave at hiauly1 dot hia dot nrc dot ca" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/14462] [3.5 Regression] a-calend.adb:396:33: warning: value not in range of type "Ada.Calendar.Day_Duration"
Date: Sun, 07 Mar 2004 18:26:00 -0000	[thread overview]
Message-ID: <20040307182652.7180.qmail@sources.redhat.com> (raw)
In-Reply-To: <20040306175828.14462.danglin@gcc.gnu.org>


------- Additional Comments From dave at hiauly1 dot hia dot nrc dot ca  2004-03-07 18:26 -------
Subject: Re:  [3.5 Regression] a-calend.adb:396:33: warning: value not in range of type "Ada.Calendar.Day_Duration"

> The change for pa.c looks fine to me, maybe it was somewhere else.  Also I have to agree with Paolo 
> about the Ada changes as they make it hard to regtest something.

Paolo's patch introduced the gnat1 segv.  Until we find out what's
causing the segv, I don't think we can say whether there is a problem
with the ada change.  We had an almost "identical" problem a few months
ago caused by an optimization problem.

I don't see a problem with the change to pa.c  I think there was some
change in Paolo's patch beyond the introduction of new macros.

I've looked at the segv a bit.  It's caused by a null value being
returned for a pointer.  I don't see any problem with the code.
The problem would appear to be related to the initialization/setting
of the "struct" that holds the pointer.  I don't know where this
is done.

(gdb) bt
#0  0x001737c0 in system__soft_links__get_sec_stack_addr_nt ()
    at ../../gcc/gcc/ada/s-soflin.adb:232
#1  0x00174500 in system__secondary_stack__ss_mark ()
    at ../../gcc/gcc/ada/s-secsta.adb:462
#2  0x0025dc2c in _ada_gnat1drv () at ../../gcc/gcc/ada/gnat1drv.ads:33
#3  0x004095bc in toplev_main (argc=6065464, argv=0x5c8d38)
    at ../../gcc/gcc/toplev.c:1575

0x001737bc <system__soft_links__get_sec_stack_addr_nt+0>:       addil 25d800,dp,%r1
0x001737c0 <system__soft_links__get_sec_stack_addr_nt+4>:       bv r0(rp)
0x001737c4 <system__soft_links__get_sec_stack_addr_nt+8>:       ldw 57c(,r1),ret0

(gdb) disass 0x001744f4 0x00174514
Dump of assembler code from 0x1744f4 to 0x174514:
0x001744f4 <system__secondary_stack__ss_mark+12>:       ldw 488(,r1),r22
0x001744f8 <system__secondary_stack__ss_mark+16>:       b,l 0x147dcc <osint__file_stamp_hash_table__tab__TtableBIPXb+5576>,r31
0x001744fc <system__secondary_stack__ss_mark+20>:       copy r31,rp
0x00174500 <system__secondary_stack__ss_mark+24>:       ldw -54(,sp),rp
0x00174504 <system__secondary_stack__ss_mark+28>:       ldw 0(,ret0),ret0
0x00174508 <system__secondary_stack__ss_mark+32>:       bv r0(rp)
0x0017450c <system__secondary_stack__ss_mark+36>:       ldo -40(sp),sp
0x00174510 <system__secondary_stack__ss_release+0>:     addil 1800,dp,%r1

The segv is at 0x00174504 following the return from
system__soft_links__get_sec_stack_addr_nt.  The call at 0x001744f8
is an indirect call.

Dave


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14462


  parent reply	other threads:[~2004-03-07 18:26 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-06 17:58 [Bug bootstrap/14462] New: " danglin at gcc dot gnu dot org
2004-03-06 18:18 ` [Bug bootstrap/14462] [3.5 Regression] " danglin at gcc dot gnu dot org
2004-03-06 18:29 ` pinskia at gcc dot gnu dot org
2004-03-06 20:30 ` danglin at gcc dot gnu dot org
2004-03-07  5:29 ` danglin at gcc dot gnu dot org
2004-03-07  5:30 ` danglin at gcc dot gnu dot org
2004-03-07  6:48 ` bonzini at gnu dot org
2004-03-07  7:17 ` pinskia at gcc dot gnu dot org
2004-03-07 18:26 ` dave at hiauly1 dot hia dot nrc dot ca [this message]
2004-03-07 22:02 ` bonzini at gnu dot org
2004-03-07 22:39 ` bonzini at gnu dot org
2004-03-08  0:31 ` dave at hiauly1 dot hia dot nrc dot ca
2004-03-08 11:40 ` charlet at act-europe dot fr
2004-03-08 18:21 ` bonzini at gnu dot org
2004-03-08 23:17 ` charlet at act-europe dot fr
2004-03-09  6:12 ` dave at hiauly1 dot hia dot nrc dot ca
2004-03-09 19:11 ` bonzini at gnu dot org
2004-03-09 21:31 ` dave at hiauly1 dot hia dot nrc dot ca
2004-03-11 23:12 ` dave at hiauly1 dot hia dot nrc dot ca
2004-03-11 23:17 ` danglin at gcc dot gnu dot org
2004-03-12  6:37 ` charlet at act-europe dot fr
2004-03-12 15:46 ` dave at hiauly1 dot hia dot nrc dot ca
2004-03-12 15:47 ` danglin at gcc dot gnu dot org
2004-03-13  8:35 ` bonzini at gnu dot org
2004-03-13 12:42 ` charlet at act-europe dot fr
2004-03-13 16:55 ` dave at hiauly1 dot hia dot nrc dot ca
2004-03-13 16:56 ` dave at hiauly1 dot hia dot nrc dot ca
2004-03-14 10:08 ` charlet at act-europe dot fr
2004-04-05 17:03 ` danglin at gcc dot gnu dot org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040307182652.7180.qmail@sources.redhat.com \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).