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/114415] New: wrong code with -Oz -fno-dce -fno-forward-propagate -flive-range-shrinkage -fweb
Date: Thu, 21 Mar 2024 12:52:07 +0000	[thread overview]
Message-ID: <bug-114415-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 114415
           Summary: wrong code with -Oz -fno-dce -fno-forward-propagate
                    -flive-range-shrinkage -fweb
           Product: gcc
           Version: 14.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 57755
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57755&action=edit
reduced testcase

Output:
$ x86_64-pc-linux-gnu-gcc -Oz -fno-dce -fno-forward-propagate
-flive-range-shrinkage -fweb testcase.c -Wno-psabi
$ ./a.out 
Aborted


It seems the issue is in:


   0x000000000040137e <+214>:   movq   $0x1,-0x1b0(%rbp)
   0x0000000000401389 <+225>:   push   $0x10
   0x000000000040138b <+227>:   pop    %rcx
   0x000000000040138c <+228>:   rep movsl %ds:(%rsi),%es:(%rdi)
=> 0x000000000040138e <+230>:   push   $0x10
   0x0000000000401390 <+232>:   mov    %rbx,%rdi
   0x0000000000401393 <+235>:   lea    -0xf0(%rbp),%rsi
   0x000000000040139a <+242>:   pop    %rcx

(gdb) p $rsp
$48 = (void *) 0x7fffffffd3c0

(gdb) p/x $rdi
$50 = 0x7fffffffd3c0

that "push" overwrites the destination of the just finished "rep movsd"; this
is probably specific to -Oz


$ 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-r14-9591-20240321175934-gac2f8c2a367-checking-yes-rtl-df-extra-nobootstrap-amd64/bin/../libexec/gcc/x86_64-pc-linux-gnu/14.0.1/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
--disable-bootstrap --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 --enable-libsanitizer
--disable-libstdcxx-pch
--prefix=/repo/gcc-trunk//binary-trunk-r14-9591-20240321175934-gac2f8c2a367-checking-yes-rtl-df-extra-nobootstrap-amd64
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 14.0.1 20240321 (experimental) (GCC)

             reply	other threads:[~2024-03-21 12:52 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-21 12:52 zsojka at seznam dot cz [this message]
2024-03-25 14:43 ` [Bug target/114415] [13/14 Regression] wrong code with -Oz -fno-dce -fno-forward-propagate -flive-range-shrinkage -fweb since r13-1826 jakub at gcc dot gnu.org
2024-03-25 16:59 ` jakub at gcc dot gnu.org
2024-03-25 17:15 ` jakub at gcc dot gnu.org
2024-03-29 23:49 ` law at gcc dot gnu.org
2024-04-03 16:28 ` vmakarov at gcc dot gnu.org
2024-04-04 11:32 ` vmakarov at gcc dot gnu.org
2024-04-04 20:07 ` [Bug rtl-optimization/114415] " cvs-commit at gcc dot gnu.org
2024-04-05  4:10 ` [Bug rtl-optimization/114415] [13 " law at gcc dot gnu.org
2024-04-06 12:01 ` ebotcazou at gcc dot gnu.org
2024-04-06 17:35 ` law at gcc dot gnu.org
2024-05-08 12:28 ` rguenth at gcc dot gnu.org
2024-05-09 10:04 ` jakub at gcc dot gnu.org
2024-05-09 15:40 ` vmakarov at gcc dot gnu.org
2024-05-09 16:42 ` cvs-commit at gcc dot gnu.org
2024-05-09 19:06 ` 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-114415-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).