public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: dave@hiauly1.hia.nrc.ca To: gcc-gnats@gcc.gnu.org Subject: fortran/6138: Incorrect access of integer*1 variables on PA Date: Tue, 02 Apr 2002 14:06:00 -0000 [thread overview] Message-ID: <20020402220114.26063.qmail@sources.redhat.com> (raw) >Number: 6138 >Category: fortran >Synopsis: Incorrect access of integer*1 variables on PA >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Tue Apr 02 14:06:01 PST 2002 >Closed-Date: >Last-Modified: >Originator: Dave Anglin >Release: gcc 3.1 (prerelease) and gcc 3.2 >Organization: >Environment: hppa-linux, hppa2.0w-hp-hpux11*, hppa1.1-hp-hpux10.20 >Description: Problem noted by examing f90-intrinsic-numeric.f FAIL. The following snippet from the above test shows the problem: j = -9 ja = 9 k = j ka = ja call c_i2(ABS(j),ja,'ABS(integer*2)') call c_i1(ABS(k),ka,'ABS(integer*1)') Incorrect code is generated for "ka" load. ldi 9,%r4 sth %r4,-120(%r30) ldb -117(%r30),%r19 The above assembly code shows the store generated for "ja" and load for "ja". The offset should be -119, not -117. This error is present in the initial rtl: (insn 45 33 34 (set (reg:QI 101) (mem/f:QI (plus:SI (reg/f:SI 90 virtual-stack-vars) (const_int 3 [0x3])) [0 S1 A8])) -1 (nil) (nil)) This occurs at -O1 and above. Looks like the g77 code assumes that the load is from an integer*4 variable rather than an integer*2 variable. >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2002-04-02 22:06 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-04-02 14:06 dave [this message] 2002-04-06 12:16 Toon Moene 2002-04-06 12:26 John David Anglin 2002-04-07 5:06 Toon Moene 2002-04-21 11:17 mmitchel 2002-04-22 12:34 mmitchel
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=20020402220114.26063.qmail@sources.redhat.com \ --to=dave@hiauly1.hia.nrc.ca \ --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: 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).