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/101023] New: [11/12 Regression] wrong code with -mstackrealign
Date: Thu, 10 Jun 2021 21:13:24 +0000	[thread overview]
Message-ID: <bug-101023-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 101023
           Summary: [11/12 Regression] wrong code with -mstackrealign
           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 50981
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50981&action=edit
auto-reduced testcase (from OpenTTD sources)

Compiler output:
$ x86_64-pc-linux-gnu-g++ -O2 -mtune=opteron -mstackrealign
--param=hot-bb-frequency-fraction=1 testcase.C -S

The offending code is:
.L8:
        pushq   %rbp
        .cfi_def_cfa_offset 16
        .cfi_offset 6, -16
        movq    %rsp, %rbp
        .cfi_def_cfa_register 6
        movq    %r12, -8(%rbp)
        pushq   %rax

the "push" overwrites r12 stored just one instruction above; when returning:
        movq    -8(%rbp), %r12
        xorl    %eax, %eax
        leave
        .cfi_def_cfa 7, 8
        ret

the wrong data is restored to r12

I wasn't able yet to generate an executable testcase, but I can try to if
needed. (it shouldn't be that hard, just r12 needs to be used by the caller
during the call)

$ x86_64-pc-linux-gnu-g++ -v
Using built-in specs.
COLLECT_GCC=/repo/gcc-trunk/binary-latest-amd64/bin/x86_64-pc-linux-gnu-g++
COLLECT_LTO_WRAPPER=/repo/gcc-trunk/binary-trunk-r12-1366-20210610095751-g6fcba9ef23e-checking-yes-rtl-df-extra-nobootstrap-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
--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 --disable-libstdcxx-pch
--prefix=/repo/gcc-trunk//binary-trunk-r12-1366-20210610095751-g6fcba9ef23e-checking-yes-rtl-df-extra-nobootstrap-amd64
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 12.0.0 20210610 (experimental) (GCC)

             reply	other threads:[~2021-06-10 21:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-10 21:13 zsojka at seznam dot cz [this message]
2021-06-11  8:03 ` [Bug target/101023] " rguenth at gcc dot gnu.org
2021-06-11  8:19 ` ubizjak at gmail dot com
2021-06-11 12:25 ` hjl.tools at gmail dot com
2021-06-11 12:56 ` jakub at gcc dot gnu.org
2021-06-11 12:56 ` jakub at gcc dot gnu.org
2021-06-11 13:09 ` zsojka at seznam dot cz
2021-06-11 14:37 ` hjl.tools at gmail dot com
2021-06-11 20:49 ` hjl.tools at gmail dot com
2021-06-13 12:16 ` cvs-commit at gcc dot gnu.org
2021-06-13 13:16 ` hjl.tools at gmail dot com
2021-07-15 12:43 ` cvs-commit at gcc dot gnu.org
2021-07-15 12:43 ` hjl.tools at gmail dot com

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-101023-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).