public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/48337] [4.7 regression] options.c doesn't compile on SPARC
Date: Tue, 29 Mar 2011 15:08:00 -0000 [thread overview]
Message-ID: <bug-48337-4-QQOqUuXSYs@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-48337-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48337
--- Comment #1 from joseph at codesourcery dot com <joseph at codesourcery dot com> 2011-03-29 14:51:01 UTC ---
On Tue, 29 Mar 2011, ro at gcc dot gnu.org wrote:
> 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]
Try adding Init(PROCESSOR_V7) to the lines in sparc.opt defining sparc_cpu
and sparc_cpu_and_features. It appears an explicit initializer of 0 for
these enums isn't being accepted even where an implicit 0 from the lack of
initializer (when a variable rather than a field was used) was accepted.
next prev parent reply other threads:[~2011-03-29 14:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-29 14:38 [Bug bootstrap/48337] New: " ro at gcc dot gnu.org
2011-03-29 15:08 ` joseph at codesourcery dot com [this message]
2011-03-29 15:50 ` [Bug bootstrap/48337] " 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-QQOqUuXSYs@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).