[Bug fortran/18428] No preprocessing option -cpp for gfortran

2008-05-29 Thread dfranke at gcc dot gnu dot org
--- Comment #10 from dfranke at gcc dot gnu dot org 2008-05-29 19:12 --- Implemented, but not yet fixed, in trunk. Closing. -- dfranke at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/18428] No preprocessing option -cpp for gfortran

2008-05-25 Thread dfranke at gcc dot gnu dot org
--- Comment #9 from dfranke at gcc dot gnu dot org 2008-05-25 22:38 --- Subject: Bug 18428 Author: dfranke Date: Sun May 25 22:37:41 2008 New Revision: 135882 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=135882 Log: gcc: 2008-05-26 Daniel Franke <[EMAIL PROTECTED]>

[Bug fortran/18428] No preprocessing option -cpp for gfortran

2008-02-10 Thread dfranke at gcc dot gnu dot org
--- Comment #8 from dfranke at gcc dot gnu dot org 2008-02-10 14:35 --- Ancient, but still valid. -- dfranke at gcc dot gnu dot org changed: What|Removed |Added A

[Bug fortran/18428] No preprocessing option -cpp for gfortran

2006-03-07 Thread tom dot browder at fwb dot srs dot com
--- Comment #7 from tom dot browder at fwb dot srs dot com 2006-03-07 20:37 --- (In reply to comment #6) > While I completely agree with you, I don't see a way to do that with the > current framework. On the other hand, when (or if) we switch to cpplib, it How does the current framewo

[Bug fortran/18428] No preprocessing option -cpp for gfortran

2006-02-26 Thread pinskia at gcc dot gnu dot org
-- pinskia at gcc dot gnu dot org changed: What|Removed |Added Severity|normal |enhancement Last reconfirmed|2005-11-24 22:11:22 |2006-02-2

[Bug fortran/18428] No preprocessing option -cpp for gfortran

2005-11-24 Thread fxcoudert at gcc dot gnu dot org
--- Comment #6 from fxcoudert at gcc dot gnu dot org 2005-11-24 22:11 --- (In reply to comment #5) > The -x option in gfortran is not really a good replacement as described > in my comment #2. While I completely agree with you, I don't see a way to do that with the current framework. O

[Bug fortran/18428] No preprocessing option -cpp for gfortran

2005-08-12 Thread c dot lemmen at fz-juelich dot de
--- Additional Comments From c dot lemmen at fz-juelich dot de 2005-08-12 13:22 --- Subject: Re: No preprocessing option -cpp for gfortran pinskia at gcc dot gnu dot org wrote: > --- Additional Comments From pinskia at gcc dot gnu dot org 2005-08-12 > 12:32 --- > (In reply to

[Bug fortran/18428] No preprocessing option -cpp for gfortran

2005-08-12 Thread pinskia at gcc dot gnu dot org
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-08-12 12:32 --- (In reply to comment #3) > Now, testcase.f90 will be preprocessed. This should be reflected in the > documentation (rather than having to dig around the 400 page gcc manual) Why, specs files are not for t

[Bug fortran/18428] No preprocessing option -cpp for gfortran

2005-08-12 Thread c dot lemmen at fz-juelich dot de
--- Additional Comments From c dot lemmen at fz-juelich dot de 2005-08-12 12:29 --- Rather than fiddling with -x f95-cpp-input I found that the best option is to use the gcc specs option to redeclare suffix rules. To enforce preprocessing for files with suffix .f90 create a file overrid

[Bug fortran/18428] No preprocessing option -cpp for gfortran

2005-06-12 Thread c dot lemmen at fz-juelich dot de
--- Additional Comments From c dot lemmen at fz-juelich dot de 2005-06-12 11:36 --- > "gfortran -x f95-cpp-input" works > maybe this should be documented. This is not the same. 1) The -x option states that ALL following input files should be treated as being of type 2) The former

[Bug fortran/18428] No preprocessing option -cpp for gfortran

2004-11-11 Thread pinskia at gcc dot gnu dot org
--- Additional Comments From pinskia at gcc dot gnu dot org 2004-11-11 15:05 --- "gfortran -x f95-cpp-input" works So does "gfortran -x f77-cpp-input" maybe this should be documented. -- What|Removed |Added ---