public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Giovanni Bajo" <rasky@develer.com>
To: "Ernest L. Williams Jr." <ernesto@ornl.gov>
Cc: <gcc@gcc.gnu.org>
Subject: Re: tree_list not supported by dump_type (Historical Question)
Date: Sat, 04 Dec 2004 15:56:00 -0000	[thread overview]
Message-ID: <0b2501c4da19$d42a8350$f503030a@mimas> (raw)
In-Reply-To: <1102175011.6750.17.camel@lion>

Ernest L. Williams Jr. <ernesto@ornl.gov> wrote:

>> Do you have a testcase?
>
============================================================================
==========
> #include <stdio.h>
>
> int incr(int i){return ++i;}
>
> main()
> {
>   int (*dummy)(...);
>   dummy=incr;
>   (void)printf("%d\n",dummy(1));
>   return(0);
> }
>
============================================================================
=============
>
>
> The above code should yield the error I mention under gcc-2.95

2.95 is five years old and unsupported at this point. With a current GCC
release (3.4.2), I get this:

GNU C++ version 3.4.2 20041017 (Red Hat 3.4.2-6.fc3) (i386-redhat-linux)
        compiled by GNU C version 3.4.2 20041017 (Red Hat 3.4.2-6.fc3).
GGC heuristics: --param ggc-min-expand=33 --param ggc-min-heapsize=6250
bahf.cc:6: warning: ISO C++ forbids declaration of `main' with no type
bahf.cc: In function `int main()':
bahf.cc:8: error: invalid conversion from `int (*)(int)' to `int (*)(...)'

So whatever that patch is, it is not required anymore.
-- 
Giovanni Bajo

      parent reply	other threads:[~2004-12-04 15:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-04 14:13 Ernest L. Williams Jr.
2004-12-04 15:19 ` Giovanni Bajo
     [not found]   ` <1102175011.6750.17.camel@lion>
2004-12-04 15:56     ` Giovanni Bajo [this message]

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='0b2501c4da19$d42a8350$f503030a@mimas' \
    --to=rasky@develer.com \
    --cc=ernesto@ornl.gov \
    --cc=gcc@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).