DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: David Christensen <drc@linux.vnet.ibm.com>
Cc: dev@dpdk.org, Thinh Tran <thinhtr@linux.vnet.ibm.com>,
	david.marchand@redhat.com
Subject: Re: [PATCH v2] config/ppc: fix gcc "internal compiler error" message for p10
Date: Wed, 28 Jun 2023 01:35:27 +0200	[thread overview]
Message-ID: <1818610.BzM5BlMlMQ@thomas> (raw)
In-Reply-To: <20230627210341.2516951-1-drc@linux.vnet.ibm.com>

27/06/2023 23:03, David Christensen:
> Building DPDK with gcc 11.3.x for the power10 instruction set may
> generate the following error:
> 
> ../drivers/mempool/cnxk/cnxk_mempool_ops.c
> during RTL pass: final
> ../drivers/mempool/cnxk/cnxk_mempool_ops.c:
>   In function ‘cnxk_mempool_alloc’:
> ../drivers/mempool/cnxk/cnxk_mempool_ops.c:124:1:
>   internal compiler error: output_operand: invalid expression as operand
>   124 | }
>       | ^
> Please submit a full bug report,
> with preprocessed source if appropriate.
> ...
> ninja: build stopped: subcommand failed.
> 
> The same issue is not encountered when building with gcc 11.4 or
> later, where the compiler automatically adds the option
> "-mno-block-ops-vector-pair" when building for power10 which
> is intended as a code optimization and also effectively avoids
> the compiler bug displayed.
> 
> Modify the meson.build file for ppc and manually set the flag when
> building for power10 with gcc less than 11.4.
> 
> Bugzilla ID: 1251
> 
> Signed-off-by: David Christensen <drc@linux.vnet.ibm.com>
> Tested-by: Thinh Tran <thinhtr@linux.vnet.ibm.com>

Applied, thanks.

Note: IBM POWER support is still marked as alpha.
Would you like to work on its status?



      reply	other threads:[~2023-06-27 23:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-27 20:54 [PATCH] " David Christensen
2023-06-27 21:03 ` [PATCH v2] " David Christensen
2023-06-27 23:35   ` Thomas Monjalon [this message]

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=1818610.BzM5BlMlMQ@thomas \
    --to=thomas@monjalon.net \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=drc@linux.vnet.ibm.com \
    --cc=thinhtr@linux.vnet.ibm.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 NNTP newsgroup(s).