public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Andrew Pinski" <pinskia@gmail.com>
To: "Ismail Dönmez" <ismail@pardus.org.tr>
Cc: gcc@gcc.gnu.org
Subject: Re: Changes in C++ FE regarding pedwarns to be errors are harmful
Date: Tue, 08 Jan 2008 22:45:00 -0000	[thread overview]
Message-ID: <de8d50360801081444n67e45c83v6c108168a915f049@mail.gmail.com> (raw)
In-Reply-To: <200801090037.31205.ismail@pardus.org.tr>

On 1/8/08, Ismail Dönmez <ismail@pardus.org.tr> wrote:
> Oh that clears up my confusion. So the right fix would be downgrading this
> redefinition problem to be pedwarn instead. But I see no point in creating a
> bug report if its just gonna be closed as invalid, so I hope we can discuss
> if its feasible to downgrade this error to be a pedwarn.

It is already a pedwarn.  Just the C++ front-end enables pedwarn as
being errors by default and downgrades them as being warnings with
-fpermissive.  This is the whole point of -fpermissive.

Thanks,
Andrew Pinski

  reply	other threads:[~2008-01-08 22:45 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-08 21:27 Ismail Dönmez
2008-01-08 21:34 ` Joe Buck
2008-01-08 21:43   ` Richard Guenther
2008-01-08 21:44   ` Ismail Dönmez
2008-01-08 22:13     ` Andrew Pinski
2008-01-08 22:29     ` Manuel López-Ibáñez
2008-01-08 22:36       ` Ismail Dönmez
2008-01-08 22:45         ` Andrew Pinski [this message]
2008-01-09 14:10           ` Paolo Bonzini
2008-01-09 15:38             ` Manuel López-Ibáñez
2008-01-09 15:57               ` Paolo Bonzini
2008-01-08 22:51         ` Manuel López-Ibáñez
2008-01-08 23:02           ` Ismail Dönmez
2008-01-09  1:23       ` Ismail Dönmez
2008-01-09  2:25         ` Manuel López-Ibáñez
2008-01-09 16:47           ` Ian Lance Taylor
2008-01-09 18:11             ` Benjamin Kosnik
2008-01-09 18:18               ` Andrew Pinski
2008-01-09 18:21                 ` Paolo Carlini
2008-01-09 19:42             ` Mark Mitchell
2008-01-11 17:06               ` Jason Merrill
2008-01-11 17:12                 ` Joe Buck
2008-01-11 17:55                   ` Mark Mitchell
2008-01-12 19:07                     ` Jonathan Wakely
2008-01-12 19:50                       ` Manuel López-Ibáñez
2008-01-13  3:28                         ` Jonathan Wakely
2008-01-13 15:30                           ` Manuel López-Ibáñez
2008-01-13 22:56                             ` Jonathan Wakely
2008-01-14  2:04                               ` Jonathan Wakely
2008-01-14  2:19                                 ` Manuel López-Ibáñez
2008-01-13 15:33         ` Gabriel Dos Reis
2008-01-13 15:36           ` Ismail Dönmez
2008-01-13 16:09             ` Andreas Schwab
2008-01-13 16:10               ` Ismail Dönmez
2008-01-13 16:13                 ` Richard Guenther
2008-01-13 16:41                   ` Ismail Dönmez
2008-01-13 23:08                     ` Manuel López-Ibáñez
2008-01-14 11:03                 ` Paolo Bonzini
2008-01-14 16:23                   ` Ismail Dönmez
2008-01-13 16:43             ` Gabriel Dos Reis
2008-01-13 16:45               ` Ismail Dönmez
2008-01-13 19:17                 ` Gabriel Dos Reis

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=de8d50360801081444n67e45c83v6c108168a915f049@mail.gmail.com \
    --to=pinskia@gmail.com \
    --cc=gcc@gcc.gnu.org \
    --cc=ismail@pardus.org.tr \
    /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).