https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68676
--- Comment #6 from Paul Thomas ---
Author: pault
Date: Sat Dec 5 17:10:33 2015
New Revision: 231319
URL: https://gcc.gnu.org/viewcvs?rev=231319=gcc=rev
Log:
2015-12-05 Paul Thomas
PR fortran/68676
*
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68676
Paul Thomas changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68676
--- Comment #5 from paul.richard.thomas at gmail dot com ---
As promised, I am working to fix this. Thanks for your contributions.
Paul
On 4 December 2015 at 10:59, ubizjak at gmail dot com
wrote:
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68676
--- Comment #4 from Uroš Bizjak ---
(In reply to Dominique d'Humieres from comment #1)
> See the thread starting at
> https://gcc.gnu.org/ml/fortran/2015-12/msg00030.html.
>
> Note that I don't see these failures on x86_64-apple-darwin14 (no
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68676
Dominique d'Humieres changed:
What|Removed |Added
Target|alphaev68-linux-gnu |alphaev68-linux-gnu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68676
--- Comment #2 from Steve Kargl ---
On Thu, Dec 03, 2015 at 01:02:02PM +, dominiq at lps dot ens.fr wrote:
> --- Comment #1 from Dominique d'Humieres ---
> See the thread starting at
> https://gcc.gnu.org/ml/fortran/2015-12/msg00030.html.
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68676
--- Comment #3 from Uroš Bizjak ---
(In reply to Steve Kargl from comment #2)
> Note, I see the problem on i386-*-freebsd, and I do not
> see the problem on x86_64-*-freebsd. So, it appears to
> a 32-bit vs 64-bit pointer issue (ie., someone