public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Xi Ruoyao <xry111@mengyan1223.wang>
To: chenglulu <chenglulu@loongson.cn>, gcc-patches@gcc.gnu.org
Cc: yangyujie@loongson.cn, xuchenghua@loongson.cn
Subject: Re: [PATCH 01/12] LoongArch Port: gcc build
Date: Sun, 28 Nov 2021 08:51:12 +0800	[thread overview]
Message-ID: <25a89acf318adfc42a0d8af0eb9ecb6fb062b20a.camel@mengyan1223.wang> (raw)
In-Reply-To: <20211127082735.4139682-2-chenglulu@loongson.cn>

On Sat, 2021-11-27 at 16:27 +0800, chenglulu wrote:

> +++ b/gcc/config/loongarch/loongarch-opts.h

/* snip */

> +#ifdef IN_LIBGCC2
> +#include "loongarch-def.h"
> +#else
> +extern "C" {
> +#include "loongarch-def.h"
> +}
> +
> +/* Handler for "-m" option combinations,
> +   shared by the driver and the compiler proper.  */
> +void
> +loongarch_config_target (struct loongarch_target *target,
> +  HOST_WIDE_INT opt_switches,
> +  int opt_arch, int opt_tune, int opt_fpu,
> +  int opt_abi_base, int opt_abi_ext,
> +  int opt_cmodel, int follow_multilib_list);
> +#endif

This is causing failures building libobjc (complaining that `extern "C"`
can't be used in C code, and HOST_WIDE_INT is not defined).

I think

#ifdef IN_LIBGCC2

should be replaced with

#if defined(IN_LIBGCC2) || defined(IN_TARGET_LIBS)
-- 
Xi Ruoyao <xry111@mengyan1223.wang>
School of Aerospace Science and Technology, Xidian University

  parent reply	other threads:[~2021-11-28  0:51 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-27  8:27 LoongArch Port chenglulu
2021-11-27  8:27 ` [PATCH 01/12] LoongArch Port: gcc build chenglulu
2021-11-27 23:39   ` Xi Ruoyao
2021-11-27 23:43     ` Xi Ruoyao
2021-11-28  0:51   ` Xi Ruoyao [this message]
2021-11-29 21:10   ` Joseph Myers
2021-11-27  8:27 ` [PATCH 02/12] LoongArch Port: Regenerate gcc/configure chenglulu
2021-11-27  8:27 ` [PATCH 03/12] LoongArch Port: Machine Decsription files chenglulu
2021-11-27  8:27 ` [PATCH 04/12] LoongArch Port: Machine description C files and .h files chenglulu
2021-11-27  8:27 ` [PATCH 05/12] LoongArch Port: Builtin functions chenglulu
2021-11-27  8:27 ` [PATCH 06/12] LoongArch Port: Builtin macros chenglulu
2021-11-27  8:27 ` [PATCH 07/12] LoongArch Port: libgcc chenglulu
2021-11-27  8:27 ` [PATCH 08/12] LoongArch Port: Regenerate libgcc/configure chenglulu
2021-11-27  8:27 ` [PATCH 09/12] LoongArch Port: libgomp chenglulu
2021-11-27  8:27 ` [PATCH 10/12] LoongArch Port: gcc/testsuite chenglulu
2021-11-27  8:27 ` [PATCH 11/12] LoongArch Port: Regenerate configure chenglulu
2021-11-27  8:27 ` [PATCH 12/12] LoongArch Port: Add doc chenglulu
2021-11-27  9:57 ` LoongArch Port Xi Ruoyao
2021-11-28  0:06 ` Xi Ruoyao
2021-11-28  8:37 ` Xi Ruoyao

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=25a89acf318adfc42a0d8af0eb9ecb6fb062b20a.camel@mengyan1223.wang \
    --to=xry111@mengyan1223.wang \
    --cc=chenglulu@loongson.cn \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=xuchenghua@loongson.cn \
    --cc=yangyujie@loongson.cn \
    /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).