public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "Thomas dot L dot Clune at nasa dot gov" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/44232] function result with pointer to strided component of argument
Date: Sat, 22 May 2010 01:59:00 -0000	[thread overview]
Message-ID: <20100522015924.17043.qmail@sourceware.org> (raw)
In-Reply-To: <bug-44232-19220@http.gcc.gnu.org/bugzilla/>



------- Comment #10 from Thomas dot L dot Clune at nasa dot gov  2010-05-22 01:59 -------
Subject: Re:  function result with pointer to strided component of argument

To be honest I'm very rusty at building gcc.   (Remember doing it  
almost daily 10-15 years ago, but generally use commercial compilers  
these days.)   Yes - there were some problems with the build, but I  
thought they were not relevant.   I did not uninstall.

Trying to cleanup and start from scratch now.


On May 21, 2010, at 9:34 PM, kargl at gcc dot gnu dot org wrote:

>
>
> ------- Comment #9 from kargl at gcc dot gnu dot org  2010-05-22  
> 01:34 -------
> (In reply to comment #8)
>> Hmm.  I've now built gfortran 4.5.1  20100521 (from the branch) and  
>> still have
>> the same internal compiler error.   Are you certain that the 4.5.1  
>> 20100420
>> version does not have this problem?
>>
>
> Yep.  But, I use FreeBSD instead of Darwin.  You could be seeing
> a target specific problem.  Your code coompiles on i686-*-freebsd
> and x86_64-*-freebsd.
>
> The obvious questions are: did you de-installed the older version?
> Are you using the newer gfortran if the older version is still
> around?
>
> -- 
> steve
>
>
> -- 
>
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44232
>
> ------- You are receiving this mail because: -------
> You reported the bug, or are watching the reporter.

Thomas Clune                                    
Software Integration and Visualization Office
NASA GSFC (610.3)
301-286-4635 (W)        240-266-0400 (F)
<Thomas.L.Clune@nasa.gov>


-- 


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


  parent reply	other threads:[~2010-05-22  1:59 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-21 17:26 [Bug fortran/44232] New: " Thomas dot L dot Clune at nasa dot gov
2010-05-21 18:20 ` [Bug fortran/44232] " kargl at gcc dot gnu dot org
2010-05-21 19:58 ` Thomas dot L dot Clune at nasa dot gov
2010-05-21 20:24 ` jvdelisle at gcc dot gnu dot org
2010-05-21 20:34 ` kargl at gcc dot gnu dot org
2010-05-21 20:49 ` Thomas dot L dot Clune at nasa dot gov
2010-05-21 21:05 ` dominiq at lps dot ens dot fr
2010-05-22  0:45 ` Thomas dot L dot Clune at nasa dot gov
2010-05-22  1:00 ` Thomas dot L dot Clune at nasa dot gov
2010-05-22  1:34 ` kargl at gcc dot gnu dot org
2010-05-22  1:59 ` Thomas dot L dot Clune at nasa dot gov [this message]
2010-05-22 10:04 ` dominiq at lps dot ens dot fr
2010-08-06  9:05 ` fxcoudert at gcc dot gnu dot org
     [not found] <bug-44232-4@http.gcc.gnu.org/bugzilla/>
2010-12-28 17:55 ` dfranke at gcc dot gnu.org
2010-12-29 16:30 ` Thomas.L.Clune at nasa dot gov
2010-12-29 16:38 ` dfranke at gcc dot gnu.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=20100522015924.17043.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).