From: Ralf Baechle <ralf@linux-mips.org>
To: Chen Jie <chenj@lemote.com>
Cc: "Maciej W. Rozycki" <macro@linux-mips.org>,
"Linux MIPS Mailing List" <linux-mips@linux-mips.org>,
陈华才 <chenhc@lemote.com>, 王锐 <wangr@lemote.com>
Subject: Re: [PATCH] mips: define _MIPS_ARCH_LOONGSON3A for Loongson3
Date: Mon, 25 Aug 2014 14:12:40 +0200 [thread overview]
Message-ID: <20140825121240.GG27724@linux-mips.org> (raw)
In-Reply-To: <CAGXxSxVqEs5jyckaOG=iX24UeV2P_WgmqV=EBQYycRJ1P9vPgg@mail.gmail.com>
On Wed, Aug 20, 2014 at 07:59:41PM +0800, Chen Jie wrote:
> 2014-08-20 18:53 GMT+08:00 Ralf Baechle <ralf@linux-mips.org>:
> > On Wed, Aug 20, 2014 at 11:14:48AM +0800, chenj wrote:
> >
> >> +cflags-$(CONFIG_CPU_LOONGSON3) += -D_MIPS_ARCH_LOONGSON3A
> >
> > The _MIPS_ARCH_* namespace belongs to GCC. While it seems current GCC
> > does not define this symbol _MIPS_ARCH_LOONGSON3A runs into the danger
> > of causing a conflict when GCC eventually will define the symbol.
> When this symbol will be defined? With option '-march=loongson3a'?
Well, not currently (at least not in my gcc 4.9.0) - but it might. In
fact, I'm wondering why it doesn't. Maciej?
Ralf
next prev parent reply other threads:[~2014-08-25 12:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-20 3:14 [PATCH 1/2] mips: .../swab.h: fix a compiling failure chenj
2014-08-20 3:14 ` [PATCH] mips: define _MIPS_ARCH_LOONGSON3A for Loongson3 chenj
2014-08-20 10:04 ` James Hogan
2014-08-20 10:04 ` James Hogan
2014-08-20 10:53 ` Ralf Baechle
2014-08-20 11:59 ` Chen Jie
2014-08-25 12:12 ` Ralf Baechle [this message]
2014-08-25 19:35 ` Maciej W. Rozycki
2014-08-25 19:41 ` Ralf Baechle
2014-08-26 1:12 ` Chen Jie
2014-08-25 12:07 ` [PATCH 1/2] mips: .../swab.h: fix a compiling failure Ralf Baechle
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=20140825121240.GG27724@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=chenhc@lemote.com \
--cc=chenj@lemote.com \
--cc=linux-mips@linux-mips.org \
--cc=macro@linux-mips.org \
--cc=wangr@lemote.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.