public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "danglin at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ada/20754] ACATS cxg1005 fails at runtime on hppa-linux Date: Thu, 05 Jan 2006 02:53:00 -0000 [thread overview] Message-ID: <20060105025352.5244.qmail@sourceware.org> (raw) In-Reply-To: <bug-20754-7210@http.gcc.gnu.org/bugzilla/> ------- Comment #7 from danglin at gcc dot gnu dot org 2006-01-05 02:53 ------- The bug is as follows. The return from the call to cxg1005__test_block__complex_pack__compose_from_cartesian___389 is in registers ret0 and ret1. bl cxg1005__test_block__complex_pack__compose_from_cartesian___389,%r2 fcpy,sgl %fr12L,%fr4L stw %r28,-16(%r30) fldws -16(%r30),%fr19L copy %r0,%r19 copy %r0,%r20 .loc 4 88 0 fcpy,sgl %fr13L,%fr4L stw %r19,-496(%r30) stw %r20,-492(%r30) stw %r19,-488(%r30) stw %r20,-484(%r30) .loc 4 87 0 .loc 4 88 0 bl cxg1005__test_block__complex_pack__compose_from_cartesian__3___395,%r 2 stw %r29,-16(%r30) .loc 4 87 0 fldws -16(%r30),%fr21L Prior to the call to cxg1005__test_block__complex_pack__compose_from_cartesian__3___395, the return value in ret1 is saved in the frame marker at -16(%r30). The function cxg1005__test_block__complex_pack__compose_from_cartesian__3___395 is a leaf function and doesn't allocate a frame. It does a similar register interchange clobbering the old value at -16(%r30). .type cxg1005__test_block__complex_pack__compose_from_cartesian__3___3 95, @function .LFB50: .loc 1 474 0 cxg1005__test_block__complex_pack__compose_from_cartesian__3___395: .PROC .CALLINFO FRAME=0,NO_CALLS .ENTRY .LVL3: .LVL4: .loc 1 477 0 fstws %fr4L,-16(%r30) copy %r0,%r28 bv %r0(%r2) ldw -16(%r30),%r29 .EXIT .PROCEND -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20754
next prev parent reply other threads:[~2006-01-05 2:53 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-20754-7210@http.gcc.gnu.org/bugzilla/> 2006-01-03 19:44 ` laurent at guerby dot net 2006-01-03 20:27 ` danglin at gcc dot gnu dot org 2006-01-03 20:29 ` danglin at gcc dot gnu dot org 2006-01-03 21:19 ` laurent at guerby dot net 2006-01-04 2:41 ` dave at hiauly1 dot hia dot nrc dot ca 2006-01-04 11:48 ` laurent at guerby dot net 2006-01-05 2:53 ` danglin at gcc dot gnu dot org [this message] 2006-01-05 8:07 ` laurent at guerby dot net 2006-01-07 18:37 ` [Bug target/20754] " danglin at gcc dot gnu dot org 2006-01-11 0:07 ` danglin at gcc dot gnu dot org 2006-01-11 0:28 ` danglin at gcc dot gnu dot org 2006-01-11 0:44 ` danglin at gcc dot gnu dot org 2006-01-18 16:34 ` danglin at gcc dot gnu dot org 2006-01-23 16:33 ` pinskia at gcc dot gnu dot org 2005-04-04 19:20 [Bug ada/20754] New: " laurent at guerby dot net 2005-04-05 1:59 ` [Bug ada/20754] " 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=20060105025352.5244.qmail@sourceware.org \ --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: linkBe 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).