public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: mnmoran@bellsouth.net
To: gcc-gnats@gcc.gnu.org
Subject: target/10205: Incorrect code generated for H8300 "normal" mode
Date: Tue, 25 Mar 2003 05:46:00 -0000	[thread overview]
Message-ID: <20030325052620.28376.qmail@sources.redhat.com> (raw)


>Number:         10205
>Category:       target
>Synopsis:       Incorrect code generated for H8300 "normal" mode
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Mar 25 05:36:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     Mike Moran
>Release:        gcc-20030324 snapshot
>Organization:
>Environment:
Linux glass 2.2.18-4hpmac #1 Thu Dec 21 15:16:15 MST 2000 ppc unknown
$ gcc -v
Reading specs from /usr/lib/gcc-lib/ppc-redhat-linux/2.95.3/specs
gcc version 2.95.3 20001130 (prerelease/franzo/20001204)
>Description:
       subs  #0x4,er7    --- reserve space for object
       mov.l er4,@-er7   --- save non-volatile register
       mov.w r7,r4       --- copy of SP/FP
       adds  #0x2,er4    --- BUG! should add 4 to SP/FP
       mov.w #0x0,r2
       mov.w r2,@er4     --- Overwrites saved non-volatile

I tried the snapshot since the same type of problem
in GCC-3.2.1
>How-To-Repeat:
../gcc-20030324/configure --prefix=/tools/gnu/h8300-elf --target=h8300-elf --enable-languages=c c++ --with-newlib

h8300-elf-gcc -c -fno-builtin -mn -mh -fomit-frame-pointer -fno-exceptions -O2 testcase.cpp

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="testcase.cpp"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="testcase.cpp"

CmNsYXNzIEIgewoJcHVibGljOgoJCXZpcnR1YWwgdm9pZAl4KCkgdGhyb3coKT0wOwoJCXZpcnR1
YWwgdm9pZAl5KCkgdGhyb3coKT0wOwoJfTsKCmNsYXNzIE1YIDogcHVibGljIEIgewoJdW5zaWdu
ZWQgY2hhcglfc2F2ZTsKCXB1YmxpYzoKCQl2b2lkIHgoKSB0aHJvdygpOwoJCXZvaWQgeSgpIHRo
cm93KCk7Cgl9OwoKY2xhc3MgREEgewoJcHVibGljOgoJCXZpcnR1YWwgdm9pZAl0KCkgdGhyb3co
KT0wOwoJfTsKCmNsYXNzIEQgOiBwdWJsaWMgREEgewoJcHVibGljOgoJCXZvaWQJdCgpIHRocm93
KCk7Cgl9OwoKZXh0ZXJuIHZvaWQgeihCICZhLEIgJmIpOwovL2V4dGVybiB2b2lkIHooTVggJmEs
TVggJmIpOwoKdm9pZCBEOjp0KCkgdGhyb3coKXsKCU1YCW14OwoJbXgueCgpOwoJeihteCxteCk7
CglteC55KCk7Cgl9Cgo=


             reply	other threads:[~2003-03-25  5:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-25  5:46 mnmoran [this message]
2003-03-27 13:12 kazu
2003-03-27 20:12 kazu
2003-03-28  7:56 Dhananjay R. Deshpande
2003-03-28 15:07 Kazu Hirata
2003-03-28 15:26 kazu
2003-03-28 16:56 Kazu Hirata

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=20030325052620.28376.qmail@sources.redhat.com \
    --to=mnmoran@bellsouth.net \
    --cc=gcc-gnats@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).