From: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
To: Bernd Schmidt <bernds@codesourcery.com>, Jie Zhang <jzhang918@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH, bfin] handle BFIN_CPU_UNKNOWN in TARGET_CPU_CPP_BUILTINS
Date: Wed, 08 Apr 2015 20:12:00 -0000 [thread overview]
Message-ID: <CAC1BbcS+3EU0=AeqVsBXtQ5rKOdGYMV9b7SqA1EKxyYX3AXBLg@mail.gmail.com> (raw)
In-Reply-To: <CAC1BbcSviH0u38QbDzvnzq+S14PvJwYRt+39cfsLoffWoSeN8Q@mail.gmail.com>
ping
On 1 April 2015 at 23:34, Bernhard Reutner-Fischer
<rep.dot.nop@gmail.com> wrote:
> Hi,
>
> gcc/c-family/c-cppbuiltin.c
> In file included from ./tm.h:21:0,
> from
> ../../../../../../home/me/src/gcc-5.0.mine/gcc/c-family/c-cppbuiltin.c:23:
> ../../../../../../home/me/src/gcc-5.0.mine/gcc/c-family/c-cppbuiltin.c:
> In function ‘void c_cpp_builtins(cpp_reader*)’:
> ../../../../../../home/me/src/gcc-5.0.mine/gcc/config/bfin/bfin.h:43:14:
> error: enumeration value ‘BFIN_CPU_UNKNOWN’ not handled in switch
> [-Werror=switch]
> switch (bfin_cpu_type) \
> ^
> ../../../../../../home/me/src/gcc-5.0.mine/gcc/c-family/c-cppbuiltin.c:1243:3:
> note: in expansion of macro ‘TARGET_CPU_CPP_BUILTINS’
> TARGET_CPU_CPP_BUILTINS ();
> ^
> cc1plus: all warnings being treated as errors
> make[2]: *** [c-family/c-cppbuiltin.o] Error 1
>
> gcc/ChangeLog:
>
> 2015-04-01 Bernhard Reutner-Fischer <aldot@gcc.gnu.org>
>
> * config/bfin/bfin.h (TARGET_CPU_CPP_BUILTINS): Add BFIN_CPU_UNKNOWN.
next prev parent reply other threads:[~2015-04-08 20:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-01 21:34 Bernhard Reutner-Fischer
2015-04-01 21:37 ` Bernhard Reutner-Fischer
2015-04-02 20:49 ` [PATCH, c6x] handle unk_isa " Bernhard Reutner-Fischer
2015-04-08 20:13 ` Bernhard Reutner-Fischer
2015-04-22 8:12 ` Bernhard Reutner-Fischer
2015-04-08 20:12 ` Bernhard Reutner-Fischer [this message]
2015-04-22 8:11 ` [PATCH, bfin] handle BFIN_CPU_UNKNOWN " Bernhard Reutner-Fischer
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='CAC1BbcS+3EU0=AeqVsBXtQ5rKOdGYMV9b7SqA1EKxyYX3AXBLg@mail.gmail.com' \
--to=rep.dot.nop@gmail.com \
--cc=bernds@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jzhang918@gmail.com \
/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).