public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/113689] [11/12/13/14 Regression] wrong code with -fprofile -mcmodel=large when needing drap register since r11-6548
Date: Mon, 05 Feb 2024 19:08:53 +0000	[thread overview]
Message-ID: <bug-113689-4-gRuuZKxGnD@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113689-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by H.J. Lu <hjl@gcc.gnu.org>:

https://gcc.gnu.org/g:51f8ac3341078303e81e72d9013698a31c5ddd29

commit r14-8808-g51f8ac3341078303e81e72d9013698a31c5ddd29
Author: H.J. Lu <hjl.tools@gmail.com>
Date:   Thu Feb 1 08:02:27 2024 -0800

    x86-64: Find a scratch register for large model profiling

    2 scratch registers, %r10 and %r11, are available at function entry for
    large model profiling.  But %r10 may be used by stack realignment and we
    can't use %r10 in this case.  Add x86_64_select_profile_regnum to find
    a caller-saved register which isn't live or a callee-saved register
    which has been saved on stack in the prologue at entry for large model
    profiling and sorry if we can't find one.

    gcc/

            PR target/113689
            * config/i386/i386.cc (x86_64_select_profile_regnum): New.
            (x86_function_profiler): Call x86_64_select_profile_regnum to
            get a scratch register for large model profiling.

    gcc/testsuite/

            PR target/113689
            * gcc.target/i386/pr113689-1.c: New file.
            * gcc.target/i386/pr113689-2.c: Likewise.
            * gcc.target/i386/pr113689-3.c: Likewise.

  parent reply	other threads:[~2024-02-05 19:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-31 20:32 [Bug target/113689] New: wrong code with unused _BitInt() division with -O2 -fprofile -mcmodel=large -mavx zsojka at seznam dot cz
2024-01-31 23:04 ` [Bug target/113689] " pinskia at gcc dot gnu.org
2024-02-01 12:27 ` [Bug target/113689] [11/12/13/14 Regression] wrong code with -fprofile -mcmodel=large when needing drap register since r11-6548 jakub at gcc dot gnu.org
2024-02-01 12:39 ` jakub at gcc dot gnu.org
2024-02-01 18:23 ` hjl.tools at gmail dot com
2024-02-05 19:08 ` cvs-commit at gcc dot gnu.org [this message]
2024-02-05 19:09 ` hjl.tools at gmail dot com
2024-02-06 18:30 ` ro at gcc dot gnu.org
2024-02-06 18:37 ` jakub at gcc dot gnu.org
2024-02-06 18:42 ` hjl.tools at gmail dot com
2024-02-06 18:50 ` jakub at gcc dot gnu.org
2024-02-06 18:58 ` hjl.tools at gmail dot com
2024-02-06 19:03 ` cvs-commit 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-113689-4-gRuuZKxGnD@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).