public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Rainer Orth <ro@TechFak.Uni-Bielefeld.DE>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: Re: target/2273: [Alpha/Tru64 UNIX V5.1] SEGV in long double code
Date: Tue, 03 Apr 2001 10:16:00 -0000	[thread overview]
Message-ID: <20010403171605.32299.qmail@sourceware.cygnus.com> (raw)

The following reply was made to PR target/2273; it has been noted by GNATS.

From: Rainer Orth <ro@TechFak.Uni-Bielefeld.DE>
To: gcc-gnats@gcc.gnu.org
Cc: gcc-bugs@gcc.gnu.org, Richard Henderson <rth@redhat.com>
Subject: Re: target/2273: [Alpha/Tru64 UNIX V5.1] SEGV in long double code
Date: Tue, 3 Apr 2001 19:09:23 +0200 (MEST)

 I've single-stepped the test program and found the exact location where it
 SEGVs:
 
 int
 main (void)
 {
   long double ld = 1.0;
 }
 
 Here's an excerpt from the resulting assembler code:
 
 	.rdata
 	.quad 0
 	.align 4
 $LC0:
 	.quad 0x000000000,0x3fff000000000000
 
 and here's the relevant code for the assignment to ld, just after the
 function prologue:
 
 	lda $1,$LC0	; load address of ld into $1
 	ldq $1,0($1)	; store high quad of ld into $1, overwriting &ld!
 	ldq $2,8($1)	; the first quad of 1.0 happens to be 0, so 8($1)
 			; dereferences a NULL pointer and SEGVs
 
 Unfortunately, I cannot yet read the RTL dumps to understand why this is
 happening.
 
 	Rainer
 
 -----------------------------------------------------------------------------
 Rainer Orth, Faculty of Technology, Bielefeld University
 
 Email: ro@TechFak.Uni-Bielefeld.DE
 


             reply	other threads:[~2001-04-03 10:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-03 10:16 Rainer Orth [this message]
2002-03-29  0:33 rth

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=20010403171605.32299.qmail@sourceware.cygnus.com \
    --to=ro@techfak.uni-bielefeld.de \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).