public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug fortran/29671] preprocessor statements must start in column 1
       [not found] <bug-29671-4@http.gcc.gnu.org/bugzilla/>
@ 2012-03-03 14:38 ` fxcoudert at gcc dot gnu.org
  0 siblings, 0 replies; 3+ messages in thread
From: fxcoudert at gcc dot gnu.org @ 2012-03-03 14:38 UTC (permalink / raw)
  To: gcc-bugs

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

Francois-Xavier Coudert <fxcoudert at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |fxcoudert at gcc dot
                   |                            |gnu.org
         Resolution|                            |DUPLICATE

--- Comment #3 from Francois-Xavier Coudert <fxcoudert at gcc dot gnu.org> 2012-03-03 14:36:27 UTC ---
Fixed as duplicate of PR28662, as both have the same root cause.

*** This bug has been marked as a duplicate of bug 28662 ***


^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug fortran/29671] preprocessor statements must start in column 1
  2006-10-31 11:42 [Bug fortran/29671] New: " franke dot daniel at gmail dot com
  2006-10-31 12:48 ` [Bug fortran/29671] " burnus at gcc dot gnu dot org
@ 2006-10-31 13:02 ` burnus at gcc dot gnu dot org
  1 sibling, 0 replies; 3+ messages in thread
From: burnus at gcc dot gnu dot org @ 2006-10-31 13:02 UTC (permalink / raw)
  To: gcc-bugs



------- Comment #2 from burnus at gcc dot gnu dot org  2006-10-31 13:02 -------
Confirm and mark as enhancement.


-- 

burnus at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|normal                      |enhancement
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|0                           |1
   Last reconfirmed|0000-00-00 00:00:00         |2006-10-31 13:02:35
               date|                            |


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


^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug fortran/29671] preprocessor statements must start in column 1
  2006-10-31 11:42 [Bug fortran/29671] New: " franke dot daniel at gmail dot com
@ 2006-10-31 12:48 ` burnus at gcc dot gnu dot org
  2006-10-31 13:02 ` burnus at gcc dot gnu dot org
  1 sibling, 0 replies; 3+ messages in thread
From: burnus at gcc dot gnu dot org @ 2006-10-31 12:48 UTC (permalink / raw)
  To: gcc-bugs



------- Comment #1 from burnus at gcc dot gnu dot org  2006-10-31 12:48 -------
The problem is that gfortran calls "cpp" with the -traditional-cpp option.

This causes some more modern constructs not to work and it also is the reason
behind your problem. (cf. PR 28662).

We need to use -traditional-cpp since "some tokens in C are not
tokens in Fortran so you could get the wrong result." (A.P. in the other PR)

The solution is to modify cpp to know fortran tokens (when called with
-lang-fortran).

Note this problem is not limited to gfortran; e.g. the NAG f95 compiler uses
Sun's public-domain fpp (netlib.org/fortran/), which has similar problems.


-- 


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


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2012-03-03 14:38 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <bug-29671-4@http.gcc.gnu.org/bugzilla/>
2012-03-03 14:38 ` [Bug fortran/29671] preprocessor statements must start in column 1 fxcoudert at gcc dot gnu.org
2006-10-31 11:42 [Bug fortran/29671] New: " franke dot daniel at gmail dot com
2006-10-31 12:48 ` [Bug fortran/29671] " burnus at gcc dot gnu dot org
2006-10-31 13:02 ` burnus at gcc dot gnu dot org

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).