public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Toon Moene <toon@moene.indiv.nluug.nl> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: fortran/6138: Incorrect access of integer*1 variables on PA Date: Sat, 06 Apr 2002 12:16:00 -0000 [thread overview] Message-ID: <20020406201601.1341.qmail@sources.redhat.com> (raw) The following reply was made to PR fortran/6138; it has been noted by GNATS. From: Toon Moene <toon@moene.indiv.nluug.nl> To: dave@hiauly1.hia.nrc.ca Cc: gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org Subject: Re: fortran/6138: Incorrect access of integer*1 variables on PA Date: Sat, 06 Apr 2002 21:26:15 +0200 dave@hiauly1.hia.nrc.ca wrote: > 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)') I've worked on this today, because this test suite entry fails for powerpc-linux too. Unfortunately, after half a day of fiddling, I'm not sure if the reason this fails on HPPA is the same as the reason it fails on POWERPC. On the latter, even the following is incorrect: INTEGER*1 I I = -9 PRINT*,I END which prints 247 ;-) So I thought, this must be a signed/unsigned "char" problem, no ? Well, AFAICS, the PA port is default-signed-char platform, so this analysis doesn't apply. Welllllll, perhaps this means that this afternoon multiplied one problem into two :-( -- Toon Moene - mailto:toon@moene.indiv.nluug.nl - phoneto: +31 346 214290 Saturnushof 14, 3738 XG Maartensdijk, The Netherlands Maintainer, GNU Fortran 77: http://gcc.gnu.org/onlinedocs/g77_news.html Join GNU Fortran 95: http://g95.sourceforge.net/ (under construction)
next reply other threads:[~2002-04-06 20:16 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-04-06 12:16 Toon Moene [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-04-22 12:34 mmitchel 2002-04-21 11:17 mmitchel 2002-04-07 5:06 Toon Moene 2002-04-06 12:26 John David Anglin 2002-04-02 14:06 dave
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=20020406201601.1341.qmail@sources.redhat.com \ --to=toon@moene.indiv.nluug.nl \ --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: 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).