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 tree-optimization/107176] [10/11/12/13 Regression] Wrong code at -Os on x86_64-pc-linux-gnu
Date: Thu, 06 Oct 2022 20:50:22 +0000	[thread overview]
Message-ID: <bug-107176-4-bIxDGIgSZj@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107176-4@http.gcc.gnu.org/bugzilla/>

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|---                         |10.5
          Component|c                           |tree-optimization
           Keywords|                            |wrong-code
      Known to fail|                            |7.1.0
     Ever confirmed|0                           |1
             Status|UNCONFIRMED                 |NEW
            Summary|Wrong code at -O0/-Os on    |[10/11/12/13 Regression]
                   |x86_64-pc-linux-gnu         |Wrong code at -Os on
                   |                            |x86_64-pc-linux-gnu
   Last reconfirmed|                            |2022-10-06
      Known to work|                            |6.3.0

--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Confirmed.
Here is a better testcase:
#include <stdio.h>

int a;
long b;
static inline long c(unsigned d) { 
    return d; 
}
static inline void e(int d) { 
    a = d; 
}
int main() {
  b = 0;
  for (; b < 1; b = c(b - 90) + 90 + 1)
    ;
  e(b >> 2);
  printf("%d\n", a);
  if (a != 1073741824)
    __builtin_abort();
}

  reply	other threads:[~2022-10-06 20:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-06 20:41 [Bug c/107176] New: Wrong code at -O0/-Os " shaohua.li at inf dot ethz.ch
2022-10-06 20:50 ` pinskia at gcc dot gnu.org [this message]
2022-10-07  7:30 ` [Bug tree-optimization/107176] [10/11/12/13 Regression] Wrong code at -Os " rguenth at gcc dot gnu.org
2022-10-07 14:36 ` [Bug tree-optimization/107176] [10/11/12/13 Regression] Wrong code at -Os on x86_64-pc-linux-gnu since r7-2012-g43aabfcfd4139e4c marxin at gcc dot gnu.org
2022-10-18  8:35 ` rguenth at gcc dot gnu.org
2022-10-21 13:25 ` rguenth at gcc dot gnu.org
2022-10-24  8:30 ` rguenth at gcc dot gnu.org
2022-10-24  9:54 ` rguenth at gcc dot gnu.org
2022-10-24 13:31 ` rguenth at gcc dot gnu.org
2022-10-25 11:40 ` cvs-commit at gcc dot gnu.org
2022-10-25 11:41 ` [Bug tree-optimization/107176] [10/11/12 " rguenth at gcc dot gnu.org
2022-11-28 10:18 ` rguenth at gcc dot gnu.org
2023-07-07 10:44 ` [Bug tree-optimization/107176] [11/12 " 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-107176-4-bIxDGIgSZj@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).