public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ramana at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/56139] unmodified static data could go in .rodata, not .data
Date: Fri, 23 Jan 2015 10:40:00 -0000	[thread overview]
Message-ID: <bug-56139-4-9Z4hHX7fJj@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

Ramana Radhakrishnan <ramana at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2015-01-23
                 CC|                            |ramana at gcc dot gnu.org
     Ever confirmed|0                           |1
      Known to fail|                            |4.9.0, 5.0

--- Comment #1 from Ramana Radhakrishnan <ramana at gcc dot gnu.org> ---
If it worked in 4.6 then this is a regression, no ? don't have a 4.6 tree handy
to check it but ...


  reply	other threads:[~2015-01-23 10:40 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 ` ramana at gcc dot gnu.org [this message]
2021-12-25  9:55 ` [Bug ipa/56139] [9/10/11/12 Regression] " pinskia at gcc dot gnu.org
2022-10-19  8:52 ` [Bug ipa/56139] [10/11/12/13 " 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-9Z4hHX7fJj@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).