public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "domob 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, 28 Jul 2008 18:42:00 -0000	[thread overview]
Message-ID: <20080728184136.26913.qmail@sourceware.org> (raw)
In-Reply-To: <bug-36403-5208@http.gcc.gnu.org/bugzilla/>



------- Comment #4 from domob at gcc dot gnu dot org  2008-07-28 18:41 -------
Thanks for all the hints, Tobias!  I've had a look through the F2003 standard
about intrinsics taking optional char arguments, and it seems as though PACK
and RESHAPE would suffer from the same problem as EOSHIFT does (optional string
argument whose type is not even specified as to be always string), and tests
showed that here too the call to the library function has one less argument
when the optional string argument is not present...  This is probably a problem
there, too, isn't it?

None of those have their own conv_intrinsic_ functions at the moment (for all
of them the if matches, as they all return non-scalar values).  Is it ok if I
try to write one generic conv-function for this case and call it for all the
three intrinsics?


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36403


  parent reply	other threads:[~2008-07-28 18:42 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 ` [Bug fortran/36403] " fxcoudert at gcc dot gnu dot org
2008-06-11 11:13 ` 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 [this message]
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=20080728184136.26913.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: link
Be 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).