New gfortran bug
Can somebody submit the following (minor) bug in gfortran 4.6 for me?
I haven't had much luck with Bugzilla.
character(1) c
read(*,*) c
! latest 4.6 doesn't like the following unless broken into separate
lines
if (c=='y') stop; if (c=='Y') stop
end
Al Greynolds
www.ruda-cardinal.com
.
Relevant Pages
- Re: Safe way to remove old kernels (except SMP)
... > It would be good to get a component in bugzilla for the yum scripts, ... > far, no luck. ... I've added this as bug 163606. ... (Fedora) - Re: Safe way to remove old kernels (except SMP)
... >>It would be good to get a component in bugzilla for the yum scripts, ... >>far, no luck. ... > I've added this as bug 163606. ... (Fedora) - Re: Passing module procedures to external procedures -- type issues
... (In fact, I wasn't sure whether the problem was with my code, or with gfortran. ... Had I been sure of a bug in the compiler, I would have gone to bugzilla -- promise!) ... (comp.lang.fortran) - [EXPL] Improper Input Validation in Bugzilla (Exploit)
... Developers can use Bugzilla to keep a commotion list as well ... Text Bug Listing", so we then know file is created. ... * Can edit all aspects of any bug. ... sub generate_chart { ... (Securiteam) - Gfortran 2006 Year End Status Report
... Gfortran has achieved many milestones this year and hopefully the ... contributors can continue to move forward with bug fixes, ... to Fortran 95 standard, and the implementation of Fortran 2003 features. ... There were 420 commits to the gfortran front end in 2006. ... (comp.lang.fortran) |
|