public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fxcoudert at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/36403] [4.4 Regression] Some fortran tests using eoshift fail on SH Date: Mon, 02 Jun 2008 11:30:00 -0000 [thread overview] Message-ID: <20080602112959.23972.qmail@sourceware.org> (raw) In-Reply-To: <bug-36403-5208@http.gcc.gnu.org/bugzilla/> ------- Comment #1 from fxcoudert at gcc dot gnu dot org 2008-06-02 11:29 ------- It's a front-end issue: as the BOUNDARY character argument is not present, its length is not appended to the argument list as it should. I guess we need to add a gfc_conv_intrinsic_eoshift function in trans-intrinsic.c to take care of EOSHIFT. -- fxcoudert at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|unassigned at gcc dot gnu |fxcoudert at gcc dot gnu dot |dot org |org Status|UNCONFIRMED |ASSIGNED Ever Confirmed|0 |1 Last reconfirmed|0000-00-00 00:00:00 |2008-06-02 11:29:59 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36403
next prev parent reply other threads:[~2008-06-02 11:30 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-05-31 23:41 [Bug fortran/36403] New: " kkojima at gcc dot gnu dot org 2008-06-02 11:30 ` fxcoudert at gcc dot gnu dot org [this message] 2008-06-11 11:13 ` [Bug fortran/36403] " jsm28 at gcc dot gnu dot org 2008-06-15 15:14 ` fxcoudert at gcc dot gnu dot org 2008-07-18 16:51 ` rguenth at gcc dot gnu dot org 2008-07-24 17:04 ` domob at gcc dot gnu dot org 2008-07-27 13:52 ` burnus at gcc dot gnu dot org 2008-07-28 18:42 ` domob at gcc dot gnu dot org 2008-07-28 18:42 ` domob at gcc dot gnu dot org 2008-07-28 20:04 ` burnus at gcc dot gnu dot org 2008-07-29 9:13 ` domob at gcc dot gnu dot org 2008-07-29 9:18 ` domob 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=20080602112959.23972.qmail@sourceware.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).