public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/103641] [11/12 regression] Severe compile time regression in SLP vectorize step
Date: Fri, 10 Dec 2021 10:06:27 +0000	[thread overview]
Message-ID: <bug-103641-4-yD2O7ZN6Ay@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103641-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103641

--- Comment #9 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #8)
> (In reply to Martin Liška from comment #6)
> > How does one enable NEON? What -mcpu -mtune do you use?
> 
> NEON is enabled by default :).

I have a cross compiler that can't consume the provided pre-processed source
file:

$ marxin@marxinbox:~/Programming/testcases> aarch64-suse-linux-gcc-11 -v
Using built-in specs.
COLLECT_GCC=aarch64-suse-linux-gcc-11
COLLECT_LTO_WRAPPER=/usr/lib64/gcc/aarch64-suse-linux/11/lto-wrapper
Target: aarch64-suse-linux
Configured with: ../configure --prefix=/usr --infodir=/usr/share/info
--mandir=/usr/share/man --libdir=/usr/lib64 --libexecdir=/usr/lib64
--enable-languages=c,c++ --enable-checking=release --disable-werror
--with-gxx-include-dir=/usr/include/c++/11 --enable-ssp --disable-libssp
--disable-libvtv --enable-cet=auto --disable-libcc1 --disable-plugin
--with-bugurl=https://bugs.opensuse.org/ --with-pkgversion='SUSE Linux'
--with-slibdir=/usr/aarch64-suse-linux/sys-root/lib64 --with-system-zlib
--enable-libstdcxx-allocator=new --disable-libstdcxx-pch
--enable-version-specific-runtime-libs --with-gcc-major-version-only
--enable-linker-build-id --enable-linux-futex --enable-gnu-indirect-function
--program-suffix=-11 --program-prefix=aarch64-suse-linux-
--target=aarch64-suse-linux --disable-nls
--with-sysroot=/usr/aarch64-suse-linux/sys-root
--with-build-sysroot=/usr/aarch64-suse-linux/sys-root
--with-build-time-tools=/usr/aarch64-suse-linux/bin
--enable-fix-cortex-a53-835769 --enable-fix-cortex-a53-843419
--disable-libsanitizer --build=x86_64-suse-linux --host=x86_64-suse-linux
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 11.2.1 20211124 [revision 7510c23c1ec53aa4a62705f0384079661342ff7b]
(SUSE Linux) 

$ aarch64-suse-linux-gcc-11 xxhash.i -c -fmax-errors=5
In file included from xxhash.h:2710,
                 from xxhash.c:43:
/home/ubuntu/upstream-gcc/lib/gcc/aarch64-unknown-linux-gnu/12.0.0/include/arm_neon.h:33:9:
error: unknown '#pragma GCC aarch64' option 'arm_neon.h'
In file included from xxhash.h:2710,
                 from xxhash.c:43:
/home/ubuntu/upstream-gcc/lib/gcc/aarch64-unknown-linux-gnu/12.0.0/include/arm_neon.h:
In function 'vaddl_u8':
/home/ubuntu/upstream-gcc/lib/gcc/aarch64-unknown-linux-gnu/12.0.0/include/arm_neon.h:401:10:
error: incompatible types when returning type 'int' but 'uint16x8_t' was
expected
/home/ubuntu/upstream-gcc/lib/gcc/aarch64-unknown-linux-gnu/12.0.0/include/arm_neon.h:
In function 'vaddl_u16':
/home/ubuntu/upstream-gcc/lib/gcc/aarch64-unknown-linux-gnu/12.0.0/include/arm_neon.h:408:10:
error: incompatible types when returning type 'int' but 'uint32x4_t' was
expected
/home/ubuntu/upstream-gcc/lib/gcc/aarch64-unknown-linux-gnu/12.0.0/include/arm_neon.h:
In function 'vaddl_u32':
/home/ubuntu/upstream-gcc/lib/gcc/aarch64-unknown-linux-gnu/12.0.0/include/arm_neon.h:415:10:
error: incompatible types when returning type 'int' but 'uint64x2_t' was
expected
/home/ubuntu/upstream-gcc/lib/gcc/aarch64-unknown-linux-gnu/12.0.0/include/arm_neon.h:
In function 'vaddl_high_u8':
/home/ubuntu/upstream-gcc/lib/gcc/aarch64-unknown-linux-gnu/12.0.0/include/arm_neon.h:443:10:
error: incompatible types when returning type 'int' but 'uint16x8_t' was
expected

That's why I'm asking.

  parent reply	other threads:[~2021-12-10 10:06 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-10  9:03 [Bug rtl-optimization/103641] New: [aarch64][11 " husseydevin at gmail dot com
2021-12-10  9:25 ` [Bug rtl-optimization/103641] " marxin at gcc dot gnu.org
2021-12-10  9:37 ` [Bug tree-optimization/103641] " pinskia at gcc dot gnu.org
2021-12-10  9:43 ` [Bug tree-optimization/103641] [11/12 " pinskia at gcc dot gnu.org
2021-12-10  9:46 ` pinskia at gcc dot gnu.org
2021-12-10  9:56 ` pinskia at gcc dot gnu.org
2021-12-10 10:01 ` marxin at gcc dot gnu.org
2021-12-10 10:02 ` pinskia at gcc dot gnu.org
2021-12-10 10:03 ` pinskia at gcc dot gnu.org
2021-12-10 10:06 ` marxin at gcc dot gnu.org [this message]
2021-12-10 10:08 ` pinskia at gcc dot gnu.org
2021-12-10 10:09 ` pinskia at gcc dot gnu.org
2021-12-10 10:12 ` marxin at gcc dot gnu.org
2021-12-10 10:12 ` pinskia at gcc dot gnu.org
2021-12-10 10:14 ` pinskia at gcc dot gnu.org
2021-12-10 10:15 ` [Bug middle-end/103641] " pinskia at gcc dot gnu.org
2021-12-10 10:24 ` pinskia at gcc dot gnu.org
2021-12-10 10:28 ` pinskia at gcc dot gnu.org
2021-12-10 13:17 ` roger at nextmovesoftware dot com
2021-12-10 13:19 ` husseydevin at gmail dot com
2022-01-18 14:10 ` rguenth at gcc dot gnu.org
2022-01-22 14:30 ` roger at nextmovesoftware dot com
2022-01-24  8:13 ` rguenther at suse dot de
2022-01-24 16:49 ` roger at nextmovesoftware dot com
2022-01-24 17:02 ` roger at nextmovesoftware dot com
2022-01-25  7:23 ` rguenth at gcc dot gnu.org
2022-01-25  7:52 ` rguenth at gcc dot gnu.org
2022-02-04  7:26 ` rguenth at gcc dot gnu.org
2022-02-04 10:30 ` cvs-commit at gcc dot gnu.org
2022-02-04 10:43 ` rguenth at gcc dot gnu.org
2022-02-04 11:08 ` tnfchris at gcc dot gnu.org
2022-02-07 12:19 ` tnfchris at gcc dot gnu.org
2022-02-07 15:05 ` [Bug middle-end/103641] [11 " rguenth at gcc dot gnu.org
2022-02-08  8:08 ` tnfchris at gcc dot gnu.org
2022-02-08  8:13 ` pinskia at gcc dot gnu.org
2022-02-08  8:15 ` tnfchris at gcc dot gnu.org
2022-03-16  8:22 ` cvs-commit at gcc dot gnu.org
2022-03-16  8:23 ` rguenth 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-103641-4-yD2O7ZN6Ay@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).