public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "billingd at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/16581] New: gfortran F90 bit intrinsics don't work with integer*{1,2,8} Date: Fri, 16 Jul 2004 01:32:00 -0000 [thread overview] Message-ID: <20040716013242.16581.billingd@gcc.gnu.org> (raw) Fortran 90 bit intrinsics don't work with integer*{1,2,8}. I understand this is a know bug. The test case is g77.f-torture/execute/f90-intrinsic-bit.f, which I believe to be standard conforming (as I wrote it). The first few error messages are: In file f90-intrinsic-bit.f:107 call c_i(IBCLR(14,j2),12,'IBCLR(integer,integer*2)') 1 Error: 'pos' argument of 'ibclr' intrinsic at (1) must be of kind 4 In file f90-intrinsic-bit.f:108 call c_i(IBCLR(14,k2),12,'IBCLR(integer,integer*1)') 1 Error: 'pos' argument of 'ibclr' intrinsic at (1) must be of kind 4 In file f90-intrinsic-bit.f:109 call c_i(IBCLR(14,m2),12,'IBCLR(integer,integer*8)') 1 Error: 'pos' argument of 'ibclr' intrinsic at (1) must be of kind 4 In file f90-intrinsic-bit.f:111 call c_i2(IBCLR(j,j2),ja,'IBCLR(integer*2,integer*2)') 1 Error: 'pos' argument of 'ibclr' intrinsic at (1) must be of kind 4 -- Summary: gfortran F90 bit intrinsics don't work with integer*{1,2,8} Product: gcc Version: 3.5.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: billingd at gcc dot gnu dot org CC: gcc-bugs at gcc dot gnu dot org GCC host triplet: i686-pc-cygwin http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16581
next reply other threads:[~2004-07-16 1:32 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-07-16 1:32 billingd at gcc dot gnu dot org [this message] 2004-07-17 3:11 ` [Bug fortran/16581] " pinskia at gcc dot gnu dot org 2004-12-05 21:47 ` sgk at troutmask dot apl dot washington dot edu 2004-12-12 21:09 ` cvs-commit at gcc dot gnu dot org 2004-12-12 21:39 ` pinskia 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=20040716013242.16581.billingd@gcc.gnu.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).