public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "zsojka at seznam dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/102798] New: [9/10/11/12 Regression] wrong code with -O3 -fno-tree-pta -mavx512f
Date: Sat, 16 Oct 2021 12:43:56 +0000	[thread overview]
Message-ID: <bug-102798-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 102798
           Summary: [9/10/11/12 Regression] wrong code with -O3
                    -fno-tree-pta -mavx512f
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Keywords: wrong-code
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: zsojka at seznam dot cz
  Target Milestone: ---
              Host: x86_64-pc-linux-gnu
            Target: x86_64-pc-linux-gnu

Created attachment 51616
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51616&action=edit
auto-reduced testcase (from OpenSSL sources)

$ x86_64-pc-linux-gnu-gcc -O3 -fno-tree-pta -mavx512f testcase.c
$ gdb ./a.out
...
(gdb) r
Starting program: /home/smatz/gcc-bug/58/a.out 

Program received signal SIGSEGV, Segmentation fault.
BUF_reverse (out=<optimized out>, out@entry=0x7fffffffda60 "", in=<optimized
out>, in@entry=0x0, size=size@entry=40) at testcase.c:11
11              *out-- = *in++;
(gdb) disas
Dump of assembler code for function BUF_reverse:
...
   0x0000000000401200 <+96>:    and    $0xffffffffffffffe0,%r9
   0x0000000000401204 <+100>:   add    %rcx,%r9
   0x0000000000401207 <+103>:   nopw   0x0(%rax,%rax,1)
=> 0x0000000000401210 <+112>:   vmovdqu (%rdx),%ymm2
   0x0000000000401214 <+116>:   add    $0x20,%rdx
   0x0000000000401218 <+120>:   sub    $0x20,%rdi
   0x000000000040121c <+124>:   vperm2i128 $0x1,%ymm2,%ymm2,%ymm0
...
(gdb) info reg
rax            0x28                40
rbx            0x4013d0            4199376
rcx            0x0                 0
rdx            0x0                 0
...

$ x86_64-pc-linux-gnu-gcc -v
Using built-in specs.
COLLECT_GCC=/repo/gcc-trunk/binary-latest-amd64/bin/x86_64-pc-linux-gnu-gcc
COLLECT_LTO_WRAPPER=/repo/gcc-trunk/binary-trunk-r12-4456-20211016001627-g93d183a5fff-checking-yes-rtl-df-extra-amd64/bin/../libexec/gcc/x86_64-pc-linux-gnu/12.0.0/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: /repo/gcc-trunk//configure --enable-languages=c,c++
--enable-valgrind-annotations --disable-nls --enable-checking=yes,rtl,df,extra
--with-cloog --with-ppl --with-isl --build=x86_64-pc-linux-gnu
--host=x86_64-pc-linux-gnu --target=x86_64-pc-linux-gnu
--with-ld=/usr/bin/x86_64-pc-linux-gnu-ld
--with-as=/usr/bin/x86_64-pc-linux-gnu-as --disable-libstdcxx-pch
--prefix=/repo/gcc-trunk//binary-trunk-r12-4456-20211016001627-g93d183a5fff-checking-yes-rtl-df-extra-amd64
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 12.0.0 20211016 (experimental) (GCC)

             reply	other threads:[~2021-10-16 12:43 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-16 12:43 zsojka at seznam dot cz [this message]
2021-10-16 15:54 ` [Bug tree-optimization/102798] [9/10/11/12 Regression] wrong code with -O3 -fno-tree-pta -mavx512f by r9-2475 hjl.tools at gmail dot com
2021-10-16 16:31 ` hjl.tools at gmail dot com
2021-10-16 18:10 ` hjl.tools at gmail dot com
2021-10-16 18:16 ` hjl.tools at gmail dot com
2021-10-16 18:42 ` pinskia at gcc dot gnu.org
2021-10-16 18:43 ` pinskia at gcc dot gnu.org
2021-10-16 18:46 ` [Bug tree-optimization/102798] [9/10/11/12 Regression] wrong code with -O3 -fno-tree-pta " pinskia at gcc dot gnu.org
2021-10-16 19:08 ` hjl.tools at gmail dot com
2021-10-17  0:53 ` hjl.tools at gmail dot com
2021-10-17  2:49 ` hjl.tools at gmail dot com
2021-10-17 13:33 ` hjl.tools at gmail dot com
2021-10-17 18:29 ` hjl.tools at gmail dot com
2021-10-18  6:39 ` rguenth at gcc dot gnu.org
2021-10-18  7:03 ` rguenth at gcc dot gnu.org
2021-10-18  8:26 ` cvs-commit at gcc dot gnu.org
2021-10-18  8:27 ` [Bug tree-optimization/102798] [9/10/11 " rguenth at gcc dot gnu.org
2021-11-08 13:32 ` cvs-commit at gcc dot gnu.org
2022-02-17 10:48 ` [Bug tree-optimization/102798] [9/10 " cvs-commit at gcc dot gnu.org
2022-02-17 11:57 ` [Bug tree-optimization/102798] [9 " cvs-commit at gcc dot gnu.org
2022-02-17 11:58 ` rguenth at gcc dot gnu.org
2022-02-18  7:10 ` rguenth at gcc dot gnu.org
2022-02-18  7:11 ` rguenth at gcc dot gnu.org
2022-02-18  7:13 ` rguenth at gcc dot gnu.org
2022-02-18  8:21 ` rguenth at gcc dot gnu.org
2022-02-18  8:22 ` 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-102798-4@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).