public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "paulthomas2 at wanadoo dot fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/18857] MATMUL failing with ALLOCATED matrices, unless base indices given
Date: Fri, 29 Apr 2005 14:59:00 -0000 [thread overview]
Message-ID: <20050429145929.11329.qmail@sourceware.org> (raw)
In-Reply-To: <20041206185831.18857.paulthomas2@wanadoo.fr>
------- Additional Comments From paulthomas2 at wanadoo dot fr 2005-04-29 14:59 -------
Subject: Re: MATMUL failing with ALLOCATED matrices, unless base indices given
Tobi,
> The library uses the latter way, so the offset is not needed there.
>
Exactly - I was aware of this because the namelist functions do not use
base/offset at all.
> BTW this also answers the question of ssize_t vs size_t we were dicussing
> before: correct overflow only plays a role when one uses the first way,
> and this
> is only used in compiler-generated code.
Yes, that is the point that Thomas was making, when he raised it in the
first place.
>
> The library only uses the latter kind of indexing and therefore using
> ssize_t
> should work correctly under all circumstances.
Again, exactly.
As for the care that I am taking - after the business with namelist, I feel
like the monkey and the billiard ball- I'll see if I can find it on the web.
You will see why it is appropriate.
Paul
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18857
next prev parent reply other threads:[~2005-04-29 14:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-06 18:58 [Bug libfortran/18857] New: " paulthomas2 at wanadoo dot fr
2004-12-06 21:29 ` [Bug libfortran/18857] " pinskia at gcc dot gnu dot org
2004-12-08 23:44 ` tobi at gcc dot gnu dot org
2005-04-19 18:51 ` [Bug fortran/18857] " tkoenig at gcc dot gnu dot org
2005-04-25 14:13 ` tobi at gcc dot gnu dot org
2005-04-25 15:35 ` paulthomas2 at wanadoo dot fr
2005-04-25 20:31 ` paulthomas2 at wanadoo dot fr
2005-04-25 20:47 ` Tobias dot Schlueter at physik dot uni-muenchen dot de
2005-04-26 12:56 ` paulthomas2 at wanadoo dot fr
2005-04-29 9:52 ` [Bug libfortran/18857] " paulthomas2 at wanadoo dot fr
2005-04-29 10:29 ` tobi at gcc dot gnu dot org
2005-04-29 14:59 ` paulthomas2 at wanadoo dot fr [this message]
2005-04-29 16:34 ` Tobias dot Schlueter at physik dot uni-muenchen dot de
2005-05-24 21:59 ` [Bug libfortran/18857] [4.0 only] " tkoenig at gcc dot gnu dot org
2005-07-08 1:37 ` mmitchel at gcc dot gnu dot org
2005-07-15 20:48 ` cvs-commit at gcc dot gnu dot org
2005-07-15 20:50 ` tkoenig at gcc dot gnu dot org
2005-07-15 20:50 ` tkoenig 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=20050429145929.11329.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).