public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Alexandre Oliva <aoliva@redhat.com>
To: Andrew Pinski <pinskia@physics.uc.edu>
Cc: Mark Mitchell <mark@codesourcery.com>,
	Marc Espie <espie@cvs.openbsd.org>,
	tech@openbsd.org, gcc@gcc.gnu.org
Subject: Re: new fails on gcc 3.4, i686-unknown-openbsd3.1
Date: Sat, 28 Dec 2002 15:45:00 -0000	[thread overview]
Message-ID: <orvg1e3tpw.fsf@free.redhat.lsd.ic.unicamp.br> (raw)
In-Reply-To: <ord6nm59b8.fsf@free.redhat.lsd.ic.unicamp.br>

On Dec 28, 2002, Alexandre Oliva <aoliva@redhat.com> wrote:

> Mark, would it be too hard to accept such empty declarations, for the
> sake of backward-compatibility, perhaps emitting a warning for this
> deprecated extension, and make it an error only in a future release?

Doh, I meant to check the sources before hitting send, but my fingers
slipped.  Sorry.  I realize now that we just pedwarn if we're in
pedantic mode (which the testsuite enables).

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer                 aoliva@{redhat.com, gcc.gnu.org}
CS PhD student at IC-Unicamp        oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist                Professional serial bug killer

  parent reply	other threads:[~2002-12-28 18:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200212281205.gBSC5PAn026010@grendel.geop.uc.edu>
2002-12-28 11:03 ` Andrew Pinski
2002-12-28 11:48   ` Marc Espie
2002-12-28 13:49   ` Alexandre Oliva
2002-12-28 13:58     ` Marc Espie
2002-12-28 18:44       ` Alexandre Oliva
2002-12-28 19:06         ` Marc Espie
2002-12-28 15:45     ` Alexandre Oliva [this message]
2002-12-28 18:18     ` Mark Mitchell
2003-01-14 12:05     ` Mark Mitchell

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=orvg1e3tpw.fsf@free.redhat.lsd.ic.unicamp.br \
    --to=aoliva@redhat.com \
    --cc=espie@cvs.openbsd.org \
    --cc=gcc@gcc.gnu.org \
    --cc=mark@codesourcery.com \
    --cc=pinskia@physics.uc.edu \
    --cc=tech@openbsd.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).