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 ipa/56139] [9/10/11/12 Regression] unmodified static data could go in .rodata, not .data
Date: Sat, 25 Dec 2021 09:55:27 +0000	[thread overview]
Message-ID: <bug-56139-4-wbhq1f9P3t@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56139-4@http.gcc.gnu.org/bugzilla/>

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|tree-optimization           |ipa
   Target Milestone|---                         |13.0
           Keywords|                            |deferred
      Known to fail|                            |4.7.1
           Severity|enhancement                 |normal
                 CC|                            |marxin at gcc dot gnu.org
            Summary|unmodified static data      |[9/10/11/12 Regression]
                   |could go in .rodata, not    |unmodified static data
                   |.data                       |could go in .rodata, not
                   |                            |.data

--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
We do handle:
static int x[] = {1, 2, 3, 4};

void bar (int x);

int func(int i)
{
    bar(x[i]);

    return 0;
}

Just fine. It is the IR of the other case where we mess up. And it looks like
it is a regression too. I suspect it is because we used to be able to create
back the ARARY_REF in GCC 4.6.x and that was removed in GCC 4.7 as it caused
other issues.

  parent reply	other threads:[~2021-12-25  9:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-29 10:06 [Bug tree-optimization/56139] New: " amker.cheng at gmail dot com
2015-01-23 10:40 ` [Bug tree-optimization/56139] " ramana at gcc dot gnu.org
2021-12-25  9:55 ` pinskia at gcc dot gnu.org [this message]
2022-10-19  8:52 ` [Bug ipa/56139] [10/11/12/13 Regression] " rguenth at gcc dot gnu.org
2023-01-14 21:56 ` hubicka at gcc dot gnu.org
2023-04-26  6:55 ` [Bug ipa/56139] [10/11/12/13/14 " rguenth at gcc dot gnu.org
2023-07-27  9:19 ` [Bug ipa/56139] [11/12/13/14 " 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-56139-4-wbhq1f9P3t@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).