public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Steve Kargl <sgk@troutmask.apl.washington.edu>
To: Thomas Koenig <tkoenig@netcologne.de>
Cc: fortran@gcc.gnu.org, kargl@gcc.gnu.org
Subject: Re: co-arrays and libgfortran
Date: Tue, 22 Dec 2020 15:24:27 -0800	[thread overview]
Message-ID: <20201222232427.GA61259@troutmask.apl.washington.edu> (raw)
In-Reply-To: <20201222014001.GA13574@troutmask.apl.washington.edu>

On Mon, Dec 21, 2020 at 05:40:01PM -0800, Steve Kargl wrote:
> On Mon, Dec 21, 2020 at 04:18:43PM -0800, Steve Kargl wrote:
> > On Tue, Dec 22, 2020 at 12:44:29AM +0100, Thomas Koenig wrote:
> > > 
> > > > That URL appears to take me to the coarray_native branch.  If I click
> > > > on the 'clone' link, I seehttps://github.com/gcc-mirror/gcc.git.
> > > > Is that for a complete gcc repository or specific to your branch?
> > > > IOW, if I clone from that URL, do I need to do any git voodoo
> > > > magic incantation to get to the branch?
> > > 
> > > Actually, I tried this via svn from github. Not the normal way of
> > > accessing it, but if you're more familiar with svn, it chould work for
> > > you.
> > > 
> > > What I did was
> > > 
> > > $ svn co --depth empty https://github.com/gcc-mirror/gcc.git Gcc
> > > $ cd Gcc
> > > $ svn up trunk
> > > $ cd trunk
> > > $ svn switch
> > > https://github.com/gcc-mirror/gcc.git/branches/devel/coarray_native
> > > 
> > 
> > Thanks.  Downloading now.  It'll take a day to bootstrap on my
> > old i386-*-freebsd system.
> > 
> 
> It appears the above worked.   Last questions.  Any special
> --enable-XXX options you want me to test?  What's the 
> checking target 'make check-shared'?
> 

Just finished bootstrap on x86_64-*-freebsd.

% gmake -j7 check-fortran

                === gfortran Summary ===

# of expected passes            54886
# of unexpected failures        3
# of expected failures          193
# of unsupported tests          110


% gmake check-fortran RUNTESTFLAGS="cas.exp=\*.f\*"
                === gfortran Summary ===

# of expected passes            65
# of unsupported tests          2
objs/gcc/gfortran  version 11.0.0 20201025 (experimental) (GCC) 


So, the issue I've reported else thread is likely a
32-bit vs 64-bit OS issue.  Perhaps, a size_t or
ssize_t issue?

% cat a.c
#include <stdio.h>
int
main(void)
{
   printf("%d\n", sizeof(size_t));
   printf("%d\n", sizeof(ssize_t));
   return 0;
}

On i386-*-freebsd
% cc -o z a.c
% ./z
4
4

On x86_64-*-freebsd
%  cc -o z a.c
% ./z
8
8


-- 
Steve

  parent reply	other threads:[~2020-12-22 23:24 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-18  4:28 Steve Kargl
2020-12-18 12:26 ` Thomas Koenig
2020-12-18 15:52   ` Steve Kargl
2020-12-19 21:59     ` Steve Kargl
2020-12-20 10:52       ` Thomas Koenig
2020-12-20 17:47         ` Steve Kargl
2020-12-21  1:04           ` Steve Kargl
2020-12-21  2:01             ` Damian Rouson
2020-12-21 13:15     ` Thomas Koenig
2020-12-21 15:18       ` Steve Kargl
2020-12-21 23:44         ` Thomas Koenig
2020-12-22  0:18           ` Steve Kargl
2020-12-22  1:40             ` Steve Kargl
2020-12-22 10:04               ` Thomas Koenig
2020-12-22 18:32                 ` Steve Kargl
2020-12-22 19:33                   ` Steve Kargl
2020-12-22 20:12                     ` Steve Kargl
2020-12-22 20:20                       ` Steve Kargl
2020-12-22 22:08                         ` Steve Kargl
2020-12-22 22:22                           ` Steve Kargl
2020-12-22 23:24               ` Steve Kargl [this message]
2020-12-22 23:46                 ` Thomas Koenig

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=20201222232427.GA61259@troutmask.apl.washington.edu \
    --to=sgk@troutmask.apl.washington.edu \
    --cc=fortran@gcc.gnu.org \
    --cc=kargl@gcc.gnu.org \
    --cc=tkoenig@netcologne.de \
    /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).