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/111818] [11/12/13/14 Regression] ICE with __builtin_memcpy with volatile and constants
Date: Mon, 16 Oct 2023 06:59:45 +0000	[thread overview]
Message-ID: <bug-111818-4-gy2UB4pOiZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111818-4@http.gcc.gnu.org/bugzilla/>

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Assignee|unassigned at gcc dot gnu.org      |rguenth at gcc dot gnu.org
             Status|NEW                         |ASSIGNED

--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
It's inlining of

void foo (const volatile unsigned int x, void * p)
{
  unsigned int _2;
  unsigned int _5;

  <bb 2> [local count: 1073741824]:
  _2 ={v} MEM <unsigned int> [(char * {ref-all})&x];

into

  foo (305419896, number_4(D));

Smaller testcase:

static void foo(const volatile unsigned int x, void *p) 
{ 
  __builtin_memcpy(p, &x, sizeof x);
}

void bar(void *number)
{ 
  foo(0, number);
}

  parent reply	other threads:[~2023-10-16  6:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-15  1:38 [Bug c/111818] New: GCC: 14: internal compiler error: tree check: expected tree that contains 'decl common' structure, have 'integer_cst' in tree_could_trap_p, at tree-eh.cc:2733 141242068 at smail dot nju.edu.cn
2023-10-15  1:47 ` [Bug middle-end/111818] [11/12/13/14 Regression] ICE with __builtin_memcpy with volatile and constants pinskia at gcc dot gnu.org
2023-10-16  6:59 ` rguenth at gcc dot gnu.org [this message]
2023-10-17  6:26 ` cvs-commit at gcc dot gnu.org
2023-10-17  6:27 ` [Bug middle-end/111818] [11/12/13 " rguenth at gcc dot gnu.org
2023-11-10 14:24 ` cvs-commit at gcc dot gnu.org
2023-11-27 13:09 ` [Bug middle-end/111818] [11/12 " cvs-commit at gcc dot gnu.org
2023-12-15 12:18 ` [Bug middle-end/111818] [11 " cvs-commit at gcc dot gnu.org
2023-12-15 12:22 ` 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-111818-4-gy2UB4pOiZ@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).