public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/108937] Intrinsic IBITS(I,POS,LEN) fails when LEN equals to BIT_SIZE(I). Date: Mon, 27 Feb 2023 21:30:44 +0000 [thread overview] Message-ID: <bug-108937-4-UhWmBQYahH@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108937-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108937 --- Comment #8 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Harald Anlauf <anlauf@gcc.gnu.org>: https://gcc.gnu.org/g:6cce953ebec274f1468d5d3a0697cf05bb43b8f6 commit r13-6362-g6cce953ebec274f1468d5d3a0697cf05bb43b8f6 Author: Harald Anlauf <anlauf@gmx.de> Date: Mon Feb 27 21:37:11 2023 +0100 Fortran: fix corner case of IBITS intrinsic [PR108937] gcc/fortran/ChangeLog: PR fortran/108937 * trans-intrinsic.cc (gfc_conv_intrinsic_ibits): Handle corner case LEN argument of IBITS equal to BITSIZE(I). gcc/testsuite/ChangeLog: PR fortran/108937 * gfortran.dg/ibits_2.f90: New test.
next prev parent reply other threads:[~2023-02-27 21:30 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-27 1:43 [Bug libfortran/108937] New: " saitofuyuki at jamstec dot go.jp 2023-02-27 1:44 ` [Bug libfortran/108937] " saitofuyuki at jamstec dot go.jp 2023-02-27 2:26 ` kargl at gcc dot gnu.org 2023-02-27 3:01 ` saitofuyuki at jamstec dot go.jp 2023-02-27 18:14 ` kargl at gcc dot gnu.org 2023-02-27 19:32 ` anlauf at gcc dot gnu.org 2023-02-27 20:21 ` [Bug fortran/108937] " anlauf at gcc dot gnu.org 2023-02-27 20:55 ` anlauf at gcc dot gnu.org 2023-02-27 21:30 ` cvs-commit at gcc dot gnu.org [this message] 2023-02-27 23:07 ` saitofuyuki at jamstec dot go.jp 2023-03-04 19:51 ` cvs-commit at gcc dot gnu.org 2023-03-05 19:35 ` cvs-commit at gcc dot gnu.org 2023-03-05 19:36 ` cvs-commit at gcc dot gnu.org 2023-03-05 19:40 ` anlauf at gcc dot gnu.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=bug-108937-4-UhWmBQYahH@http.gcc.gnu.org/bugzilla/ \ --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).