public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Toon Moene <toon@moene.indiv.nluug.nl>
To: "Maciej Z. Pindera" <mzp@HiWAAY.net>
Cc: rth@cygnus.com, gcc@gcc.gnu.org
Subject: Re: fortran and c pointers in gcc 2.95.2
Date: Wed, 13 Sep 2000 12:40:00 -0000	[thread overview]
Message-ID: <39BFD1F3.301EF336@moene.indiv.nluug.nl> (raw)
In-Reply-To: <39BF1507.3AC88694@HiWAAY.net>

Maciej Z. Pindera wrote:

> I wrote:

[ Please show us the source, so that we can say something intelligent
  about your problem  ... ]

> Oops.  It was very late at night, and it wasn't my code.  While I'm aware
> that fortran does not use pointers and passes arguments by reference, I
> thought that this particular code used LOC (or similar) intrinsics that
> return INTEGER*8 pointer-like constructs on DEC_Alphas.  In the event it
> turned out that the code did not do this; the error was not compiler but code
> generated.

Ha !  This shows exactly why it is important to sent an example code
that behaves problematic in the way mentioned:  I didn't even recall the
ancient LOC-on-64-bit-target problems anymore ...

Cheers,

-- 
Toon Moene - mailto:toon@moene.indiv.nluug.nl - phoneto: +31 346 214290
Saturnushof 14, 3738 XG  Maartensdijk, The Netherlands
GNU Fortran 77: http://gcc.gnu.org/onlinedocs/g77_news.html
GNU Fortran 95: http://g95.sourceforge.net/ (under construction)

      reply	other threads:[~2000-09-13 12:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-10  1:42 Maciej Z. Pindera
2000-09-10 11:53 ` Toon Moene
2000-09-12 22:48   ` Maciej Z. Pindera
2000-09-13 12:40     ` Toon Moene [this message]

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=39BFD1F3.301EF336@moene.indiv.nluug.nl \
    --to=toon@moene.indiv.nluug.nl \
    --cc=gcc@gcc.gnu.org \
    --cc=mzp@HiWAAY.net \
    --cc=rth@cygnus.com \
    /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).