public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "balder at yahooinc dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/108599] Incorrect code generation newer intel architectures for gcc 12 and 13
Date: Mon, 30 Jan 2023 13:32:02 +0000 [thread overview]
Message-ID: <bug-108599-4-0DRWbt2iaU@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108599-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108599
--- Comment #2 from Henning Baldersheim <balder at yahooinc dot com> ---
This is an even bigger issue with gcc 13. Then it only requires -march=haswell
Works:
c++ -Wall -Wextra -O3 -march=ivybridge test.cpp && ./a.out
Fails:
c++ -Wall -Wextra -O3 -march=haswell test.cpp && ./a.out
a.out: test.cpp:23: void assert_stats(size_t, size_t, size_t, size_t, Stats):
Assertion `exp_dead == stats._dead' failed.
gcc version:
gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-redhat-linux/13/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-redhat-linux
Configured with: ../configure --enable-bootstrap
--enable-languages=c,c++,fortran,objc,obj-c++,ada,go,d,m2,lto
--prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info
--with-bugurl=https://urldefense.com/v3/__http://bugzilla.redhat.com/bugzilla__;!!Op6eflyXZCqGR5I!CPaxwlsoI_wy_AwjCIWAdmMOLgtd7sjMpqqz-fNyAFo5nnEaBO0guYKTV5m7wWkHYS5N4zBFXJGe0DaFnA$
--enable-shared
--enable-threads=posix --enable-checking=release --enable-multilib
--with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions
--enable-gnu-unique-object --enable-linker-build-id
--with-gcc-major-version-only --enable-libstdcxx-backtrace
--with-libstdcxx-zoneinfo=/usr/share/zoneinfo
--with-linker-hash-style=gnu --enable-plugin --enable-initfini-array
--with-isl=/builddir/build/BUILD/gcc-13.0.1-20230117/obj-x86_64-redhat-linux/isl-install
--enable-offload-targets=nvptx-none --without-cuda-driver
--enable-offload-defaulted --enable-gnu-indirect-function --enable-cet
--with-tune=generic --with-arch_32=i686 --build=x86_64-redhat-linux
--with-build-config=bootstrap-lto --enable-link-serialization=1
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 13.0.1 20230117 (Red Hat 13.0.1-0) (GCC)
next prev parent reply other threads:[~2023-01-30 13:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 13:18 [Bug c++/108599] New: " balder at yahooinc dot com
2023-01-30 13:20 ` [Bug c++/108599] " balder at yahooinc dot com
2023-01-30 13:32 ` balder at yahooinc dot com [this message]
2023-01-30 13:49 ` [Bug target/108599] [12/13 Regression] Incorrect code generation newer intel architectures jakub at gcc dot gnu.org
2023-01-30 14:00 ` jakub at gcc dot gnu.org
2023-01-30 14:10 ` jakub at gcc dot gnu.org
2023-01-30 14:31 ` jakub at gcc dot gnu.org
2023-01-30 15:17 ` rguenth at gcc dot gnu.org
2023-01-30 15:19 ` jakub at gcc dot gnu.org
2023-01-31 9:12 ` cvs-commit at gcc dot gnu.org
2023-01-31 9:14 ` [Bug target/108599] [12 " jakub at gcc dot gnu.org
2023-02-09 11:54 ` balder at yahooinc dot com
2023-02-09 12:02 ` jakub at gcc dot gnu.org
2023-02-10 17:46 ` cvs-commit at gcc dot gnu.org
2023-02-10 18:01 ` jakub 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-108599-4-0DRWbt2iaU@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).