public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/113689] wrong code with unused _BitInt() division with -O2 -fprofile -mcmodel=large -mavx
Date: Wed, 31 Jan 2024 23:04:38 +0000	[thread overview]
Message-ID: <bug-113689-4-dy9xJ413SN@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

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Last reconfirmed|                            |2024-01-31
             Status|UNCONFIRMED                 |NEW
     Ever confirmed|0                           |1

--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Confirmed. s/511/(256-63)/ is the min to reproduce this issue. Basically just
enough to auto-vectorize.

I get the feeling that mcount causes alignment differences ...

  reply	other threads:[~2024-01-31 23:04 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-31 20:32 [Bug target/113689] New: " zsojka at seznam dot cz
2024-01-31 23:04 ` pinskia at gcc dot gnu.org [this message]
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
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-dy9xJ413SN@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).