public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/104763] [12 Regression] Generate wrong assembly code
Date: Mon, 07 Mar 2022 08:07:22 +0000	[thread overview]
Message-ID: <bug-104763-4-sOMr9rOeXm@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104763-4@http.gcc.gnu.org/bugzilla/>

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           See Also|                            |https://gcc.gnu.org/bugzill
                   |                            |a/show_bug.cgi?id=85803

--- Comment #6 from Richard Biener <rguenth at gcc dot gnu.org> ---
PR85803 - I'd say this bug is a duplicate (to some extent).  Simplified
testcase
that, with the help of alarm() and signal handlers could be turned into a
runtime FAIL.

typedef __SIZE_TYPE__ size_t;
void move_up(void *p)
{
  for ( size_t* i=(size_t *)(p); ; )
    {
      *i=0x0700070007000700;
      if (i == (size_t *)(p)+2 )
        break;
      ++i;
    }
  while (1){}
}

  parent reply	other threads:[~2022-03-07  8:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-02 18:01 [Bug c/104763] New: [12.0] " 570070308 at qq dot com
2022-03-02 18:44 ` [Bug c/104763] " 570070308 at qq dot com
2022-03-02 18:58 ` jakub at gcc dot gnu.org
2022-03-03  5:08 ` [Bug middle-end/104763] " 570070308 at qq dot com
2022-03-03 11:35 ` [Bug middle-end/104763] [12 Regression] " marxin at gcc dot gnu.org
2022-03-07  8:03 ` rguenth at gcc dot gnu.org
2022-03-07  8:07 ` rguenth at gcc dot gnu.org [this message]
2022-03-07  8:12 ` rguenth at gcc dot gnu.org
2022-03-07  8:37 ` 570070308 at qq dot com
2022-03-07  9:05 ` 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-104763-4-sOMr9rOeXm@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).