public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/48337] New: [4.7 regression] options.c doesn't compile on SPARC Date: Tue, 29 Mar 2011 14:38:00 -0000 [thread overview] Message-ID: <bug-48337-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48337 Summary: [4.7 regression] options.c doesn't compile on SPARC Product: gcc Version: 4.7.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: bootstrap AssignedTo: unassigned@gcc.gnu.org ReportedBy: ro@gcc.gnu.org CC: ebotcazou@gcc.gnu.org, jsm28@gcc.gnu.org Host: sparc-sun-solaris2.* Target: sparc-sun-solaris2.* Build: sparc-sun-solaris2.* As already reported by Art Haas on the gcc list, SPARC bootstrap is broken since Joseph's recent sparc option patch: options.c:753:3: error: enum conversion in initialization is invalid in C++ [-Werror=c++-compat] options.c:753:3: error: (near initialization for 'global_options_init.x_sparc_cpu_and_features') [-Werror=c++-compat] options.c:755:3: error: enum conversion in initialization is invalid in C++ [-Werror=c++-compat] options.c:755:3: error: (near initialization for 'global_options_init.x_sparc_cpu') [-Werror=c++-compat] The lines in question are: 0, /* sparc_cpu_and_features */ 0, /* sparc_std_struct_return */ 0, /* sparc_cpu */ Since I could make no sense of the options machinery, I've added options.o-warn = -Wno-error to gcc/Makefile.in as a workaround.
next reply other threads:[~2011-03-29 14:37 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-03-29 14:38 ro at gcc dot gnu.org [this message] 2011-03-29 15:08 ` [Bug bootstrap/48337] " joseph at codesourcery dot com 2011-03-29 15:50 ` ro at CeBiTec dot Uni-Bielefeld.DE 2011-03-29 16:07 ` ro at gcc dot gnu.org 2011-03-30 10:42 ` ro at gcc dot gnu.org 2011-03-30 10:44 ` ro 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-48337-4@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: linkBe 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).