public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "manu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/65387] [4.8/4.9/5 Regression] cpp -C emits extraneous comment header on every file
Date: Wed, 11 Mar 2015 15:52:00 -0000	[thread overview]
Message-ID: <bug-65387-4-G3iMksMeA0@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65387-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65387

Manuel López-Ibáñez <manu at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |manu at gcc dot gnu.org

--- Comment #3 from Manuel López-Ibáñez <manu at gcc dot gnu.org> ---
https://gcc.gnu.org/gcc-4.8/porting_to.html suggests to use -ffreestanding

Of course, the real fix for this and future issues arising from such mis-use is
to make libcpp more general and enable cpp to have a "Fortran mode" (-x
fortran) or even compile a Fortran version of cpp (fpp?). This would be a very
valuable contribution to GCC and gfortran and, technically, it should be not
very difficult:

https://gcc.gnu.org/wiki/GettingStarted#Basics:_Contributing_to_GCC_in_10_easy_steps
>From gcc-bugs-return-480086-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Mar 11 15:57:06 2015
Return-Path: <gcc-bugs-return-480086-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 24924 invoked by alias); 11 Mar 2015 15:57:06 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 24856 invoked by uid 48); 11 Mar 2015 15:57:02 -0000
From: "doko at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/65384] Intel MPX does not support x32
Date: Wed, 11 Mar 2015 15:57:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: other
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: doko at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: enkovich.gnu at gmail dot com
X-Bugzilla-Target-Milestone: 5.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-65384-4-F4hF4iYZYo@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-65384-4@http.gcc.gnu.org/bugzilla/>
References: <bug-65384-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-03/txt/msg01230.txt.bz2
Content-length: 191

https://gcc.gnu.org/bugzilla/show_bug.cgi?ide384

--- Comment #1 from Matthias Klose <doko at gcc dot gnu.org> ---
patch posted at
https://gcc.gnu.org/ml/gcc-patches/2015-03/msg00627.html


  parent reply	other threads:[~2015-03-11 15:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-11  9:53 [Bug preprocessor/65387] New: " bugs at stellardeath dot org
2015-03-11 10:00 ` [Bug preprocessor/65387] [4.8/4.9/5 Regression] " rguenth at gcc dot gnu.org
2015-03-11 10:03 ` rguenth at gcc dot gnu.org
2015-03-11 15:52 ` manu at gcc dot gnu.org [this message]
2015-03-11 17:11 ` jakub 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=bug-65387-4-G3iMksMeA0@http.gcc.gnu.org/bugzilla/ \
    --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).