public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jay dot krell at cornell dot edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/44426]  New: gcc 4.5.0 requires c9x compiler to build
Date: Sat, 05 Jun 2010 14:24:00 -0000	[thread overview]
Message-ID: <bug-44426-16543@http.gcc.gnu.org/bugzilla/> (raw)

Surprising. I'll try 4.4.

cc -c  -g -DIN_GCC    -DHAVE_CONFIG_H -I. -I. -I/home/jayk/src/gcc-4.5.0/gcc
-I/home/jayk/src/gcc-4.5.0/gcc/. -I/home/jayk/src/gcc-4.5.0/gcc/../include
-I/home/jayk/src/gcc-4.5.0/gcc/../libcpp/include -I/home/jayk/include 
-I/home/jayk/src/gcc-4.5.0/gcc/../libdecnumber
-I/home/jayk/src/gcc-4.5.0/gcc/../libdecnumber/dpd -I../libdecnumber    
/home/jayk/src/gcc-4.5.0/gcc/tree-mudflap.c -o tree-mudflap.o
cc: Warning: /home/jayk/src/gcc-4.5.0/gcc/tree.h, line 4943: Formal parameter
isn't an identifier. (badformalparm)
#define build_call_expr(...)\
------------------------^
cc: Warning: /home/jayk/src/gcc-4.5.0/gcc/tree-mudflap.c, line 1262: Too many
actual parameters in macro call. (toomanyactls)
  call_stmt = build_call_expr (mf_register_fndecl, 4,
-------------------------------^
cc: Warning: /home/jayk/src/gcc-4.5.0/gcc/tree-mudflap.c, line 1324: Too many
actual parameters in macro call. (toomanyactls)
    tree call2_stmt = build_call_expr (mf_init_fndecl, 0);
---------------------------------------^
cc: Warning: /home/jayk/src/gcc-4.5.0/gcc/tree-mudflap.c, line 1332: Too many
actual parameters in macro call. (toomanyactls)
      tree call_stmt = build_call_expr (mf_set_options_fndecl, 1, arg);
----------------------------------------^
cc: Error: /home/jayk/src/gcc-4.5.0/gcc/tree-mudflap.c, line 1262: In this
statement, "__VA_ARGS__" is not declared. (undeclared)
  call_stmt = build_call_expr (mf_register_fndecl, 4,
--------------^
cc: Error: /home/jayk/src/gcc-4.5.0/gcc/tree-mudflap.c, line 1262: In this
statement, "build_call_expr_loc" expects 3 arguments, but 2 are supplied.
(toofewargs)
  call_stmt = build_call_expr (mf_register_fndecl, 4,
--------------^
cc: Error: /home/jayk/src/gcc-4.5.0/gcc/tree-mudflap.c, line 1324: In the
initializer for call2_stmt, "__VA_ARGS__" is not declared. (undeclared)
    tree call2_stmt = build_call_expr (mf_init_fndecl, 0);
----------------------^
cc: Error: /home/jayk/src/gcc-4.5.0/gcc/tree-mudflap.c, line 1324: In the
initializer for call2_stmt, "build_call_expr_loc" expects 3 arguments, but 2
are supplied. (toofewargs)
    tree call2_stmt = build_call_expr (mf_init_fndecl, 0);
----------------------^
cc: Error: /home/jayk/src/gcc-4.5.0/gcc/tree-mudflap.c, line 1332: In the
initializer for call_stmt, "__VA_ARGS__" is not declared. (undeclared)
      tree call_stmt = build_call_expr (mf_set_options_fndecl, 1, arg);
-----------------------^
cc: Error: /home/jayk/src/gcc-4.5.0/gcc/tree-mudflap.c, line 1332: In the
initializer for call_stmt, "build_call_expr_loc" expects 3 arguments, but 2 are
supplied. (toofewargs)
      tree call_stmt = build_call_expr (mf_set_options_fndecl, 1, arg);
-----------------------^
make[3]: *** [tree-mudflap.o] Error 1


#define build_call_expr(...)\
   build_call_expr_loc (UNKNOWN_LOCATION, __VA_ARGS__)


-- 
           Summary: gcc 4.5.0 requires c9x compiler to build
           Product: gcc
           Version: 4.5.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: bootstrap
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: jay dot krell at cornell dot edu


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


             reply	other threads:[~2010-06-05 14:24 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-05 14:24 jay dot krell at cornell dot edu [this message]
2010-06-05 14:54 ` [Bug bootstrap/44426] [4.5/4.6 Regression] " jsm28 at gcc dot gnu dot org
2010-06-05 15:14 ` jay dot krell at cornell dot edu
2010-06-05 15:51 ` manu at gcc dot gnu dot org
2010-06-05 17:37 ` joseph at codesourcery dot com
2010-06-05 17:40 ` [Bug bootstrap/44426] [4.4/4.5/4.6 " jsm28 at gcc dot gnu dot org
2010-06-05 17:52 ` rguenth at gcc dot gnu dot org
2010-06-05 19:05 ` manu at gcc dot gnu dot org
2010-06-05 19:10 ` rguenth at gcc dot gnu dot org
2010-06-05 19:39 ` manu at gcc dot gnu dot org
2010-06-05 21:33 ` joseph at codesourcery dot com
2010-06-14  8:55 ` jakub at gcc dot gnu dot org
2010-06-14 10:20 ` jakub at gcc dot gnu dot org
2010-06-14 15:54 ` jakub at gcc dot gnu dot org
2010-06-14 16:01 ` jakub at gcc dot gnu dot org
2010-06-21 16:27 ` jakub at gcc dot gnu dot org
2010-06-21 17:07 ` jakub at gcc dot gnu dot org
2010-06-21 17:11 ` jakub at gcc dot gnu dot org
2010-06-21 17:20 ` jakub at gcc dot gnu dot 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-44426-16543@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).